Hi Graham, thanks for reporting your issue, sorry you're having problems. First, this is not an apparmor issue; likely it's an issue with sssd (so adjusting there).
Second, sssd in trusty did have an update published for it on 15 March 2017 https://launchpad.net/ubuntu/+source/sssd/1.11.8-0ubuntu0.5 (an update from https://launchpad.net/ubuntu/+source/sssd/1.11.8-0ubuntu0.3), so perhaps your previous successful deployment was before that update made it out. There was also a recent glibc security update released, but that did not touch locale processing code directly. It would be good to verify that reverting to https://launchpad.net/ubuntu/+source/eglibc/2.19-0ubuntu6.9 does not address the issue. The primary commits referenced in the upstream bug report are (for sssd 1.13 branch): https://pagure.io/SSSD/sssd/c/4815471669a25566f6772c228c104a206ffa37f7?branch=sssd-1-13 https://pagure.io/SSSD/sssd/c/76ab3eb947f4d6fe6555d8ea0ae97dc3966f02ac?branch=sssd-1-13 ** Package changed: apparmor (Ubuntu) => sssd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1675118 Title: Setting locale breaks sss_ssh_authorizedkeys: set_locale() failed (5): Input/output error Status in sssd package in Ubuntu: New Bug description: Configure an Ubuntu Trusty machine with sssd against an LDAP domain. This fails as follows: ubuntu@bastion01:~$ /usr/bin/sss_ssh_authorizedkeys [username] (Wed Mar 22 17:46:15:940434 2017) [/usr/bin/sss_ssh_authorizedkeys] [main] (0x0020): set_locale() failed (5): Input/output error Error setting the locale Further login with LDAP users is impossible. This appears to be a recent regression, a similar machine was deployed on 15 March 2017 using the same orchestration and same configuration without a problem. ubuntu@bastion01:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.5 LTS Release: 14.04 Codename: trusty It looks like this bug or a bug similar to this was fixed in sssd recently, but this doesn't explain the sudden unexpected failure: https://pagure.io/SSSD/sssd/issue/2785 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1675118/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
