[opensuse] stuck kernel package from 42.2 after dup to 42.3 that is needed by ipset-kmp-default
Right now as I am typing this bug onto the list here, I figure, that there is multiple ipset-kmp-default packages on the machine still. Originally I had a 42.2 system, and dup-ed it to 42.3 some while ago. After a while now, I also try to clean up unused kernel-packages, as opensuse saves or keeps two distinct versions on the system installed, maybe as a fallback. Thats when I found, that I couldnt rpm -e the one kernel-default..... package today, as the rpm replied that it was still in use by some ipset-kmp-default. I didnt force it to be removed or so, so far. Right now as I am writing, I decided to see what ipset packages were on the system just as a gut feeling, and apparently there is also multiple installed, probably some leftover due to mishaps during zypper dup from 42.2 to 42.3? I read something about kernel package versions bug when going from 42.2 to 42.3 that were named with bad revision numbers or something so that zypper or rpm would keep a lower versioned kernel package even when upgrading to 42.3 maybe that or similar is the case here with ipset-kmp as well? here are some error logs: sudo rpm -e kernel-default-4.4.74-18.20.1.x86_64 [sudo] password for root: error: Failed dependencies: ksym(default:__alloc_skb) = 8dcf4dcd is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:__netlink_dump_start) = 17acfde3 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:__nlmsg_put) = c51274da is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:__pskb_pull_tail) = c14dfbc0 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:dev_get_by_index_rcu) = 966a59e4 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:ipv6_skip_exthdr) = e9d68b14 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:kfree_skb) = 7585cd2c is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:module_layout) = 84e6b870 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:module_put) = 8ab8a627 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:mutex_lock) = 5d083dc2 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:mutex_unlock) = 3641d42 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:netlink_ack) = fb929982 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:netlink_unicast) = 87c6a320 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:nf_register_sockopt) = 280927eb is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:nf_unregister_sockopt) = dee26e07 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:nfnetlink_subsys_register) = ee210dc0 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:nfnetlink_subsys_unregister) = 625b73a is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:ns_capable) = fffc3dc2 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:param_ops_int) = 7389fdb8 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:register_pernet_subsys) = 7d3bf1f3 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:skb_copy_bits) = c1c82c8e is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:skb_pull) = 1527026c is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:skb_push) = 53e381ca is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:skb_trim) = 37543bae is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:tcf_em_register) = b0286127 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:tcf_em_unregister) = dc81202 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:try_module_get) = c33d56c4 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:unregister_pernet_subsys) = e514b5f9 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:xt_register_matches) = 6ec37eed is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:xt_register_targets) = a4851cd7 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:xt_unregister_matches) = 379bbf4a is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:xt_unregister_targets) = ec6e725d is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 rpm -aq | grep kmp ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ipset-kmp-default-6.29_k4.4.76_1-3.19.x86_64 drm-kmp-default-4.9.33_k4.4.76_1-3.2.x86_64 rpm -aq | grep kerne kernel-firmware-20170530-9.1.noarch kernel-default-4.4.79-19.1.x86_64 kernel-default-4.4.74-18.20.1.x86_64 Thanks for hints. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op woensdag 16 augustus 2017 13:23:37 CEST schreef cagsm:
Right now as I am typing this bug onto the list here, I figure, that there is multiple ipset-kmp-default packages on the machine still.
Originally I had a 42.2 system, and dup-ed it to 42.3 some while ago.
After a while now, I also try to clean up unused kernel-packages, as opensuse saves or keeps two distinct versions on the system installed, maybe as a fallback.
Thats when I found, that I couldnt rpm -e the one kernel-default..... package today, as the rpm replied that it was still in use by some ipset-kmp-default.
I didnt force it to be removed or so, so far.
Right now as I am writing, I decided to see what ipset packages were on the system just as a gut feeling, and apparently there is also multiple installed, probably some leftover due to mishaps during zypper dup from 42.2 to 42.3?
I read something about kernel package versions bug when going from 42.2 to 42.3 that were named with bad revision numbers or something so that zypper or rpm would keep a lower versioned kernel package even when upgrading to 42.3
maybe that or similar is the case here with ipset-kmp as well?
here are some error logs:
sudo rpm -e kernel-default-4.4.74-18.20.1.x86_64 [sudo] password for root: error: Failed dependencies: ksym(default:__alloc_skb) = 8dcf4dcd is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:__netlink_dump_start) = 17acfde3 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:__nlmsg_put) = c51274da is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:__pskb_pull_tail) = c14dfbc0 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:dev_get_by_index_rcu) = 966a59e4 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:ipv6_skip_exthdr) = e9d68b14 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:kfree_skb) = 7585cd2c is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:module_layout) = 84e6b870 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:module_put) = 8ab8a627 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:mutex_lock) = 5d083dc2 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:mutex_unlock) = 3641d42 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:netlink_ack) = fb929982 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:netlink_unicast) = 87c6a320 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:nf_register_sockopt) = 280927eb is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:nf_unregister_sockopt) = dee26e07 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:nfnetlink_subsys_register) = ee210dc0 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:nfnetlink_subsys_unregister) = 625b73a is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:ns_capable) = fffc3dc2 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:param_ops_int) = 7389fdb8 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:register_pernet_subsys) = 7d3bf1f3 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:skb_copy_bits) = c1c82c8e is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:skb_pull) = 1527026c is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:skb_push) = 53e381ca is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:skb_trim) = 37543bae is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:tcf_em_register) = b0286127 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:tcf_em_unregister) = dc81202 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:try_module_get) = c33d56c4 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:unregister_pernet_subsys) = e514b5f9 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:xt_register_matches) = 6ec37eed is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:xt_register_targets) = a4851cd7 is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:xt_unregister_matches) = 379bbf4a is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ksym(default:xt_unregister_targets) = ec6e725d is needed by (installed) ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64
rpm -aq | grep kmp ipset-kmp-default-6.32_k4.4.27_2-63.1.x86_64 ipset-kmp-default-6.29_k4.4.76_1-3.19.x86_64 drm-kmp-default-4.9.33_k4.4.76_1-3.2.x86_64
rpm -aq | grep kerne kernel-firmware-20170530-9.1.noarch kernel-default-4.4.79-19.1.x86_64 kernel-default-4.4.74-18.20.1.x86_64
Thanks for hints.
Remove the ipset-kmp....4.4.27...., then try again. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Aug 16, 2017 at 1:32 PM, Knurpht - Gertjan Lettink <knurpht@opensuse.org> wrote:
Remove the ipset-kmp....4.4.27...., then try again.
yes thanks I already had figured or was in midst of the process of finding out about this when I started writing my mailinglist post ;) thanks anways, apparently I had leftovers from some additional repo still from 42.2 which brought in some ipset and network stuff, that blocked or kept those other kernel packages and so on. now I have removed all 42.2 leftovers. thank you. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 16/08/17 07:23 AM, cagsm wrote:
Thats when I found, that I couldnt rpm -e the one kernel-default.....
Just out of curiosity ... Why are you manually removing the kernels rather than using the 'purge_kernels" utility? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-16 15:58, Anton Aylward wrote:
On 16/08/17 07:23 AM, cagsm wrote:
Thats when I found, that I couldnt rpm -e the one kernel-default.....
Just out of curiosity ...
Why are you manually removing the kernels rather than using the 'purge_kernels" utility?
Because it failed. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Wed, Aug 16, 2017 at 3:58 PM, Anton Aylward <opensuse@antonaylward.com> wrote:
Just out of curiosity ... Why are you manually removing the kernels rather than using the 'purge_kernels" utility?
I used to have situations when I reboot a machine and the newly installed kernel (via zypper up) didnt become the booted kernel. Ever since those troubles and hassle I always remove the currently running kernel packe while still being on the machine alive, and then only the new kernel package from a zypper up remains and becomes the booted one. Learned the hard way. Maybe its just me or its specialties and corner cases or whatever but this way I have more control, and grub2 logics and syntax and all those config files seem too hard or too cumbersome and chaos to me or I never had time so far to really get my head around all those places where you influence what gets written into grub2 places and what becomes the active to be booted entry and so on. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 17/08/17 06:28 AM, cagsm wrote:
On Wed, Aug 16, 2017 at 3:58 PM, Anton Aylward <opensuse@antonaylward.com> wrote:
Just out of curiosity ... Why are you manually removing the kernels rather than using the 'purge_kernels" utility?
I used to have situations when I reboot a machine and the newly installed kernel (via zypper up) didnt become the booted kernel.
I can think of a few reasons for that happening but the all get back to the rebuilding of the grub.conf menu of kernels. Since you are making sure you have only the one kernel you never see that the bot menu can offer a choice of the menus available.
Ever since those troubles and hassle I always remove the currently running kernel packe while still being on the machine alive, and then only the new kernel package from a zypper up remains and becomes the booted one. Learned the hard way.
There are, I suppose, ways to disable the rebuilding of the grub.conf after zypper up installs a new kernel but they don't come to mind. Maybe be it ha to do with multiversion.kernels setting in /etc/zypp/zypp.conf ? There are those of us that keep a backlog of kernels as well as specific kennels using that setting and do purge others.
Maybe its just me or its specialties and corner cases or whatever but this way I have more control, and grub2 logics and syntax and all those config files seem too hard or too cumbersome and chaos to me or I never had time so far to really get my head around all those places where you influence what gets written into grub2 places and what becomes the active to be booted entry and so on.
Just so. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Anton Aylward -
cagsm -
Carlos E. R. -
Knurpht - Gertjan Lettink