This problem still exists in the Hardy package (0.24.4-3 at this moment). The upstream bug that is being linked to is a different one and has been fixed in 0.24.2. The linked bug is about a situation where the puppetmaster refuses the connection, the problem I am reporting is a situation where the name puppet cannot be resolved.
Effectively this means that the packages puppet and network-manager are conflicting. Puppet will be started while network-manager has not finished configuring yet so the name "puppet" can't be resolved and the client will exit. -- puppet client always exits on startup https://bugs.launchpad.net/bugs/176113 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
