The MAAS config file gets changed by the packaging because at the time
MAAS did not support conf.d/ (and it does not currently support it
either). The packaging updates the config file (which it actually
shouldn't be doing, but it was the only way of solving the problem).
The problem was that if we were providing a new config quite constantly,
which meant that a new config file needed to be installed replacing the
older config, causing upgrades to fail because there was no way to
obtain the old password. This is not a simple packaging fix, at least,
at the time it wasn't and it required lots of hacky things (since we
were doing things we werent supposed by policy anyway)
Now, as I have expressed before, the Region needs to be able to notify
the Clusters about its password changes. It doesn't matter who changes
the password here, whether it is the user directly or the packaging, the
issue still remains and this should be fixed in MAAS and not just go for
a quick fix in packaging. This is a bug in MAAS.
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Status: New => Confirmed
** Changed in: maas
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Title:
Rabbit password is reset on every upgrade which forces lockstep
cluster restarts
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1300507/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
