Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide migration from SLES 12 SP5 to SLES 15 SP4 in aggregated updates #18756

Merged
merged 1 commit into from
Apr 16, 2024

Conversation

hjluo
Copy link
Contributor

@hjluo hjluo commented Feb 28, 2024

$${{\color{green}\Huge{\textsf{ Provide migration from SLES 12 SP5 to SLES 15 SP4 in aggregated updates }}}}$$

@hjluo hjluo changed the title Provide migration from SLES 12 SP5 to SLES 15 SP4 in aggregated updates WIP: Provide migration from SLES 12 SP5 to SLES 15 SP4 in aggregated updates Feb 28, 2024
@hjluo hjluo added the qe-yam label Feb 28, 2024
@hjluo hjluo changed the title WIP: Provide migration from SLES 12 SP5 to SLES 15 SP4 in aggregated updates Provide migration from SLES 12 SP5 to SLES 15 SP4 in aggregated updates Feb 28, 2024
Copy link
Contributor

@rakoenig rakoenig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@lemon-suse
Copy link
Contributor

Is this 'regression for addon_products_sle' related with the PR?

@hjluo
Copy link
Contributor Author

hjluo commented Feb 29, 2024

Is this 'regression for addon_products_sle' related with the PR?

cause we've changed the code in addon_products_sle.pm

@hjluo hjluo force-pushed the maintenance_migration branch 3 times, most recently from 70a4204 to ed7331d Compare March 4, 2024 01:54
@hjluo hjluo changed the title Provide migration from SLES 12 SP5 to SLES 15 SP4 in aggregated updates WIP: Provide migration from SLES 12 SP5 to SLES 15 SP4 in aggregated updates Mar 4, 2024
@hjluo hjluo force-pushed the maintenance_migration branch 8 times, most recently from ce883d2 to a2029dd Compare March 4, 2024 08:35
@hjluo hjluo changed the title WIP: Provide migration from SLES 12 SP5 to SLES 15 SP4 in aggregated updates Provide migration from SLES 12 SP5 to SLES 15 SP4 in aggregated updates Mar 4, 2024
@hjluo hjluo force-pushed the maintenance_migration branch 5 times, most recently from d380583 to 2eef41b Compare March 5, 2024 04:05
@hjluo
Copy link
Contributor Author

hjluo commented Apr 3, 2024

there are aprox. 28 repos with updates, but I can only see in patching 20, could you please check that?

I've manually run zypper patch 2 times and it still shows 20 packages patched. the rest may be for the reason that 8 packages were not installed, so even though we have a repo we can't do a patch here.

@hjluo hjluo changed the title WIP: Provide migration from SLES 12 SP5 to SLES 15 SP4 in aggregated updates Provide migration from SLES 12 SP5 to SLES 15 SP4 in aggregated updates Apr 3, 2024
@hjluo
Copy link
Contributor Author

hjluo commented Apr 3, 2024

You'd better to un-label WIP when already ready for review.

Done.

@lemon-suse
Copy link
Contributor

LGTM.

@hjluo hjluo force-pushed the maintenance_migration branch 2 times, most recently from e1c7349 to 765bd2f Compare April 8, 2024 09:04
@jknphy
Copy link
Contributor

jknphy commented Apr 9, 2024

we already have one test suite, 'create_hdd_yast_maintenance_desktop', that install the system, I don't get why we are adding a new one here, we should reuse (/fix) the existing one as described in the ticket.

@lemon-suse
Copy link
Contributor

we already have one test suite, 'create_hdd_yast_maintenance_desktop', that install the system, I don't get why we are adding a new one here, we should reuse (/fix) the existing one as described in the ticket.

Yes, we should re-use this 'create_hdd_yast_maintenance_desktop' , while the test on 12SP5 has an issue that can't add unreleased repo, should fix in another ticket.

@hjluo
Besides, it is strange that I found you added de-register in latest VR, https://openqa.suse.de/tests/13964318#step/scc_deregistration/1 I think that is not as expected.

@jknphy
Copy link
Contributor

jknphy commented Apr 10, 2024

we already have one test suite, 'create_hdd_yast_maintenance_desktop', that install the system, I don't get why we are adding a new one here, we should reuse (/fix) the existing one as described in the ticket.

Yes, we should re-use this 'create_hdd_yast_maintenance_desktop' , while the test on 12SP5 has an issue that can't add unreleased repo, should fix in another ticket.

@hjluo Besides, it is strange that I found you added de-register in latest VR, https://openqa.suse.de/tests/13964318#step/scc_deregistration/1 I think that is not as expected.

why in another ticket? I don't think it is a good idea duplicate autoyast profile and not fixing in this one, what is the different between both profiles that one add the repos and the other not?

For example this block is not necessary, because sle 12 sp5 doesn't have libyui-rest-api:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18756/files#diff-f969ba3f0eca25129917f41599a294bad311508f3f645c8273b0b9b574ebf5d0R222-R230

@lemon-suse
Copy link
Contributor

we already have one test suite, 'create_hdd_yast_maintenance_desktop', that install the system, I don't get why we are adding a new one here, we should reuse (/fix) the existing one as described in the ticket.

Yes, we should re-use this 'create_hdd_yast_maintenance_desktop' , while the test on 12SP5 has an issue that can't add unreleased repo, should fix in another ticket.
@hjluo Besides, it is strange that I found you added de-register in latest VR, https://openqa.suse.de/tests/13964318#step/scc_deregistration/1 I think that is not as expected.

why in another ticket? I don't think it is a good idea duplicate autoyast profile and not fixing in this one, what is the different between both profiles that one add the repos and the other not?

For example this block is not necessary, because sle 12 sp5 doesn't have libyui-rest-api: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18756/files#diff-f969ba3f0eca25129917f41599a294bad311508f3f645c8273b0b9b574ebf5d0R222-R230

I haven't express clear for my meaning, in fact I just mean there already a ticket created https://progress.opensuse.org/issues/158401 . NP to fix it in this PR, I think need compare the profiles to update.

1 similar comment
@lemon-suse
Copy link
Contributor

we already have one test suite, 'create_hdd_yast_maintenance_desktop', that install the system, I don't get why we are adding a new one here, we should reuse (/fix) the existing one as described in the ticket.

Yes, we should re-use this 'create_hdd_yast_maintenance_desktop' , while the test on 12SP5 has an issue that can't add unreleased repo, should fix in another ticket.
@hjluo Besides, it is strange that I found you added de-register in latest VR, https://openqa.suse.de/tests/13964318#step/scc_deregistration/1 I think that is not as expected.

why in another ticket? I don't think it is a good idea duplicate autoyast profile and not fixing in this one, what is the different between both profiles that one add the repos and the other not?

For example this block is not necessary, because sle 12 sp5 doesn't have libyui-rest-api: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18756/files#diff-f969ba3f0eca25129917f41599a294bad311508f3f645c8273b0b9b574ebf5d0R222-R230

I haven't express clear for my meaning, in fact I just mean there already a ticket created https://progress.opensuse.org/issues/158401 . NP to fix it in this PR, I think need compare the profiles to update.

@hjluo hjluo force-pushed the maintenance_migration branch 2 times, most recently from 5e4188d to ab2a209 Compare April 11, 2024 06:07
@hjluo hjluo force-pushed the maintenance_migration branch 2 times, most recently from f24d2f6 to 05c245b Compare April 15, 2024 08:47
@hjluo hjluo force-pushed the maintenance_migration branch 3 times, most recently from 8f22034 to 12697da Compare April 16, 2024 06:50
@hjluo hjluo force-pushed the maintenance_migration branch 2 times, most recently from e318f94 to c710ab8 Compare April 16, 2024 08:54
@jknphy jknphy merged commit 96c624a into os-autoinst:master Apr 16, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants