debian-sys-maint password is unmanaged and inconsistent

Bug #1579731 reported by Mick Gregg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Percona Cluster Charm
Triaged
Medium
Unassigned
percona-cluster (Juju Charms Collection)
Invalid
Medium
Unassigned

Bug Description

The debian-sys-maint user password seems not to be managed by the charm, meaning it is left to the package and inconsistent in debian.cnf across nodes in a cluster.

In production, we see `/etc/logrotate.d/percona-xtradb-cluster-server-5.5` trying to use debian.cnf, and we have at least one custom admin script failing for trying to use the debian-sys-maint user.

Perhaps debian.cnf could be templated, and the passwwd could be generated and set with debconf.

Alternatively, if debian-sys-maint/debian.cnf use is deprecated, perhaps the charm could manage/remove/comment the deprecated file and uses (logrorate being the example here).

Revision history for this message
James Page (james-page) wrote :

Agree that is is really required - the package maintainer scripts also require that this is present and functional.

The act of clustering pxc means that only the bootstrap nodes debian-sys-maint entry is actually accurate - we should take control of this file as part of the charm and ensure that the value is accurate both in the file and the database across all units.

Changed in percona-cluster (Juju Charms Collection):
status: New → Triaged
importance: Undecided → Medium
James Page (james-page)
Changed in charm-percona-cluster:
importance: Undecided → Medium
status: New → Triaged
Changed in percona-cluster (Juju Charms Collection):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.