Bug 1218795

Summary: HA online migration from sles15sp3 to sles15sp6, got error message: nothing provides 'pacemaker-schemas = 2.1.7+20231219.0f7f88312-150600.1.1'
Product: [openSUSE] PUBLIC SUSE Linux Enterprise High Availability Extension 15 SP6 Reporter: yutao wang <yuwang>
Component: InstallationAssignee: Yan Gao <ygao>
Status: RESOLVED FIXED QA Contact:
Severity: Normal    
Priority: P3 - Medium CC: eugenio.paolantonio, kernel-storage-team, pgajdos, thao.huynh, yuwang
Version: unspecified   
Target Milestone: ---   
Hardware: S/390   
OS: SLES 15   
URL: https://openqa.suse.de/tests/13242850/modules/zypper_migration/steps/6
Whiteboard:
Found By: openQA Services Priority:
Business Priority: Blocker: Yes
Marketing QA Status: --- IT Deployment: ---
Attachments: zypper migration log file

Description yutao wang 2024-01-15 01:33:33 UTC
Created attachment 871867 [details]
zypper migration log file

Hardware: s390x, x86_64, aarch64, ppc64le
Migration: Installed sles5sp3 upgrade to sles15sp6
***************************************************************
## Observation

openQA test in scenario sle-15-SP6-Migration-from-SLE15-SPx-s390x-ha_migration_online_pscc_sles15sp3@s390x-kvm fails in
[zypper_migration](https://openqa.suse.de/tests/13242850/modules/zypper_migration/steps/6)

## Reproducible

Fails since (at least) Build [46.40](https://openqa.suse.de/tests/13242850) (current job)

## Further details

Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=s390x&distri=sle&flavor=Migration-from-SLE15-SPx&machine=s390x-kvm&test=ha_migration_online_pscc_sles15sp3&version=15-SP6)
*********************************************************************
Test steps:
1. Installed sles15sp3 with HA and LTSS
2. Update the system
3. Remove LTSS
4. Did 'zypper migration'  upgrade to sles15sp6
Got error message:
8 Problems:
Problem: nothing provides 'pacemaker-schemas = 2.1.7+20231219.0f7f88312-150600.1.1' needed by the to be installed pacemaker-libs-2.1.7+20231219.0f7f88312-150600.1.1.s390x
Problem: nothing provides 'python3-pacemaker = 2.1.7+20231219.0f7f88312-150600.1.1' needed by the to be installed pacemaker-2.1.7+20231219.0f7f88312-150600.1.1.s390x
Problem: nothing provides 'libsgutils2-1.48.so.2()(64bit)' needed by the to be installed sg3_utils-1.48+4.fa9618a-150600.1.1.s390x
Problem: nothing provides 'libpoppler.so.132()(64bit)' needed by the to be installed poppler-tools-23.10.0-150600.1.1.s390x
Problem: nothing provides 'libpoppler.so.132()(64bit)' needed by the to be installed libpoppler-cpp0-23.10.0-150600.1.1.s390x
Problem: nothing provides 'libLLVM.so.17()(64bit)' needed by the to be installed Mesa-dri-23.2.1-150600.80.1.s390x
Problem: nothing provides 'pacemaker-schemas = 2.1.7+20231219.0f7f88312-150600.1.1' needed by the to be installed pacemaker-libs-2.1.7+20231219.0f7f88312-150600.1.1.s390x
Problem: nothing provides 'pacemaker-schemas = 2.1.7+20231219.0f7f88312-150600.1.1' needed by the to be installed pacemaker-libs-2.1.7+20231219.0f7f88312-150600.1.1.s390x

Problem: nothing provides 'pacemaker-schemas = 2.1.7+20231219.0f7f88312-150600.1.1' needed by the to be installed pacemaker-libs-2.1.7+20231219.0f7f88312-150600.1.1.s390x
 Solution 1: Following actions will be done:
  deinstallation of libpacemaker3-2.0.5+20201202.ba59be712-150300.4.33.5.s390x
  deinstallation of patterns-ha-ha_sles-15.1.0-11.1.s390x
  deinstallation of ha-cluster-bootstrap-0.5-13.3.1.noarch
 Solution 2: keep obsolete libpacemaker3-2.0.5+20201202.ba59be712-150300.4.33.5.s390x
 Solution 3: break pacemaker-libs-2.1.7+20231219.0f7f88312-150600.1.1.s390x by ignoring some of its dependencies
Comment 1 Yan Gao 2024-01-15 11:18:49 UTC
Apparently the new sub-packages of pacemaker, pacemaker-schemas and python3-pacemaker, are not existing in the SLE15 SP6 HA installation source/media yet.

Thao is helping with this. Thanks!
Comment 2 Eugenio Paolantonio 2024-01-16 11:05:10 UTC
Hi, build 46.40 is faulty, the next build will have these packages properly shipped in the media. Thanks and sorry for the noise!
Comment 3 Yan Gao 2024-01-16 11:32:36 UTC
Thanks for the info, Eugenio.
Comment 4 Petr Gajdos 2024-01-16 11:58:05 UTC
Thanks for the info as well
Comment 6 yutao wang 2024-01-24 06:47:13 UTC
This bug has been fixed.
Verified: https://openqa.suse.de/tests/13320622
Comment 7 Yan Gao 2024-01-24 10:21:10 UTC
Thanks for verification, yutao.

And thanks to Thao and Eugenio for taking care.

Closing it now.