action #18488
closed[Migration] sles12 GA LTSS migration
Added by mitiao about 7 years ago. Updated almost 7 years ago.
100%
Description
Just got regcode of sles12 ga LTSS.
Implement offline/online migration for sles 12 ga LTSS
Updated by mitiao about 7 years ago
- Status changed from New to In Progress
Tried to verify the process of online migration from sles12 ga LTSS to sles12 sp3 via scc/proxyscc:
Note: so far we have to delete LTSS product and its repos before migration, otherwise there is no available migration target.
Steps:
- Launch sles12 ga and register base product and LTSS product with given regcodes.
- Perform fully patch
Remove LTSS product and its services and repos by following commands:
zypper rm -t product SLES-LTSS
zypper rs SUSE_Linux_Enterprise_Server_LTSS_12_x86_64
4a. Perform online migration by zypper migration via scc with following output:
Executing 'zypper refresh'
Repository 'SLES12-12-0' is up to date.
Repository 'SLES12-Pool' is up to date.
Repository 'SLES12-Updates' is up to date.
All repositories have been refreshed.
Executing 'zypper --no-refresh patch-check --updatestack-only'
Loading repository data...
Reading installed packages...
0 patches needed (0 security patches)
command 'zypper --no-refresh --non-interactive install --no-recommends -t product SLES-LTSS' failed
Can't install release package for registered product SLES-LTSS
SUSE::Connect::ZypperError: Product 'SLES-LTSS' not found.
Calling SUSEConnect rollback to make sure SCC is synchronized with the system state.
Available migrations:
1 | SUSE Linux Enterprise Server 12 SP3 x86_64
2 | SUSE Linux Enterprise Server 12 SP2 x86_64
3 | SUSE Linux Enterprise Server 12 SP1 x86_64
[num/q]:
Above error shown and call rollback to sync scc with system, then able to show the migration target.
4b. Perform online migration by zypper migration via proxyscc with following output:
Executing 'zypper refresh'
Repository 'SLES12-12-0' is up to date.
Repository 'SLES12-Pool' is up to date.
Repository 'SLES12-Updates' is up to date.
All repositories have been refreshed.
Executing 'zypper --no-refresh patch-check --updatestack-only'
Loading repository data...
Reading installed packages...
0 patches needed (0 security patches)
command 'zypper --no-refresh --non-interactive install --no-recommends -t product SLES-LTSS' failed
Can't install release package for registered product SLES-LTSS
SUSE::Connect::ZypperError: Product 'SLES-LTSS' not found.
Calling SUSEConnect rollback to make sure SCC is synchronized with the system state.
command 'zypper --non-interactive --releasever 12 ref -f' failed
Can't determine the list of installed products: SUSE::Connect::ZypperError: Repository 'SLES12-Pool' is invalid.
[SUSE_Linux_Enterprise_Server_12_x86_64:SLES12-Pool|http://openqa.suse.de/assets/repo/SLE-12-SERVER-POOL-x86_64-Build0323-Media1/] Valid metadata not found at specified URL
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'SLES12-Pool' because of the above error.
Repository 'SLES12-Updates' is invalid.
[SUSE_Linux_Enterprise_Server_12_x86_64:SLES12-Updates|http://openqa.suse.de/assets/repo/SLE-12-SERVER-POOL-x86_64-Build0323-Media1/] Valid metadata not found at specified URL
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'SLES12-Updates' because of the above error.
Some of the repositories have not been refreshed because of an error.
'/usr/lib/zypper/commands/zypper-migration' exited with status 1
Failed as expected with invalid repo by proxyscc.
So I have a question, is it a correct way to migrate with LTSS or what I did wrong among the steps.
I will cc this info to Artem.
Updated by mitiao about 7 years ago
The process of offline migration with ltss works well from my local openQA run.
PR submitting:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2746
Updated by mitiao about 7 years ago
File a bug for this issue:
https://bugzilla.suse.com/show_bug.cgi?id=1034598
Updated by mitiao about 7 years ago
mitiao wrote:
The process of offline migration with ltss works well from my local openQA run.
PR submitting:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2746
Waiting for feedback
Updated by mitiao about 7 years ago
Another PR submit to validate LTSS repos
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2780
Updated by mitiao almost 7 years ago
mitiao wrote:
mitiao wrote:
The process of offline migration with ltss works well from my local openQA run.
PR submitting:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2746Waiting for feedback
Got feedback and confirmation from Marita and Anja, current LTSS migration procedure is OK.
I rebased the PR and change its title to 'Add support for LTSS product migration'.
see: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2746
Updated by mitiao almost 7 years ago
- % Done changed from 0 to 50
PR merged.
Added 8 cases both for online and offline migration with ltss and ltss+addons on x86_64 to job groups
For cases of ltss on s390x, it will take time to create sle12 images of s390x since only 1 zkvm-image worker available.
Updated by mitiao almost 7 years ago
@mgriessmeier
Could you please add following two 12sp0 repos on ftp://openqa.suse.de/fixed/? I would like to create some images for LTSS migration on s390x. Thanks.
SLE-12-HA-GEO-s390x-GM-DVD1
SLE-12-HA-s390x-GM-DVD1
Updated by mitiao almost 7 years ago
From comments of bsc#1039217, dropped ltss+sdk which is not support.
LTSS on x86_64 done.
Working on LTSS for s390x.
Created 12sp0 image for s390x failed on zkvm worker:
https://openqa.suse.de/tests/943822
Feedback from mgriessmeier, sp0 has not been tested on zkvm-image worker and failure was expected.
need to investigate it.
Updated by maritawerner almost 7 years ago
Fate #316271: Technology Preview: KVM on s390x
On SLES 12 GA zKVM was only a Tech Preview so we do not need to test that migration scenario. Please start with SP1 LTSS on zKVM.
Updated by mitiao almost 7 years ago
maritawerner wrote:
Fate #316271: Technology Preview: KVM on s390x
On SLES 12 GA zKVM was only a Tech Preview so we do not need to test that migration scenario. Please start with SP1 LTSS on zKVM.
Got it, thanks.
Updated by mitiao almost 7 years ago
- Status changed from In Progress to Feedback
- % Done changed from 50 to 100
Created sles12sp1 ltss cases for x86_64 and s390x and added them to Migration: Server/HA job groups.
See the results in next build.
Updated by mitiao almost 7 years ago
- Related to action #19736: [migration] test fails in register_without_ltss - issue after skipping LTSS addon on sle12sp1 added
Updated by mitiao almost 7 years ago
- Status changed from Feedback to Resolved
Related issue has been fixed.
Resolved with 12ga/12sp1 with ltss on x84_64 and 12sp1 with ltss on s390x.