** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Title:
Rabbit password is reset on every upgrade which forces lockstep
cluster restarts
To
We'll SRU 1.7 once it's super-solid!
Mark
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Title:
Rabbit password is reset on every upgrade which forces lockstep
cluster
FYI neel, current version in 14.04.1 LTS (1.5.4+bzr2294-0ubuntu1.1) does
not seem include a fix for this. A backport (or SRU?) would be nice to
have for this. Or a ReleaseNotes entry at least.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I am getting an Error with Ubuntu 14.04 Server installed from downloaded
iso.
[2014-09-26 12:37:35,356: ERROR/Beat] beat: Connection error: timed out. Trying
again in 32.0 seconds...
[2014-09-26 12:37:35,357: ERROR/MainProcess] consumer: Cannot connect to
Hi neel,
unlikely. A timeout usually means a network connectivity problem. If it
were a password problem, you would get an immediate error and it would
say the credentials are incorrect.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** No longer affects: maas
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Title:
Rabbit password is reset on every upgrade which forces lockstep
cluster restarts
To manage
This bug was fixed in the package maas - 1.6.1+bzr2550-0ubuntu1
---
maas (1.6.1+bzr2550-0ubuntu1) utopic; urgency=medium
* New upstream bugfix release:
- Auto-link node MACs to Networks (LP: #1341619)
[ Julian Edwards ]
* debian/maas-region-controller.postinst: Don't
** Branch linked: lp:ubuntu/maas
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Title:
Rabbit password is reset on every upgrade which forces lockstep
cluster restarts
To
** Branch linked: lp:~andreserl/maas/packaging.trusty.lp1300507
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Title:
Rabbit password is reset on every upgrade which forces
** Branch linked: lp:~andreserl/maas/packaging_fix_1300507
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Title:
Rabbit password is reset on every upgrade which forces
** Branch linked: lp:~lutostag/maas/packaging+fix1300507
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Title:
Rabbit password is reset on every upgrade which forces lockstep
** Branch linked: lp:~lutostag/maas/packaging+fix1300507
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Title:
Rabbit password is reset on every upgrade which forces lockstep
I just hit it again -- on upgrading from 1.6rc1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Title:
Rabbit password is reset on every upgrade which forces lockstep
cluster
Same here on another machine. Rabbit was full of these:
=ERROR REPORT 12-Aug-2014::19:18:59 ===
closing AMQP connection 0.4488.0 (10.96.0.10:36895 - 10.96.0.10:5672):
{handshake_error,starting,0,
{amqp_error,access_refused,
AMQPLAIN login refused:
Found where it happens:
debian/maas-region-controller.postinst:95
Should only happen when creating a new user -- will have to find out why
the region-controller does not think it has a user already.
Will dive in further.
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Greg
Saw this as well, Latest in trusty - 1.6b6.
** Tags added: landscape
** Tags added: cloud-installer
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Title:
Rabbit password is
Why is the rabbit password changed anyway?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Title:
Rabbit password is reset on every upgrade which forces lockstep
cluster
On Tuesday 22 Jul 2014 10:47:09 you wrote:
Why is the rabbit password changed anyway?
Absolutely no idea, it seems pointless but Andres wrote that packaging code so
he may be able to explain.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
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
RabbitMQ will be going away this cycle, so we should avoid investing a
lot of time in an engineering fix for this.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Title:
Rabbit
Precisely why I was advocating a quick packaging fix. :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Title:
Rabbit password is reset on every upgrade which forces lockstep
Andres, I think we're going to have to agree to disagree on this one
then.
Changing the password during installation is about the worst time it can
be done as there is going to be some instability anyway. I do agree
that changes need to be conveyed to the clusters, but if the change is
made
@Julian,
As we previously discussed, the region needs to be able to tell the
cluster about the updated password so the cluster keeps making the
requests to rabbitmq without having to manually restart the cluster.
This needs to be fixed in MAAS core regardless of maas packaging changes
the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Setting Critical for Julian.
** Changed in: maas (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Title:
Rabbit password is reset
I consider this a critical bug, but I cannot set the priority on here.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Title:
Rabbit password is reset on every upgrade which
26 matches
Mail list logo
