dhcp-client upgrade breaks automatic transactional-updates (due to manual intervention)

Hi everyone, not sure if this was reported already, if not I can open a bugzilla if needed. I just noticed that one of my openSUSE MicroOS machines was not updating automatically anymore. Seems like an update for dhcp-client-4.4.2.P1-7.3.x86_64 makes manual intervention necessary:
Problem: the to be installed dhcp-client-4.4.2.P1-7.3.x86_64 requires 'hostname', but this requirement cannot be provided not installable providers: hostname-3.23-2.10.i586[repo-oss] hostname-3.23-2.10.x86_64[repo-oss] Solution 1: deinstallation of busybox-hostname-1.35.0-21.2.noarch Solution 2: deinstallation of patterns-microos-base-5.0-44.1.x86_64 Solution 3: keep obsolete patterns-microos-base-5.0-44.1.x86_64 Solution 4: break dhcp-client-4.4.2.P1-7.3.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c):
Seems like it requires the "hostname" package, that is not installable as it conflicts with "busybox-hostname":
Problem: the installed busybox-hostname-1.35.0-21.2.noarch conflicts with 'hostname' provided by the to be installed hostname-3.23-2.10.x86_64 Solution 1: deinstallation of busybox-hostname-1.35.0-21.2.noarch Solution 2: do not install hostname-3.23-2.10.x86_64
Choose from above solutions by number or cancel [1/2/c/d/?] (c):
I replaced busybox-hostname with hostname, as it is on my other MicroOS machines, and the "zypper dup" worked fine after that. Not sure why this machine had it, but it was installed way after the other ones and was installed with SELINUX enabled. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

On Mon, Mar 14, Johannes Kastl wrote:
Hi everyone,
not sure if this was reported already, if not I can open a bugzilla if needed.
I just noticed that one of my openSUSE MicroOS machines was not updating automatically anymore.
Seems like an update for dhcp-client-4.4.2.P1-7.3.x86_64 makes manual intervention necessary:
Problem: the to be installed dhcp-client-4.4.2.P1-7.3.x86_64 requires 'hostname', but this requirement cannot be provided not installable providers: hostname-3.23-2.10.i586[repo-oss] hostname-3.23-2.10.x86_64[repo-oss] Solution 1: deinstallation of busybox-hostname-1.35.0-21.2.noarch Solution 2: deinstallation of patterns-microos-base-5.0-44.1.x86_64 Solution 3: keep obsolete patterns-microos-base-5.0-44.1.x86_64 Solution 4: break dhcp-client-4.4.2.P1-7.3.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c):
Seems like it requires the "hostname" package, that is not installable as it conflicts with "busybox-hostname":
Bug in dhcp-client, it should require /usr/bin/hostname or so and not a package name. I'm pretty sure I fixed that already in some point in the past.. Thorsten
Problem: the installed busybox-hostname-1.35.0-21.2.noarch conflicts with 'hostname' provided by the to be installed hostname-3.23-2.10.x86_64 Solution 1: deinstallation of busybox-hostname-1.35.0-21.2.noarch Solution 2: do not install hostname-3.23-2.10.x86_64
Choose from above solutions by number or cancel [1/2/c/d/?] (c):
I replaced busybox-hostname with hostname, as it is on my other MicroOS machines, and the "zypper dup" worked fine after that. Not sure why this machine had it, but it was installed way after the other ones and was installed with SELINUX enabled.
Kind Regards, Johannes
-- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de
B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
-- Thorsten Kukuk, Distinguished Engineer, Senior Architect SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Ivo Totev (HRB 36809, AG Nürnberg)

Moin, Am Montag, 14. März 2022, 11:57:39 CET schrieb Thorsten Kukuk:
On Mon, Mar 14, Johannes Kastl wrote:
Hi everyone,
not sure if this was reported already, if not I can open a bugzilla if needed.
I just noticed that one of my openSUSE MicroOS machines was not updating automatically anymore.
Seems like an update for dhcp-client-4.4.2.P1-7.3.x86_64 makes manual intervention necessary:
Problem: the to be installed dhcp-client-4.4.2.P1-7.3.x86_64 requires 'hostname', but this requirement cannot be provided not installable providers: hostname-3.23-2.10.i586[repo-oss] hostname-3.23-2.10.x86_64[repo-oss] Solution 1: deinstallation of busybox-hostname-1.35.0-21.2.noarch Solution 2: deinstallation of patterns-microos-base-5.0-44.1.x86_64 Solution 3: keep obsolete patterns-microos-base-5.0-44.1.x86_64 Solution 4: break dhcp-client-4.4.2.P1-7.3.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c):
Seems like it requires the "hostname" package, that is not installable as it conflicts with "busybox-hostname":
Bug in dhcp-client, it should require /usr/bin/hostname or so and not a package name. I'm pretty sure I fixed that already in some point in the past..
This is nevertheless something that we need to deal with sooner or later - at some point there will be some package which requires the "full" version of something instead of the busybox version, and the resulting switch shouldn't cause such a scary message and need manual intervention. Actually, this already broke building MicroOS (and probably other) images outside of OBS, because during the bootstrap phase zypper perferred the busybox variants, but then installing the rest of the packages conflicted wih the busybox variant. In OBS this doesn't happen because it's all solved in one go. I don't think we can fix this with the current packaging tools we have, so that is definitely something that needs to be more widely discussed. Cheers, Fabian
Thorsten
Problem: the installed busybox-hostname-1.35.0-21.2.noarch conflicts with 'hostname' provided by the to be installed hostname-3.23-2.10.x86_64 Solution 1: deinstallation of busybox-hostname-1.35.0-21.2.noarch Solution 2: do not install hostname-3.23-2.10.x86_64
Choose from above solutions by number or cancel [1/2/c/d/?] (c):
I replaced busybox-hostname with hostname, as it is on my other MicroOS machines, and the "zypper dup" worked fine after that. Not sure why this machine had it, but it was installed way after the other ones and was installed with SELINUX enabled.
Kind Regards, Johannes

On Mon, 2022-03-14 at 10:49 +0100, Johannes Kastl wrote:
I replaced busybox-hostname with hostname, as it is on my other MicroOS machines, and the "zypper dup" worked fine after that. Not sure why this machine had it, but it was installed way after the other ones and was installed with SELINUX enabled.
As an aside..I avoided hitting this problem on all my MicroOS hosts because I would never install dhcp-server on the host and always use our official dhcp-server container instead registry.opensuse.org/opensuse/dhcp-server:latest https://build.opensuse.org/package/view_file/openSUSE:Factory/opensuse-dhcp-... for a how-to-use guide Doesn't help you much immediately now..but figured it was worth noting given the goal of MicroOS is to avoid additional system packages as much as possible in order to avoid stuff like this happening. Regards, -- Richard Brown Linux Distribution Engineer - Future Technology Team SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuremberg, Germany (HRB 36809, AG Nürnberg) Managing Director/Geschäftsführer: Ivo Totev

Hi Richard, On 14.03.22 at 12:06 Richard Brown wrote:
On Mon, 2022-03-14 at 10:49 +0100, Johannes Kastl wrote:
[dhcp-client upgrade]
As an aside..I avoided hitting this problem on all my MicroOS hosts because I would never install dhcp-server on the host and always use
I agree, but in this case it was the **dhcp-client**, not the server. :-) Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

I have filed a bug report on Bugzilla regarding this issue: https://bugzilla.opensuse.org/show_bug.cgi?id=1197087
participants (5)
-
Fabian Vogt
-
Johannes Kastl
-
Lukas Mayer
-
Richard Brown
-
Thorsten Kukuk