Bug 1087534
| Summary: | [kernel] tries to remove booted kernel | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Lukas Slebodnik <lslebodn> | ||||||||||||
| Component: | hawkey | Assignee: | Ales Kozumplik <akozumpl> | ||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 20 | CC: | akozumpl, jzeleny, lslebodn, packaging-team-maint, pnemade, rholy, tim.lauridsen | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | dnf-plugins-core-0.0.8-2.fc20 | Doc Type: | Bug Fix | ||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2014-06-01 00:00:04 UTC | Type: | Bug | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Embargoed: | |||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Lukas Slebodnik
2014-04-14 14:38:53 UTC
Lukas, can you please attach depsolving data [1] for the described case? Thanks! [1] http://dnf.baseurl.org/2013/11/25/reporting-depsolving-bugs/ Created attachment 886366 [details]
testcase.t
Created attachment 886367 [details] solver.result Full debugdata report is here: http://lslebodn.fedorapeople.org/dnf_debug_data_BZ1087534/debugdata.tar When I locally feed the data you provided to hawkey and resolve, I get the expected outcome (i.e. 3.13.6 stays installed). It is however possible we are missing something during the running kernel detection. In hawkey upstream commit a87f0e9 I've added logging of this. I'd like to ask you, once hawkey-0.4.16 or any reaches you and you witness the bug again, please provide the debugdata again, along with /var/cache/dnf/x86_64/hawkey.log file. Thanks for your help! I will try to provide data on Wednesday or on Thursday. I prepare rpms from hawkey git repo. The latest commit has the hash 42a33f151
[root@host ~]# rpm -q hawkey python-hawkey dnf
hawkey-0.4.15-0.42a33f151.fc20.x86_64
python-hawkey-0.4.15-0.42a33f151.fc20.x86_64
dnf-0.4.20-1.fc20.noarch
dnf want to upgrade packages and also remove booted kernel.
But I was not able to run dnf with argument "--debugsolver"
[root@host ~]# dnf --debugsolver upgrade
Resolving dependencies
--> Starting dependency resolution
Traceback (most recent call last):
File "/bin/dnf", line 35, in <module>
main.user_main(sys.argv[1:], exit_code=True)
File "/usr/lib/python2.7/site-packages/dnf/cli/main.py", line 242, in user_main
errcode = main(args)
File "/usr/lib/python2.7/site-packages/dnf/cli/main.py", line 75, in main
return _main(base, args)
File "/usr/lib/python2.7/site-packages/dnf/cli/main.py", line 140, in _main
got_transaction = base.resolve()
File "/usr/lib/python2.7/site-packages/dnf/base.py", line 550, in resolve
if not self.run_hawkey_goal(goal):
File "/usr/lib/python2.7/site-packages/dnf/base.py", line 538, in run_hawkey_goal
goal.write_debugdata()
TypeError: write_debugdata() takes exactly one argument (0 given)
The same result is with dnf from updates-testing
dnf-0.5.1-1.fc20.noarch
BTW argument "--debugsolver" is not documented in manual page dnf
It will be better if you prepare scratch build for me.
Lukas, you can either wait for an F20 release or use our CI repo: http://jenkins.cloud.fedoraproject.org/job/DNF/lastSuccessfulBuild/artifact/ Documented '--debugsolver' in beb6d03. Created attachment 895785 [details]
testcase.t
Created attachment 895788 [details]
solver.result
[root@host ~]# rpm -q dnf hawkey libcomps librepo python-hawkey python-libcomps python-librepo dnf-0.5.1-99.719.20140513gitf75c389.fc20.noarch hawkey-0.4.15-99.719.20140513git42a33f1.fc20.x86_64 libcomps-0.1.6-99.719.20140513gite8c2d8315b1d10e35461450235dac9da267ecb2d.fc20.x86_64 librepo-1.7.3-99.719.20140513git5585ff7.fc20.x86_64 python-hawkey-0.4.15-99.719.20140513git42a33f1.fc20.x86_64 python-libcomps-0.1.6-99.719.20140513gite8c2d8315b1d10e35461450235dac9da267ecb2d.fc20.x86_64 python-librepo-1.7.3-99.719.20140513git5585ff7.fc20.x86_64 Full debug data: http://lslebodn.fedorapeople.org/dnf_debug_data_BZ1087534/debugdata_v2.tar http://lslebodn.fedorapeople.org/dnf_debug_data_BZ1087534/hawkey.log Here's what I see. You're running kernel-debug-3.13.6: INFO May-15 09:26:31 running_kernel(): kernel-debug-3.13.6-200.fc20.x86_64. And the proposed transaction deletes: kernel-debug-3.13.10 kernel-debug-3.13.7 kernel-debug-3.13.8 and their respective kernel-debug-modules-extra packages. It installs: kernel-debug-3.14.3 and its respective kernel-debug-moduels-extra. Most importantly, it keeps around kernel-debug-3.13.6 and its corresponding modules-extra. So I guess there's nothing wrong going on here, won't you agree? And this is what I can see [root@host ~]# dnf update Dependencies resolved. ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: kernel-debug x86_64 3.14.3-200.fc20 updates 33 M kernel x86_64 3.14.3-200.fc20 updates 32 M kernel-modules-extra x86_64 3.14.3-200.fc20 updates 2.1 M kernel-debug-modules-extra x86_64 3.14.3-200.fc20 updates 2.2 M Upgrading: kernel-devel x86_64 3.14.3-200.fc20 updates 8.7 M kernel-headers x86_64 3.14.3-200.fc20 updates 946 k kernel-tools x86_64 3.14.3-200.fc20 updates 141 k kernel-tools-libs x86_64 3.14.3-200.fc20 updates 68 k Removing: kernel x86_64 3.13.6-200.fc20 @System 133 M kernel x86_64 3.13.7-200.fc20 @System 133 M kernel x86_64 3.13.8-200.fc20 @System 133 M kernel-debug x86_64 3.13.7-200.fc20 @System 140 M kernel-debug x86_64 3.13.8-200.fc20 @System 140 M kernel-debug x86_64 3.13.10-200.fc20 @System 140 M kernel-debug-modules-extra x86_64 3.13.7-200.fc20 @System 8.9 M kernel-debug-modules-extra x86_64 3.13.8-200.fc20 @System 8.9 M kernel-debug-modules-extra x86_64 3.13.10-200.fc20 @System 8.9 M kernel-modules-extra x86_64 3.13.6-200.fc20 @System 8.1 M kernel-modules-extra x86_64 3.13.7-200.fc20 @System 8.1 M kernel-modules-extra x86_64 3.13.8-200.fc20 @System 8.1 M Transaction Summary ================================================================================ Install 4 Packages Upgrade 4 Packages Remove 12 Packages Total download size: 79 M Is this ok [y/N]: N Exiting on user Command [root@host ~]# uname -a Linux host 3.13.6-200.fc20.x86_64 #1 SMP Fri Mar 7 17:02:28 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux If you want I can test another packages with extra debug messages. I think that's exactly the correct behavior. What does 'cat /proc/cmdline' output? Created attachment 895846 [details] output from yum I am providing output from yum and it is related to 1087534#c13 [root@host ~]# cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.13.6-200.fc20.x86_64 root=/dev/mapper/fedora_18-root ro rd.lvm.lv=fedora_18/swap rd.md=0 rd.dm=0 rd.luks.uuid=luks-51de39ac-7a57-45e8-981c-3a804e0d04bf vconsole.keymap=us rd.lvm.lv=fedora_18/root rhgb quiet LANG=en_US.UTF-8 I am sorry, but I am not sure what is correct on removing booted kernel. yum do not want to remove kernel 3.13.6-200.fc20 and dnf *will*. (In reply to Lukas Slebodnik from comment #16) > [root@host ~]# cat /proc/cmdline > BOOT_IMAGE=/vmlinuz-3.13.6-200.fc20.x86_64 root=/dev/mapper/fedora_18-root > ro rd.lvm.lv=fedora_18/swap rd.md=0 rd.dm=0 > rd.luks.uuid=luks-51de39ac-7a57-45e8-981c-3a804e0d04bf vconsole.keymap=us > rd.lvm.lv=fedora_18/root rhgb quiet LANG=en_US.UTF-8 You're right I see what is going on now. We are incorrectly detecting the user is running a debug kernel. If you want I can try to reboot to the debug kernel to confirm your assumption. Fixed upstream by c5e6501, you can retest using the CI build once it finishes. Thank you very much for fix. It works as expected. But I have found another issue. It can be related to this BZ. I am not sure. If I try to remove single package (e.g. augeas-devel), dnf tries to automatically remove old kernels. Yum wants to remove just a single package. Should I file another BZ? dnf-plugins-core-0.0.8-2.fc20, libsolv-0.6.1-1.git6d968f1.fc20, hawkey-0.4.16-1.fc20, dnf-0.5.2-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/libsolv-0.6.1-1.git6d968f1.fc20,hawkey-0.4.16-1.fc20,dnf-0.5.2-1.fc20,dnf-plugins-core-0.0.8-2.fc20 Package dnf-plugins-core-0.0.8-2.fc20, libsolv-0.6.1-1.git6d968f1.fc20, hawkey-0.4.16-1.fc20, dnf-0.5.2-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dnf-plugins-core-0.0.8-2.fc20 libsolv-0.6.1-1.git6d968f1.fc20 hawkey-0.4.16-1.fc20 dnf-0.5.2-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-6789/libsolv-0.6.1-1.git6d968f1.fc20,hawkey-0.4.16-1.fc20,dnf-0.5.2-1.fc20,dnf-plugins-core-0.0.8-2.fc20 then log in and leave karma (feedback). dnf-plugins-core-0.0.8-2.fc20, libsolv-0.6.1-1.git6d968f1.fc20, hawkey-0.4.16-1.fc20, dnf-0.5.2-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |