I think the git issues were a scheduled maintenance right? Anyway, while this is borderline between bug/feature I agree that it should have very low regression potential and OTOH will help people.
So +1 on going forward with that. ** Description changed: [Impact] - * Despite libvirt having been compiled with libnss_libvirt_guest + * Despite libvirt having been compiled with libnss_libvirt_guest support, it only includes libnss_libvirt.so.2 shared library. With that, one that would like to use "libvirt_guest" as an entry in /etc/nsswitch.conf, to resolve hostnames (being the same as the virtual machine names) won't be able to. [Test Case] - * Create a virtual machine called "test" with hostname "untested" - * Make sure this virtual machine is attached to "default" network - * Make sure the "default" network offers DHCP addresses - * Edit /etc/nsswitch.conf: - ... - hosts: files libvirt dns - ... - * Confirm you're able to resolve "untested": ping untested - * Edit /etc/nsswitch.conf and change to: - ... - hosts: files libvirt_guest dns - ... - * You won't be able to resolve "test" (virtual machine name) + * Create a virtual machine called "test" with hostname "untested" + * Make sure this virtual machine is attached to "default" network + * Make sure the "default" network offers DHCP addresses + * Edit /etc/nsswitch.conf: + ... + hosts: files libvirt dns + ... + * Confirm you're able to resolve "untested": ping untested + * Edit /etc/nsswitch.conf and change to: + ... + hosts: files libvirt_guest dns + ... + * You won't be able to resolve "test" (virtual machine name) [Regression Potential] - * This change only includes a missing shared library in package libnss- + * This change only includes a missing shared library in package libnss- libvirt package. No code change: regressions could happen during package - building most likely. + building most likely. The lib is not used until you change nsswitch.conf [Other Info] Following the guidelines at: https://libvirt.org/nss.html I realized that we should be including libnss_libvirt.so.2 (as we are) and ALSO libnss_libvirt_guest.so.2 (not included) in the libnss-libvirt package. With that file missing, we can't solve libvirt machine names when changing nsswitch.conf "hosts" entry to "libvirt_guest" and we rely only in solving the guest hostname with "libvirt" only. ** Description changed: [Impact] - * Despite libvirt having been compiled with libnss_libvirt_guest - support, it only includes libnss_libvirt.so.2 shared library. With that, - one that would like to use "libvirt_guest" as an entry in - /etc/nsswitch.conf, to resolve hostnames (being the same as the virtual - machine names) won't be able to. + * Despite libvirt having been compiled with libnss_libvirt_guest support, + it only includes libnss_libvirt.so.2 shared library. With that, one + that would like to use "libvirt_guest" as an entry in + /etc/nsswitch.conf, to resolve hostnames (being the same as the virtual + machine names) won't be able to. [Test Case] - * Create a virtual machine called "test" with hostname "untested" - * Make sure this virtual machine is attached to "default" network + * Create a virtual machine called "test-guestname" with hostname + "test-hostname" + it is important that guestname and hostname differ. + * Make sure this virtual machine is attached to "default" network + (Default config) * Make sure the "default" network offers DHCP addresses + (Default config) * Edit /etc/nsswitch.conf: ... + # mode to resolve hostnames hosts: files libvirt dns ... - * Confirm you're able to resolve "untested": ping untested + * Confirm you're able to resolve "test-hostname": ping untested * Edit /etc/nsswitch.conf and change to: ... + # mode to resolve guestnames hosts: files libvirt_guest dns ... - * You won't be able to resolve "test" (virtual machine name) + * You won't be able to resolve "test-guestname" (virtual machine name) + * With the fix installed the latter will work as well [Regression Potential] * This change only includes a missing shared library in package libnss- - libvirt package. No code change: regressions could happen during package - building most likely. The lib is not used until you change nsswitch.conf + libvirt package. No code change: regressions could happen during + package building most likely. One might think "oh due to the install + now names will resolve differently", but they are not as the lib is not + used until you change nsswitch.conf as outlined above. [Other Info] Following the guidelines at: https://libvirt.org/nss.html I realized that we should be including libnss_libvirt.so.2 (as we are) and ALSO libnss_libvirt_guest.so.2 (not included) in the libnss-libvirt package. With that file missing, we can't solve libvirt machine names when changing nsswitch.conf "hosts" entry to "libvirt_guest" and we rely only in solving the guest hostname with "libvirt" only. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853074 Title: libnss-libvirt does not include libnss_libvirt_guest.so for nsswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1853074/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
