|
Bugzilla – Full Text Bug Listing |
| Summary: | kmod-compat has broken dependencies | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Moritz Duge <duge> |
| Component: | Upgrade Problems | Assignee: | Lubos Kocman <lubos.kocman> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | dcassany, lslezak, lubos.kocman, martin.wilck, mlin, ms, ops, varkoly |
| Version: | Leap 15.3 | Flags: | martin.wilck:
needinfo?
(lubos.kocman) martin.wilck: needinfo? (mlin) |
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Moritz Duge
2021-05-28 14:48:36 UTC
kmod-compat is obsolete. So this behavior is correct.
# rpm -q --obsoletes kmod
kmod-compat < 28-2.1
module-init-tools < 3.16
# rpm -q --provides kmod
...
kmod-compat = 28-2.1
The problem, if any, is that kmod-compat still appears in the "oss" repository:
> http://download.opensuse.org/distribution/leap/15.3/repo/oss/x86_64/kmod-compat-25-6.7.1.x86_64.rpm
It probably should have been deleted. I can see that it does NOT show up in the SLE15-SP3 repos any more (but in SLE15-SP2). So most likely an oversight in the SLE->Leap port.
Not sure who would be the default assignee. Lubos?
Unfortunately this prevents me building images with KIWI opensuse15-3:/usr/share/kiwi/custom_boot/oemboot # kiwi system build --description suse-SLES15 --set-repo 'dir:/datadisk/download.opensuse.org/distribution/leap/15.3/repo/oss' --target-dir /tmp/test The problem can be found in log file /tmp/test/build/image-root.log DEBUG: 11:06:42 | system: Problem: nothing provides 'kmod = 25-6.7.1' needed by the to be installed kmod-compat-25-6.7.1.x86_64 DEBUG: 11:06:42 | system: Solution 1: do not install kmod-compat-25-6.7.1.x86_64 DEBUG: 11:06:42 | system: Solution 2: break kmod-compat-25-6.7.1.x86_64 by ignoring some of its dependencies DEBUG: 11:06:42 | system: Choose from above solutions by number or cancel [1/2/c/d/?] (c): c ERROR: 11:06:42 | KiwiInstallPhaseFailed: System package installation failed: INFO: 11:06:42 | Cleaning up SystemPrepare instance Why is kmod-compat installed at all? It's certainly not part of a standard Leap 15.3 installation (or SLE15-SP3, for that matter). Setting needinfo on David Cassany (Kiwi team). (In reply to Olli Savia from comment #2) > Unfortunately this prevents me building images with KIWI > > opensuse15-3:/usr/share/kiwi/custom_boot/oemboot # kiwi system build > --description suse-SLES15 --set-repo > 'dir:/datadisk/download.opensuse.org/distribution/leap/15.3/repo/oss' > --target-dir /tmp/test > > The problem can be found in log file /tmp/test/build/image-root.log > > DEBUG: 11:06:42 | system: Problem: nothing provides 'kmod = 25-6.7.1' needed > by the to be installed kmod-compat-25-6.7.1.x86_64 > DEBUG: 11:06:42 | system: Solution 1: do not install > kmod-compat-25-6.7.1.x86_64 > DEBUG: 11:06:42 | system: Solution 2: break kmod-compat-25-6.7.1.x86_64 by > ignoring some of its dependencies > DEBUG: 11:06:42 | system: Choose from above solutions by number or cancel > [1/2/c/d/?] (c): c > ERROR: 11:06:42 | KiwiInstallPhaseFailed: System package installation > failed: > INFO: 11:06:42 | Cleaning up SystemPrepare instance I am not sure understand the use case... It looks like you are trying to build the images described in `kiwi-boot-descriptions` package directly by calling `kiwi system build` on them. Or you just did it for demoing purposes? Those image descriptions are meant to be used for custom initrd creation for the oem images that they still use the old initrd creation approach. They should not be used to create a bootable system. They are referenced in `boot` attribute of in `<type>` section for oem images and they are used to create an old legacy initrd not based on dracut. In order to use dracut based builds for OEM images you should have a `<type>` section in you config.xml that includes `initrd_system="dracut"` attribute and does **not** include the `boot` attribute. Note that the old custom kiwi initrds are deprecated and are only in maintenance mode for pxe and oem images on SLE. If for some reason the old oemboot code is needed (aka, you relay on some old oemboot code hooks) we need further details about the use case. The host distro, image distro or, ideally, the config.xml file you are trying to build. Sorry for delayed response. Yes, that was purely to demonstrate the problem. In my real use case I was working with an old config file. I have now manged to convert it to dracut based initrd image and my problem is solved now. Thanks for the hint. Anyway, the original problem (broken deps) is still valid. The only thing that's broken is that kmod-compat still lurks around in the repos. As long as you don't pull it in you'll have no broken deps, and you won't be missing anything. BUT: kmod-compat is *required* by "kiwi-boot-requires" and "yast2-sap-ha", and is *recommended* by "inxi" and "patterns-base-enhanced_base". No SLE15-SP3 / Leap 15.3 package should pull in kmod-compat any more. Adding lslezak for yast-sap-ha and maxlin for kiwi and patterns. (In reply to Olli Savia from comment #5) > Sorry for delayed response. > > Yes, that was purely to demonstrate the problem. > > In my real use case I was working with an old config file. I have now manged > to convert it to dracut based initrd image and my problem is solved now. > Thanks for the hint. I glad to know you are no longer blogged and that your is now solved. > Anyway, the original problem (broken deps) is still valid. I am having a look at it, I am slightly puzzled though, looking at the kmod spec looks like there should not a problem as in SP3 kmod obsoletes and provides kmod-compat, so I would have expected no issue on packaging solving... Peter, please check the kmod-compat dependency in yast2-sap-ha. Is it actually needed? Maybe there is a newer replacement for that... (In reply to Ladislav Slezák from comment #8) > Peter, please check the kmod-compat dependency in yast2-sap-ha. Is it > actually needed? Maybe there is a newer replacement for that... I've fixed the issue. Need review: https://github.com/yast/yast-sap-ha/pull/8 https://github.com/yast/yast-sap-ha/pull/7 Just some small notes: https://github.com/yast/yast-sap-ha/pull/8#pullrequestreview-830240400 The YaST part has been fixed in the pull request above, the other packages (comment #6), might still need a fix... FIXED SUSE-RU-2022:2705-1: An update that has 6 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1158843,1186618,1190774,1197290,1199029,1200427 CVE References: JIRA References: Sources used: SUSE Linux Enterprise Module for SAP Applications 15-SP2 (src): yast2-sap-ha-1.0.15-150000.3.11.1 SUSE Linux Enterprise Module for SAP Applications 15-SP1 (src): yast2-sap-ha-1.0.15-150000.3.11.1 SUSE Linux Enterprise Module for SAP Applications 15 (src): yast2-sap-ha-1.0.15-150000.3.11.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. |