[Bug 1313595] [NEW] [SRU] Puppet master fails with 'stack level too deep' error when storeconfigs = true
Public bug reported: [IMPACT] * puppet setup with storeconfig activated * On client run, master fail with stack level too deep error, and client do no apply any of its manifests * not all clients are affected, but if one client is failing it will fail forever * This issue is known and fixed on upsteam, https://tickets.puppetlabs.com/browse/PUP-1064 [TESTCASE] To reproduce this issue, you need a puppet master with storeconfig=true running on Ubuntu Trusty. Apply the rules with puppet agent -t Without fix, you may face an stack level too deep, with fix, manifests should be applied as expected. [REGRESSION POTENTIAL] Minimal, fix is upstream and applied in new puppet versions. On our side, we have validated the fix since once week on a 500 machines setup and this error does not occur anymore. ** Affects: puppet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1313595 Title: [SRU] Puppet master fails with 'stack level too deep' error when storeconfigs = true To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1313595/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1313595] Re: [SRU] Puppet master fails with 'stack level too deep' error when storeconfigs = true
Attached debdiff integrating upstream fix for trusty. Issue is fixed in Utopic (puppet 3.5.1) ** Patch added: puppet_3.4.3-1ubuntu0.1.debdiff https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1313595/+attachment/4099292/+files/puppet_3.4.3-1ubuntu0.1.debdiff ** Changed in: puppet (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1313595 Title: [SRU] Puppet master fails with 'stack level too deep' error when storeconfigs = true To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1313595/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1026570] Re: slapd has random connection failures related to do_extended: protocol version (2) too low
*** This bug is a duplicate of bug 1023025 *** https://bugs.launchpad.net/bugs/1023025 ** This bug has been marked a duplicate of bug 1023025 search fail with get_ctrls : controls require LDAPv3 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1026570 Title: slapd has random connection failures related to do_extended: protocol version (2) too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1026570/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1023025] Re: search fail with get_ctrls : controls require LDAPv3
** Changed in: openldap (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1023025 Title: search fail with get_ctrls : controls require LDAPv3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1023025/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 581813] [NEW] nmbd not starting in lucid (after a migration)
Public bug reported: Binary package hint: samba In lucid upgraded from hardy, my nmbd daemon does not start (neither with service nmbd start or calling /etc/init.d script). It seems that the upstart job is doing the following test to ensure netbios is enabled: testparm -s --parameter-name='disable netbios' 2/dev/null But, testparm now resides in samba-common-bin which is only a recommends from samba-common, thus not installed during an upgrade. Installing by hand samba-common-bin make nmbd correctly start with the upstart job. ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- nmbd not starting in lucid (after a migration) https://bugs.launchpad.net/bugs/581813 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 423252] Re: NSS using LDAP on Karmic breaks 'su' and 'sudo'
If I can try to summarize the situation on this bug: - This is a regression from hardy. This use to work on hardy. - We document using tls for LDAP authentication in the server guide The most annoying point IMHO, is that someone who has root access to his server with a LDAP account with sudo, will not be able to get root access after upgrading. If we are not able to fix this before release (which is highly probable considering where we are in the release cycle), I think it worth some words in the release notes. -- NSS using LDAP on Karmic breaks 'su' and 'sudo' https://bugs.launchpad.net/bugs/423252 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 329754] Re: Please sync ejabberd 2.0.3-1 (universe) from Debian experimental (main).
Hi Andrew, We do not include new package revisions in already released Ubuntu version. To get 2.0.3 in intrepid (or in hardy), you should fill a bug report on intrepid-backports. You can check the full process: https://help.ubuntu.com/community/UbuntuBackports#How to request new packages -- Please sync ejabberd 2.0.3-1 (universe) from Debian experimental (main). https://bugs.launchpad.net/bugs/329754 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 222804] Re: [SRU] fail2ban fails to start after reboot
The fix in fail2ban 0.8.2-2ubuntu0.1 works for me. Thanks. -- [SRU] fail2ban fails to start after reboot https://bugs.launchpad.net/bugs/222804 You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
