| 2015-07-16 13:56:12 |
Ryan Beisner |
bug |
|
|
added bug |
| 2015-07-16 14:03:41 |
Ryan Beisner |
branch linked |
|
lp:~openstack-charmers/charms/trusty/rabbitmq-server/next |
|
| 2015-07-16 14:47:25 |
Ryan Beisner |
branch linked |
|
lp:~james-page/charms/trusty/rabbitmq-server/fixup-configure-nodename |
|
| 2015-07-16 17:03:06 |
Ryan Beisner |
summary |
rmq next charm: pkg install fails when reverse dns fails - Error: unable to connect to node 'rabbit@10-245-173-55': nodedown |
rmq next charm: pkg install fails when deployed to lxc |
|
| 2015-07-16 17:03:44 |
Ryan Beisner |
description |
rmq next charm: pkg install fails when reverse dns fails - Error: unable to connect to node 'rabbit@10-245-173-55': nodedown
I deployed two identical bundles, one with the rabbitmq-server stable charm branch, one with the next charm branch.
The deploy from stable charm succeeds even when reverse dns is not working.
However, the deploy from next charm fails when reverse dns is not working.
# juju status - next charm deploy (rmq config-changed hook fails):
http://paste.ubuntu.com/11887711/
# juju status - stable charm deploy (ok):
http://paste.ubuntu.com/11887714/
# config-changed fail output:
http://paste.ubuntu.com/11887729/
00:26:49.928 2015-07-16 03:19:35 INFO config-changed Error: unable to connect to node 'rabbit@10-245-173-55': nodedown
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed DIAGNOSTICS
00:26:49.928 2015-07-16 03:19:35 INFO config-changed ===========
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed nodes in question: ['rabbit@10-245-173-55']
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed hosts, their running nodes and ports:
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - 10-245-173-55: [{rabbit,46881},{rabbitmqctl7999,46649}]
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed current node details:
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - node name: 'rabbitmqctl7999@juju-machine-0-lxc-0'
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - home dir: /var/lib/rabbitmq
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - cookie hash: 0ooESjirIlf5aCmawq/iGQ==
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed Traceback (most recent call last):
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/config-changed", line 775, in <module>
00:26:49.928 2015-07-16 03:19:35 INFO config-changed hooks.execute(sys.argv)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/charmhelpers/core/hookenv.py", line 603, in execute
00:26:49.928 2015-07-16 03:19:35 INFO config-changed self._hooks[hook_name]()
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/charmhelpers/core/host.py", line 312, in wrapped_f
00:26:49.928 2015-07-16 03:19:35 INFO config-changed f(*args, **kwargs)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/config-changed", line 748, in config_changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed update_nrpe_checks()
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/config-changed", line 551, in update_nrpe_checks
00:26:49.928 2015-07-16 03:19:35 INFO config-changed rabbit.create_vhost(vhost)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/rabbit_utils.py", line 107, in create_vhost
00:26:49.928 2015-07-16 03:19:35 INFO config-changed subprocess.check_call(cmd)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/usr/lib/python2.7/subprocess.py", line 540, in check_call
00:26:49.928 2015-07-16 03:19:35 INFO config-changed raise CalledProcessError(retcode, cmd)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed subprocess.CalledProcessError: Command '['/usr/sbin/rabbitmqctl', 'add_vhost', 'nagios-rabbitmq-server-0']' returned non-zero exit status 2
00:26:49.928 2015-07-16 03:19:35 ERROR juju.worker.uniter.operation runhook.go:103 hook "config-changed" failed: exit status 1 |
The rabbitmq-server next charm works on bare metal but not in a container; the stable charm works fine on both.
## REPRODUCER:
To remove the surrounding complexity of OpenStack and bundles, here is a simplified approach to reproducing this bug.
juju bootstrap --constraints "arch=amd64 tags=uosci"
mkdir trusty
# grab next charm
bzr branch lp:~openstack-charmers/charms/trusty/rabbitmq-server/next trusty/rabbitmq-server
# grab next charm with proposed fix
bzr branch lp:~james-page/charms/trusty/rabbitmq-server/fixup-configure-nodename trusty/rabbitmq-server-fix1
# grab stable charm
bzr branch lp:charms/trusty/rabbitmq-server trusty/rabbitmq-server-stable
# Manually change "name:" to "rabbitmq-server-fix1" in trusty/rabbitmq-server-fix1/metadata.yaml.
# Manually change "name:" to "rabbitmq-server-stable" in trusty/rabbitmq-server-stable/metadata.yaml.
# Deploy next charm to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server
# Deploy next charm to bare metal (OK):
juju add-unit rabbitmq-server
# Deploy proposed charm fix to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-fix1 # fails
# Deploy proposed charm fix to bare metal (OK):
juju add-unit rabbitmq-server-fix1 # succeeds, causes rmq to install to bare metal, no lxc.
# Deploy stable charm to a container (OK):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-stable
# Deploy stable charm to bare metal (OK):
juju add-unit rabbitmq-server-stable
# juju stat after reproducer:
juju stat --format tabular
juju stat --format yaml
--> http://paste.ubuntu.com/11888683/
--- L
rmq next charm: pkg install fails when reverse dns fails - Error: unable to connect to node 'rabbit@10-245-173-55': nodedown
I deployed two identical bundles, one with the rabbitmq-server stable charm branch, one with the next charm branch.
The deploy from stable charm succeeds even when reverse dns is not working.
However, the deploy from next charm fails when reverse dns is not working.
# juju status - next charm deploy (rmq config-changed hook fails):
http://paste.ubuntu.com/11887711/
# juju status - stable charm deploy (ok):
http://paste.ubuntu.com/11887714/
# config-changed fail output:
http://paste.ubuntu.com/11887729/
00:26:49.928 2015-07-16 03:19:35 INFO config-changed Error: unable to connect to node 'rabbit@10-245-173-55': nodedown
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed DIAGNOSTICS
00:26:49.928 2015-07-16 03:19:35 INFO config-changed ===========
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed nodes in question: ['rabbit@10-245-173-55']
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed hosts, their running nodes and ports:
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - 10-245-173-55: [{rabbit,46881},{rabbitmqctl7999,46649}]
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed current node details:
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - node name: 'rabbitmqctl7999@juju-machine-0-lxc-0'
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - home dir: /var/lib/rabbitmq
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - cookie hash: 0ooESjirIlf5aCmawq/iGQ==
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed Traceback (most recent call last):
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/config-changed", line 775, in <module>
00:26:49.928 2015-07-16 03:19:35 INFO config-changed hooks.execute(sys.argv)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/charmhelpers/core/hookenv.py", line 603, in execute
00:26:49.928 2015-07-16 03:19:35 INFO config-changed self._hooks[hook_name]()
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/charmhelpers/core/host.py", line 312, in wrapped_f
00:26:49.928 2015-07-16 03:19:35 INFO config-changed f(*args, **kwargs)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/config-changed", line 748, in config_changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed update_nrpe_checks()
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/config-changed", line 551, in update_nrpe_checks
00:26:49.928 2015-07-16 03:19:35 INFO config-changed rabbit.create_vhost(vhost)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/rabbit_utils.py", line 107, in create_vhost
00:26:49.928 2015-07-16 03:19:35 INFO config-changed subprocess.check_call(cmd)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/usr/lib/python2.7/subprocess.py", line 540, in check_call
00:26:49.928 2015-07-16 03:19:35 INFO config-changed raise CalledProcessError(retcode, cmd)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed subprocess.CalledProcessError: Command '['/usr/sbin/rabbitmqctl', 'add_vhost', 'nagios-rabbitmq-server-0']' returned non-zero exit status 2
00:26:49.928 2015-07-16 03:19:35 ERROR juju.worker.uniter.operation runhook.go:103 hook "config-changed" failed: exit status 1 |
|
| 2015-07-16 17:04:10 |
Ryan Beisner |
description |
The rabbitmq-server next charm works on bare metal but not in a container; the stable charm works fine on both.
## REPRODUCER:
To remove the surrounding complexity of OpenStack and bundles, here is a simplified approach to reproducing this bug.
juju bootstrap --constraints "arch=amd64 tags=uosci"
mkdir trusty
# grab next charm
bzr branch lp:~openstack-charmers/charms/trusty/rabbitmq-server/next trusty/rabbitmq-server
# grab next charm with proposed fix
bzr branch lp:~james-page/charms/trusty/rabbitmq-server/fixup-configure-nodename trusty/rabbitmq-server-fix1
# grab stable charm
bzr branch lp:charms/trusty/rabbitmq-server trusty/rabbitmq-server-stable
# Manually change "name:" to "rabbitmq-server-fix1" in trusty/rabbitmq-server-fix1/metadata.yaml.
# Manually change "name:" to "rabbitmq-server-stable" in trusty/rabbitmq-server-stable/metadata.yaml.
# Deploy next charm to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server
# Deploy next charm to bare metal (OK):
juju add-unit rabbitmq-server
# Deploy proposed charm fix to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-fix1 # fails
# Deploy proposed charm fix to bare metal (OK):
juju add-unit rabbitmq-server-fix1 # succeeds, causes rmq to install to bare metal, no lxc.
# Deploy stable charm to a container (OK):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-stable
# Deploy stable charm to bare metal (OK):
juju add-unit rabbitmq-server-stable
# juju stat after reproducer:
juju stat --format tabular
juju stat --format yaml
--> http://paste.ubuntu.com/11888683/
--- L
rmq next charm: pkg install fails when reverse dns fails - Error: unable to connect to node 'rabbit@10-245-173-55': nodedown
I deployed two identical bundles, one with the rabbitmq-server stable charm branch, one with the next charm branch.
The deploy from stable charm succeeds even when reverse dns is not working.
However, the deploy from next charm fails when reverse dns is not working.
# juju status - next charm deploy (rmq config-changed hook fails):
http://paste.ubuntu.com/11887711/
# juju status - stable charm deploy (ok):
http://paste.ubuntu.com/11887714/
# config-changed fail output:
http://paste.ubuntu.com/11887729/
00:26:49.928 2015-07-16 03:19:35 INFO config-changed Error: unable to connect to node 'rabbit@10-245-173-55': nodedown
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed DIAGNOSTICS
00:26:49.928 2015-07-16 03:19:35 INFO config-changed ===========
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed nodes in question: ['rabbit@10-245-173-55']
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed hosts, their running nodes and ports:
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - 10-245-173-55: [{rabbit,46881},{rabbitmqctl7999,46649}]
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed current node details:
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - node name: 'rabbitmqctl7999@juju-machine-0-lxc-0'
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - home dir: /var/lib/rabbitmq
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - cookie hash: 0ooESjirIlf5aCmawq/iGQ==
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed Traceback (most recent call last):
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/config-changed", line 775, in <module>
00:26:49.928 2015-07-16 03:19:35 INFO config-changed hooks.execute(sys.argv)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/charmhelpers/core/hookenv.py", line 603, in execute
00:26:49.928 2015-07-16 03:19:35 INFO config-changed self._hooks[hook_name]()
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/charmhelpers/core/host.py", line 312, in wrapped_f
00:26:49.928 2015-07-16 03:19:35 INFO config-changed f(*args, **kwargs)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/config-changed", line 748, in config_changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed update_nrpe_checks()
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/config-changed", line 551, in update_nrpe_checks
00:26:49.928 2015-07-16 03:19:35 INFO config-changed rabbit.create_vhost(vhost)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/rabbit_utils.py", line 107, in create_vhost
00:26:49.928 2015-07-16 03:19:35 INFO config-changed subprocess.check_call(cmd)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/usr/lib/python2.7/subprocess.py", line 540, in check_call
00:26:49.928 2015-07-16 03:19:35 INFO config-changed raise CalledProcessError(retcode, cmd)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed subprocess.CalledProcessError: Command '['/usr/sbin/rabbitmqctl', 'add_vhost', 'nagios-rabbitmq-server-0']' returned non-zero exit status 2
00:26:49.928 2015-07-16 03:19:35 ERROR juju.worker.uniter.operation runhook.go:103 hook "config-changed" failed: exit status 1 |
The rabbitmq-server next charm works on bare metal but not in a container; the stable charm works fine on both.
## REPRODUCER:
To remove the surrounding complexity of OpenStack and bundles, here is a simplified approach to reproducing this bug.
juju bootstrap --constraints "arch=amd64 tags=uosci"
mkdir trusty
# grab next charm
bzr branch lp:~openstack-charmers/charms/trusty/rabbitmq-server/next trusty/rabbitmq-server
# grab next charm with proposed fix
bzr branch lp:~james-page/charms/trusty/rabbitmq-server/fixup-configure-nodename trusty/rabbitmq-server-fix1
# grab stable charm
bzr branch lp:charms/trusty/rabbitmq-server trusty/rabbitmq-server-stable
# Manually change "name:" to "rabbitmq-server-fix1" in trusty/rabbitmq-server-fix1/metadata.yaml.
# Manually change "name:" to "rabbitmq-server-stable" in trusty/rabbitmq-server-stable/metadata.yaml.
# Deploy next charm to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server
# Deploy next charm to bare metal (OK):
juju add-unit rabbitmq-server
# Deploy proposed charm fix to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-fix1 # fails
# Deploy proposed charm fix to bare metal (OK):
juju add-unit rabbitmq-server-fix1 # succeeds, causes rmq to install to bare metal, no lxc.
# Deploy stable charm to a container (OK):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-stable
# Deploy stable charm to bare metal (OK):
juju add-unit rabbitmq-server-stable
# juju stat after reproducer:
juju stat --format tabular
juju stat --format yaml
--> http://paste.ubuntu.com/11888683/
--- Original Bug Description ---
rmq next charm: pkg install fails when reverse dns fails - Error: unable to connect to node 'rabbit@10-245-173-55': nodedown
I deployed two identical bundles, one with the rabbitmq-server stable charm branch, one with the next charm branch.
The deploy from stable charm succeeds even when reverse dns is not working.
However, the deploy from next charm fails when reverse dns is not working.
# juju status - next charm deploy (rmq config-changed hook fails):
http://paste.ubuntu.com/11887711/
# juju status - stable charm deploy (ok):
http://paste.ubuntu.com/11887714/
# config-changed fail output:
http://paste.ubuntu.com/11887729/
00:26:49.928 2015-07-16 03:19:35 INFO config-changed Error: unable to connect to node 'rabbit@10-245-173-55': nodedown
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed DIAGNOSTICS
00:26:49.928 2015-07-16 03:19:35 INFO config-changed ===========
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed nodes in question: ['rabbit@10-245-173-55']
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed hosts, their running nodes and ports:
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - 10-245-173-55: [{rabbit,46881},{rabbitmqctl7999,46649}]
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed current node details:
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - node name: 'rabbitmqctl7999@juju-machine-0-lxc-0'
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - home dir: /var/lib/rabbitmq
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - cookie hash: 0ooESjirIlf5aCmawq/iGQ==
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed Traceback (most recent call last):
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/config-changed", line 775, in <module>
00:26:49.928 2015-07-16 03:19:35 INFO config-changed hooks.execute(sys.argv)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/charmhelpers/core/hookenv.py", line 603, in execute
00:26:49.928 2015-07-16 03:19:35 INFO config-changed self._hooks[hook_name]()
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/charmhelpers/core/host.py", line 312, in wrapped_f
00:26:49.928 2015-07-16 03:19:35 INFO config-changed f(*args, **kwargs)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/config-changed", line 748, in config_changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed update_nrpe_checks()
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/config-changed", line 551, in update_nrpe_checks
00:26:49.928 2015-07-16 03:19:35 INFO config-changed rabbit.create_vhost(vhost)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/rabbit_utils.py", line 107, in create_vhost
00:26:49.928 2015-07-16 03:19:35 INFO config-changed subprocess.check_call(cmd)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/usr/lib/python2.7/subprocess.py", line 540, in check_call
00:26:49.928 2015-07-16 03:19:35 INFO config-changed raise CalledProcessError(retcode, cmd)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed subprocess.CalledProcessError: Command '['/usr/sbin/rabbitmqctl', 'add_vhost', 'nagios-rabbitmq-server-0']' returned non-zero exit status 2
00:26:49.928 2015-07-16 03:19:35 ERROR juju.worker.uniter.operation runhook.go:103 hook "config-changed" failed: exit status 1 |
|
| 2015-07-16 17:17:20 |
Ryan Beisner |
attachment added |
|
0-var-log.bz2 https://bugs.launchpad.net/charms/+source/rabbitmq-server/+bug/1475320/+attachment/4430151/+files/0-var-log.bz2 |
|
| 2015-07-16 17:17:34 |
Ryan Beisner |
attachment added |
|
1-var-log.bz2 https://bugs.launchpad.net/charms/+source/rabbitmq-server/+bug/1475320/+attachment/4430152/+files/1-var-log.bz2 |
|
| 2015-07-16 17:17:44 |
Ryan Beisner |
attachment added |
|
2-var-log.bz2 https://bugs.launchpad.net/charms/+source/rabbitmq-server/+bug/1475320/+attachment/4430153/+files/2-var-log.bz2 |
|
| 2015-07-16 17:18:17 |
Ryan Beisner |
attachment added |
|
3-var-log.bz2 https://bugs.launchpad.net/charms/+source/rabbitmq-server/+bug/1475320/+attachment/4430154/+files/3-var-log.bz2 |
|
| 2015-07-16 17:26:42 |
Ryan Beisner |
description |
The rabbitmq-server next charm works on bare metal but not in a container; the stable charm works fine on both.
## REPRODUCER:
To remove the surrounding complexity of OpenStack and bundles, here is a simplified approach to reproducing this bug.
juju bootstrap --constraints "arch=amd64 tags=uosci"
mkdir trusty
# grab next charm
bzr branch lp:~openstack-charmers/charms/trusty/rabbitmq-server/next trusty/rabbitmq-server
# grab next charm with proposed fix
bzr branch lp:~james-page/charms/trusty/rabbitmq-server/fixup-configure-nodename trusty/rabbitmq-server-fix1
# grab stable charm
bzr branch lp:charms/trusty/rabbitmq-server trusty/rabbitmq-server-stable
# Manually change "name:" to "rabbitmq-server-fix1" in trusty/rabbitmq-server-fix1/metadata.yaml.
# Manually change "name:" to "rabbitmq-server-stable" in trusty/rabbitmq-server-stable/metadata.yaml.
# Deploy next charm to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server
# Deploy next charm to bare metal (OK):
juju add-unit rabbitmq-server
# Deploy proposed charm fix to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-fix1 # fails
# Deploy proposed charm fix to bare metal (OK):
juju add-unit rabbitmq-server-fix1 # succeeds, causes rmq to install to bare metal, no lxc.
# Deploy stable charm to a container (OK):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-stable
# Deploy stable charm to bare metal (OK):
juju add-unit rabbitmq-server-stable
# juju stat after reproducer:
juju stat --format tabular
juju stat --format yaml
--> http://paste.ubuntu.com/11888683/
--- Original Bug Description ---
rmq next charm: pkg install fails when reverse dns fails - Error: unable to connect to node 'rabbit@10-245-173-55': nodedown
I deployed two identical bundles, one with the rabbitmq-server stable charm branch, one with the next charm branch.
The deploy from stable charm succeeds even when reverse dns is not working.
However, the deploy from next charm fails when reverse dns is not working.
# juju status - next charm deploy (rmq config-changed hook fails):
http://paste.ubuntu.com/11887711/
# juju status - stable charm deploy (ok):
http://paste.ubuntu.com/11887714/
# config-changed fail output:
http://paste.ubuntu.com/11887729/
00:26:49.928 2015-07-16 03:19:35 INFO config-changed Error: unable to connect to node 'rabbit@10-245-173-55': nodedown
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed DIAGNOSTICS
00:26:49.928 2015-07-16 03:19:35 INFO config-changed ===========
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed nodes in question: ['rabbit@10-245-173-55']
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed hosts, their running nodes and ports:
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - 10-245-173-55: [{rabbit,46881},{rabbitmqctl7999,46649}]
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed current node details:
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - node name: 'rabbitmqctl7999@juju-machine-0-lxc-0'
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - home dir: /var/lib/rabbitmq
00:26:49.928 2015-07-16 03:19:35 INFO config-changed - cookie hash: 0ooESjirIlf5aCmawq/iGQ==
00:26:49.928 2015-07-16 03:19:35 INFO config-changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed Traceback (most recent call last):
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/config-changed", line 775, in <module>
00:26:49.928 2015-07-16 03:19:35 INFO config-changed hooks.execute(sys.argv)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/charmhelpers/core/hookenv.py", line 603, in execute
00:26:49.928 2015-07-16 03:19:35 INFO config-changed self._hooks[hook_name]()
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/charmhelpers/core/host.py", line 312, in wrapped_f
00:26:49.928 2015-07-16 03:19:35 INFO config-changed f(*args, **kwargs)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/config-changed", line 748, in config_changed
00:26:49.928 2015-07-16 03:19:35 INFO config-changed update_nrpe_checks()
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/config-changed", line 551, in update_nrpe_checks
00:26:49.928 2015-07-16 03:19:35 INFO config-changed rabbit.create_vhost(vhost)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/var/lib/juju/agents/unit-rabbitmq-server-0/charm/hooks/rabbit_utils.py", line 107, in create_vhost
00:26:49.928 2015-07-16 03:19:35 INFO config-changed subprocess.check_call(cmd)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed File "/usr/lib/python2.7/subprocess.py", line 540, in check_call
00:26:49.928 2015-07-16 03:19:35 INFO config-changed raise CalledProcessError(retcode, cmd)
00:26:49.928 2015-07-16 03:19:35 INFO config-changed subprocess.CalledProcessError: Command '['/usr/sbin/rabbitmqctl', 'add_vhost', 'nagios-rabbitmq-server-0']' returned non-zero exit status 2
00:26:49.928 2015-07-16 03:19:35 ERROR juju.worker.uniter.operation runhook.go:103 hook "config-changed" failed: exit status 1 |
The rabbitmq-server next charm works on bare metal but not in a container; the stable charm works fine on both.
## REPRODUCER:
To remove the surrounding complexity of OpenStack and bundles, here is a simplified approach to reproducing this bug.
juju bootstrap --constraints "arch=amd64 tags=uosci"
mkdir trusty
# grab next charm
bzr branch lp:~openstack-charmers/charms/trusty/rabbitmq-server/next trusty/rabbitmq-server
# grab next charm with proposed fix
bzr branch lp:~james-page/charms/trusty/rabbitmq-server/fixup-configure-nodename trusty/rabbitmq-server-fix1
# grab stable charm
bzr branch lp:charms/trusty/rabbitmq-server trusty/rabbitmq-server-stable
# Manually change "name:" to "rabbitmq-server-fix1" in trusty/rabbitmq-server-fix1/metadata.yaml.
# Manually change "name:" to "rabbitmq-server-stable" in trusty/rabbitmq-server-stable/metadata.yaml.
# Deploy next charm to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server
# Deploy next charm to bare metal (OK):
juju add-unit rabbitmq-server
# Deploy proposed charm fix to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-fix1 # fails
# Deploy proposed charm fix to bare metal (OK):
juju add-unit rabbitmq-server-fix1 # succeeds, causes rmq to install to bare metal, no lxc.
# Deploy stable charm to a container (OK):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-stable
# Deploy stable charm to bare metal (OK):
juju add-unit rabbitmq-server-stable
# juju stat after reproducer:
juju stat --format tabular
juju stat --format yaml
SEE --> http://paste.ubuntu.com/11888683/
# juju version:
jenkins@juju-osci-machine-13:~/bzr⟫ apt-cache policy juju
juju:
Installed: 1.24.2-0ubuntu1~14.04.1~juju1
Candidate: 1.24.2-0ubuntu1~14.04.1~juju1
Version table:
*** 1.24.2-0ubuntu1~14.04.1~juju1 0
500 http://ppa.launchpad.net/juju/stable/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
1.20.11-0ubuntu0.14.04.1 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages
1.18.1-0ubuntu1 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
# maas version:
ubuntu@lescina:~$ apt-cache policy maas
maas:
Installed: 1.8.0+bzr4001-0ubuntu2~trusty1
Candidate: 1.8.0+bzr4001-0ubuntu2~trusty1
Version table:
*** 1.8.0+bzr4001-0ubuntu2~trusty1 0
500 http://ppa.launchpad.net/maas-maintainers/experimental/ubuntu/ trusty/main amd64 Packages
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
1.5.4+bzr2294-0ubuntu1.3 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
1.5.4+bzr2294-0ubuntu1.2 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
1.5+bzr2252-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
You have new mail in /var/mail/ubuntu |
|
| 2015-07-16 17:46:52 |
Ryan Beisner |
description |
The rabbitmq-server next charm works on bare metal but not in a container; the stable charm works fine on both.
## REPRODUCER:
To remove the surrounding complexity of OpenStack and bundles, here is a simplified approach to reproducing this bug.
juju bootstrap --constraints "arch=amd64 tags=uosci"
mkdir trusty
# grab next charm
bzr branch lp:~openstack-charmers/charms/trusty/rabbitmq-server/next trusty/rabbitmq-server
# grab next charm with proposed fix
bzr branch lp:~james-page/charms/trusty/rabbitmq-server/fixup-configure-nodename trusty/rabbitmq-server-fix1
# grab stable charm
bzr branch lp:charms/trusty/rabbitmq-server trusty/rabbitmq-server-stable
# Manually change "name:" to "rabbitmq-server-fix1" in trusty/rabbitmq-server-fix1/metadata.yaml.
# Manually change "name:" to "rabbitmq-server-stable" in trusty/rabbitmq-server-stable/metadata.yaml.
# Deploy next charm to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server
# Deploy next charm to bare metal (OK):
juju add-unit rabbitmq-server
# Deploy proposed charm fix to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-fix1 # fails
# Deploy proposed charm fix to bare metal (OK):
juju add-unit rabbitmq-server-fix1 # succeeds, causes rmq to install to bare metal, no lxc.
# Deploy stable charm to a container (OK):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-stable
# Deploy stable charm to bare metal (OK):
juju add-unit rabbitmq-server-stable
# juju stat after reproducer:
juju stat --format tabular
juju stat --format yaml
SEE --> http://paste.ubuntu.com/11888683/
# juju version:
jenkins@juju-osci-machine-13:~/bzr⟫ apt-cache policy juju
juju:
Installed: 1.24.2-0ubuntu1~14.04.1~juju1
Candidate: 1.24.2-0ubuntu1~14.04.1~juju1
Version table:
*** 1.24.2-0ubuntu1~14.04.1~juju1 0
500 http://ppa.launchpad.net/juju/stable/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
1.20.11-0ubuntu0.14.04.1 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages
1.18.1-0ubuntu1 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
# maas version:
ubuntu@lescina:~$ apt-cache policy maas
maas:
Installed: 1.8.0+bzr4001-0ubuntu2~trusty1
Candidate: 1.8.0+bzr4001-0ubuntu2~trusty1
Version table:
*** 1.8.0+bzr4001-0ubuntu2~trusty1 0
500 http://ppa.launchpad.net/maas-maintainers/experimental/ubuntu/ trusty/main amd64 Packages
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
1.5.4+bzr2294-0ubuntu1.3 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
1.5.4+bzr2294-0ubuntu1.2 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
1.5+bzr2252-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
You have new mail in /var/mail/ubuntu |
The rabbitmq-server next charm works on bare metal but not in a container; the stable charm works fine on both.
## REPRODUCER:
To remove the surrounding complexity of OpenStack and bundles, here is a simplified approach to reproducing this bug.
juju bootstrap --constraints "arch=amd64 tags=uosci"
mkdir trusty
# grab next charm
bzr branch lp:~openstack-charmers/charms/trusty/rabbitmq-server/next trusty/rabbitmq-server
# grab next charm with proposed fix
bzr branch lp:~james-page/charms/trusty/rabbitmq-server/fixup-configure-nodename trusty/rabbitmq-server-fix1
# grab stable charm
bzr branch lp:charms/trusty/rabbitmq-server trusty/rabbitmq-server-stable
# Manually change "name:" to "rabbitmq-server-fix1" in trusty/rabbitmq-server-fix1/metadata.yaml.
# Manually change "name:" to "rabbitmq-server-stable" in trusty/rabbitmq-server-stable/metadata.yaml.
# Deploy next charm to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server
# Deploy next charm to bare metal (OK):
juju add-unit rabbitmq-server
# Deploy proposed charm fix to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-fix1 # fails
# Deploy proposed charm fix to bare metal (OK):
juju add-unit rabbitmq-server-fix1 # succeeds, causes rmq to install to bare metal, no lxc.
# Deploy stable charm to a container (OK):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-stable
# Deploy stable charm to bare metal (OK):
juju add-unit rabbitmq-server-stable
# juju stat after reproducer:
juju stat --format tabular
juju stat --format yaml
SEE --> http://paste.ubuntu.com/11888683/
## RESULTANT CONFS:
jenkins@juju-osci-machine-13:~/bzr⟫ juju run --all "cat /etc/rabbitmq/rabbitmq-env.conf"
# ignore 0
- MachineId: "0"
Stderr: "Warning: Permanently added '10.245.168.11' (ECDSA) to the list of known
hosts.\r\ncat: /etc/rabbitmq/rabbitmq-env.conf: No such file or directory\n"
# next charm in lxc
- MachineId: 0/lxc/0
RABBITMQ_NODENAME=rabbit@10-245-173-99
# proposed fix charm in lxc
- MachineId: 0/lxc/1
RABBITMQ_NODENAME=rabbit@10-245-173-100
# stable charm in lxc
- MachineId: 0/lxc/2
RABBITMQ_NODENAME=rabbit@10-245-173-101
# next charm on bare metal
- MachineId: "1"
RABBITMQ_NODENAME=rabbit@fat-machine
# proposed fix charm on bare metal
- MachineId: "2"
RABBITMQ_NODENAME=rabbit@cylindrical-base
# stable charm on bare metal
- MachineId: "3"
RABBITMQ_NODENAME=rabbit@grizzled-family
## JUJU/MAAS VERSION INFO:
# juju version:
jenkins@juju-osci-machine-13:~/bzr⟫ apt-cache policy juju
juju:
Installed: 1.24.2-0ubuntu1~14.04.1~juju1
Candidate: 1.24.2-0ubuntu1~14.04.1~juju1
Version table:
*** 1.24.2-0ubuntu1~14.04.1~juju1 0
500 http://ppa.launchpad.net/juju/stable/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
1.20.11-0ubuntu0.14.04.1 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages
1.18.1-0ubuntu1 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
# maas version:
ubuntu@lescina:~$ apt-cache policy maas
maas:
Installed: 1.8.0+bzr4001-0ubuntu2~trusty1
Candidate: 1.8.0+bzr4001-0ubuntu2~trusty1
Version table:
*** 1.8.0+bzr4001-0ubuntu2~trusty1 0
500 http://ppa.launchpad.net/maas-maintainers/experimental/ubuntu/ trusty/main amd64 Packages
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
1.5.4+bzr2294-0ubuntu1.3 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
1.5.4+bzr2294-0ubuntu1.2 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
1.5+bzr2252-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
You have new mail in /var/mail/ubuntu |
|
| 2015-07-16 18:09:59 |
Ryan Beisner |
description |
The rabbitmq-server next charm works on bare metal but not in a container; the stable charm works fine on both.
## REPRODUCER:
To remove the surrounding complexity of OpenStack and bundles, here is a simplified approach to reproducing this bug.
juju bootstrap --constraints "arch=amd64 tags=uosci"
mkdir trusty
# grab next charm
bzr branch lp:~openstack-charmers/charms/trusty/rabbitmq-server/next trusty/rabbitmq-server
# grab next charm with proposed fix
bzr branch lp:~james-page/charms/trusty/rabbitmq-server/fixup-configure-nodename trusty/rabbitmq-server-fix1
# grab stable charm
bzr branch lp:charms/trusty/rabbitmq-server trusty/rabbitmq-server-stable
# Manually change "name:" to "rabbitmq-server-fix1" in trusty/rabbitmq-server-fix1/metadata.yaml.
# Manually change "name:" to "rabbitmq-server-stable" in trusty/rabbitmq-server-stable/metadata.yaml.
# Deploy next charm to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server
# Deploy next charm to bare metal (OK):
juju add-unit rabbitmq-server
# Deploy proposed charm fix to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-fix1 # fails
# Deploy proposed charm fix to bare metal (OK):
juju add-unit rabbitmq-server-fix1 # succeeds, causes rmq to install to bare metal, no lxc.
# Deploy stable charm to a container (OK):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-stable
# Deploy stable charm to bare metal (OK):
juju add-unit rabbitmq-server-stable
# juju stat after reproducer:
juju stat --format tabular
juju stat --format yaml
SEE --> http://paste.ubuntu.com/11888683/
## RESULTANT CONFS:
jenkins@juju-osci-machine-13:~/bzr⟫ juju run --all "cat /etc/rabbitmq/rabbitmq-env.conf"
# ignore 0
- MachineId: "0"
Stderr: "Warning: Permanently added '10.245.168.11' (ECDSA) to the list of known
hosts.\r\ncat: /etc/rabbitmq/rabbitmq-env.conf: No such file or directory\n"
# next charm in lxc
- MachineId: 0/lxc/0
RABBITMQ_NODENAME=rabbit@10-245-173-99
# proposed fix charm in lxc
- MachineId: 0/lxc/1
RABBITMQ_NODENAME=rabbit@10-245-173-100
# stable charm in lxc
- MachineId: 0/lxc/2
RABBITMQ_NODENAME=rabbit@10-245-173-101
# next charm on bare metal
- MachineId: "1"
RABBITMQ_NODENAME=rabbit@fat-machine
# proposed fix charm on bare metal
- MachineId: "2"
RABBITMQ_NODENAME=rabbit@cylindrical-base
# stable charm on bare metal
- MachineId: "3"
RABBITMQ_NODENAME=rabbit@grizzled-family
## JUJU/MAAS VERSION INFO:
# juju version:
jenkins@juju-osci-machine-13:~/bzr⟫ apt-cache policy juju
juju:
Installed: 1.24.2-0ubuntu1~14.04.1~juju1
Candidate: 1.24.2-0ubuntu1~14.04.1~juju1
Version table:
*** 1.24.2-0ubuntu1~14.04.1~juju1 0
500 http://ppa.launchpad.net/juju/stable/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
1.20.11-0ubuntu0.14.04.1 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages
1.18.1-0ubuntu1 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
# maas version:
ubuntu@lescina:~$ apt-cache policy maas
maas:
Installed: 1.8.0+bzr4001-0ubuntu2~trusty1
Candidate: 1.8.0+bzr4001-0ubuntu2~trusty1
Version table:
*** 1.8.0+bzr4001-0ubuntu2~trusty1 0
500 http://ppa.launchpad.net/maas-maintainers/experimental/ubuntu/ trusty/main amd64 Packages
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
1.5.4+bzr2294-0ubuntu1.3 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
1.5.4+bzr2294-0ubuntu1.2 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
1.5+bzr2252-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
You have new mail in /var/mail/ubuntu |
The rabbitmq-server next charm works on bare metal but not in a container; the stable charm works fine on both.
ERROR: node with name "rabbit" already running on "10-245-173-99"
DIAGNOSTICS
===========
nodes in question: ['rabbit@10-245-173-99']
hosts, their running nodes and ports:
- 10-245-173-99: [{rabbit,44415},
{rabbitmqctl11575,47036},
{rabbitmqprelaunch11590,41368}]
current node details:
- node name: 'rabbitmqprelaunch11590@juju-machine-0-lxc-0'
- home dir: /var/lib/rabbitmq
- cookie hash: /Pe4Mo4pg2tLXWUO0aB7hQ==
## REPRODUCER:
To remove the surrounding complexity of OpenStack and bundles, here is a simplified approach to reproducing this bug.
juju bootstrap --constraints "arch=amd64 tags=uosci"
mkdir trusty
# grab next charm
bzr branch lp:~openstack-charmers/charms/trusty/rabbitmq-server/next trusty/rabbitmq-server
# grab next charm with proposed fix
bzr branch lp:~james-page/charms/trusty/rabbitmq-server/fixup-configure-nodename trusty/rabbitmq-server-fix1
# grab stable charm
bzr branch lp:charms/trusty/rabbitmq-server trusty/rabbitmq-server-stable
# Manually change "name:" to "rabbitmq-server-fix1" in trusty/rabbitmq-server-fix1/metadata.yaml.
# Manually change "name:" to "rabbitmq-server-stable" in trusty/rabbitmq-server-stable/metadata.yaml.
# Deploy next charm to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server
# Deploy next charm to bare metal (OK):
juju add-unit rabbitmq-server
# Deploy proposed charm fix to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-fix1 # fails
# Deploy proposed charm fix to bare metal (OK):
juju add-unit rabbitmq-server-fix1 # succeeds, causes rmq to install to bare metal, no lxc.
# Deploy stable charm to a container (OK):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-stable
# Deploy stable charm to bare metal (OK):
juju add-unit rabbitmq-server-stable
# juju stat after reproducer:
juju stat --format tabular
juju stat --format yaml
SEE --> http://paste.ubuntu.com/11888683/
## RESULTANT CONFS:
jenkins@juju-osci-machine-13:~/bzr⟫ juju run --all "cat /etc/rabbitmq/rabbitmq-env.conf"
# ignore 0
- MachineId: "0"
Stderr: "Warning: Permanently added '10.245.168.11' (ECDSA) to the list of known
hosts.\r\ncat: /etc/rabbitmq/rabbitmq-env.conf: No such file or directory\n"
# next charm in lxc
- MachineId: 0/lxc/0
RABBITMQ_NODENAME=rabbit@10-245-173-99
# proposed fix charm in lxc
- MachineId: 0/lxc/1
RABBITMQ_NODENAME=rabbit@10-245-173-100
# stable charm in lxc
- MachineId: 0/lxc/2
RABBITMQ_NODENAME=rabbit@10-245-173-101
# next charm on bare metal
- MachineId: "1"
RABBITMQ_NODENAME=rabbit@fat-machine
# proposed fix charm on bare metal
- MachineId: "2"
RABBITMQ_NODENAME=rabbit@cylindrical-base
# stable charm on bare metal
- MachineId: "3"
RABBITMQ_NODENAME=rabbit@grizzled-family
## JUJU/MAAS VERSION INFO:
# juju version:
jenkins@juju-osci-machine-13:~/bzr⟫ apt-cache policy juju
juju:
Installed: 1.24.2-0ubuntu1~14.04.1~juju1
Candidate: 1.24.2-0ubuntu1~14.04.1~juju1
Version table:
*** 1.24.2-0ubuntu1~14.04.1~juju1 0
500 http://ppa.launchpad.net/juju/stable/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
1.20.11-0ubuntu0.14.04.1 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages
1.18.1-0ubuntu1 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
# maas version:
ubuntu@lescina:~$ apt-cache policy maas
maas:
Installed: 1.8.0+bzr4001-0ubuntu2~trusty1
Candidate: 1.8.0+bzr4001-0ubuntu2~trusty1
Version table:
*** 1.8.0+bzr4001-0ubuntu2~trusty1 0
500 http://ppa.launchpad.net/maas-maintainers/experimental/ubuntu/ trusty/main amd64 Packages
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
1.5.4+bzr2294-0ubuntu1.3 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
1.5.4+bzr2294-0ubuntu1.2 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
1.5+bzr2252-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
You have new mail in /var/mail/ubuntu |
|
| 2015-07-16 18:10:25 |
Ryan Beisner |
summary |
rmq next charm: pkg install fails when deployed to lxc |
rmq next charm: config-changed hook fails when deployed to lxc |
|
| 2015-07-16 18:15:06 |
Ryan Beisner |
description |
The rabbitmq-server next charm works on bare metal but not in a container; the stable charm works fine on both.
ERROR: node with name "rabbit" already running on "10-245-173-99"
DIAGNOSTICS
===========
nodes in question: ['rabbit@10-245-173-99']
hosts, their running nodes and ports:
- 10-245-173-99: [{rabbit,44415},
{rabbitmqctl11575,47036},
{rabbitmqprelaunch11590,41368}]
current node details:
- node name: 'rabbitmqprelaunch11590@juju-machine-0-lxc-0'
- home dir: /var/lib/rabbitmq
- cookie hash: /Pe4Mo4pg2tLXWUO0aB7hQ==
## REPRODUCER:
To remove the surrounding complexity of OpenStack and bundles, here is a simplified approach to reproducing this bug.
juju bootstrap --constraints "arch=amd64 tags=uosci"
mkdir trusty
# grab next charm
bzr branch lp:~openstack-charmers/charms/trusty/rabbitmq-server/next trusty/rabbitmq-server
# grab next charm with proposed fix
bzr branch lp:~james-page/charms/trusty/rabbitmq-server/fixup-configure-nodename trusty/rabbitmq-server-fix1
# grab stable charm
bzr branch lp:charms/trusty/rabbitmq-server trusty/rabbitmq-server-stable
# Manually change "name:" to "rabbitmq-server-fix1" in trusty/rabbitmq-server-fix1/metadata.yaml.
# Manually change "name:" to "rabbitmq-server-stable" in trusty/rabbitmq-server-stable/metadata.yaml.
# Deploy next charm to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server
# Deploy next charm to bare metal (OK):
juju add-unit rabbitmq-server
# Deploy proposed charm fix to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-fix1 # fails
# Deploy proposed charm fix to bare metal (OK):
juju add-unit rabbitmq-server-fix1 # succeeds, causes rmq to install to bare metal, no lxc.
# Deploy stable charm to a container (OK):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-stable
# Deploy stable charm to bare metal (OK):
juju add-unit rabbitmq-server-stable
# juju stat after reproducer:
juju stat --format tabular
juju stat --format yaml
SEE --> http://paste.ubuntu.com/11888683/
## RESULTANT CONFS:
jenkins@juju-osci-machine-13:~/bzr⟫ juju run --all "cat /etc/rabbitmq/rabbitmq-env.conf"
# ignore 0
- MachineId: "0"
Stderr: "Warning: Permanently added '10.245.168.11' (ECDSA) to the list of known
hosts.\r\ncat: /etc/rabbitmq/rabbitmq-env.conf: No such file or directory\n"
# next charm in lxc
- MachineId: 0/lxc/0
RABBITMQ_NODENAME=rabbit@10-245-173-99
# proposed fix charm in lxc
- MachineId: 0/lxc/1
RABBITMQ_NODENAME=rabbit@10-245-173-100
# stable charm in lxc
- MachineId: 0/lxc/2
RABBITMQ_NODENAME=rabbit@10-245-173-101
# next charm on bare metal
- MachineId: "1"
RABBITMQ_NODENAME=rabbit@fat-machine
# proposed fix charm on bare metal
- MachineId: "2"
RABBITMQ_NODENAME=rabbit@cylindrical-base
# stable charm on bare metal
- MachineId: "3"
RABBITMQ_NODENAME=rabbit@grizzled-family
## JUJU/MAAS VERSION INFO:
# juju version:
jenkins@juju-osci-machine-13:~/bzr⟫ apt-cache policy juju
juju:
Installed: 1.24.2-0ubuntu1~14.04.1~juju1
Candidate: 1.24.2-0ubuntu1~14.04.1~juju1
Version table:
*** 1.24.2-0ubuntu1~14.04.1~juju1 0
500 http://ppa.launchpad.net/juju/stable/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
1.20.11-0ubuntu0.14.04.1 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages
1.18.1-0ubuntu1 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
# maas version:
ubuntu@lescina:~$ apt-cache policy maas
maas:
Installed: 1.8.0+bzr4001-0ubuntu2~trusty1
Candidate: 1.8.0+bzr4001-0ubuntu2~trusty1
Version table:
*** 1.8.0+bzr4001-0ubuntu2~trusty1 0
500 http://ppa.launchpad.net/maas-maintainers/experimental/ubuntu/ trusty/main amd64 Packages
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
1.5.4+bzr2294-0ubuntu1.3 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
1.5.4+bzr2294-0ubuntu1.2 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
1.5+bzr2252-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
You have new mail in /var/mail/ubuntu |
The rabbitmq-server next charm works on bare metal but not in a container; the stable charm works fine on both.
After deploy, the rabbit startup errors out with:
ERROR: node with name "rabbit" already running on "10-245-173-99"
DIAGNOSTICS
===========
nodes in question: ['rabbit@10-245-173-99']
hosts, their running nodes and ports:
- 10-245-173-99: [{rabbit,44415},
{rabbitmqctl11575,47036},
{rabbitmqprelaunch11590,41368}]
current node details:
- node name: 'rabbitmqprelaunch11590@juju-machine-0-lxc-0'
- home dir: /var/lib/rabbitmq
- cookie hash: /Pe4Mo4pg2tLXWUO0aB7hQ==
After stopping the rabbitmq-server service on the unit, there remains a running mq server process.
Kill -9ing that service, then starting the rabbitmq-server service seems to resolve in place.
## REPRODUCER:
To remove the surrounding complexity of OpenStack and bundles, here is a simplified approach to reproducing this bug.
juju bootstrap --constraints "arch=amd64 tags=uosci"
mkdir trusty
# grab next charm
bzr branch lp:~openstack-charmers/charms/trusty/rabbitmq-server/next trusty/rabbitmq-server
# grab next charm with proposed fix
bzr branch lp:~james-page/charms/trusty/rabbitmq-server/fixup-configure-nodename trusty/rabbitmq-server-fix1
# grab stable charm
bzr branch lp:charms/trusty/rabbitmq-server trusty/rabbitmq-server-stable
# Manually change "name:" to "rabbitmq-server-fix1" in trusty/rabbitmq-server-fix1/metadata.yaml.
# Manually change "name:" to "rabbitmq-server-stable" in trusty/rabbitmq-server-stable/metadata.yaml.
# Deploy next charm to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server
# Deploy next charm to bare metal (OK):
juju add-unit rabbitmq-server
# Deploy proposed charm fix to a container (FAIL):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-fix1 # fails
# Deploy proposed charm fix to bare metal (OK):
juju add-unit rabbitmq-server-fix1 # succeeds, causes rmq to install to bare metal, no lxc.
# Deploy stable charm to a container (OK):
juju deploy --to lxc:0 --repository=./ local:trusty/rabbitmq-server-stable
# Deploy stable charm to bare metal (OK):
juju add-unit rabbitmq-server-stable
# juju stat after reproducer:
juju stat --format tabular
juju stat --format yaml
SEE --> http://paste.ubuntu.com/11888683/
## RESULTANT CONFS:
jenkins@juju-osci-machine-13:~/bzr⟫ juju run --all "cat /etc/rabbitmq/rabbitmq-env.conf"
# ignore 0
- MachineId: "0"
Stderr: "Warning: Permanently added '10.245.168.11' (ECDSA) to the list of known
hosts.\r\ncat: /etc/rabbitmq/rabbitmq-env.conf: No such file or directory\n"
# next charm in lxc
- MachineId: 0/lxc/0
RABBITMQ_NODENAME=rabbit@10-245-173-99
# proposed fix charm in lxc
- MachineId: 0/lxc/1
RABBITMQ_NODENAME=rabbit@10-245-173-100
# stable charm in lxc
- MachineId: 0/lxc/2
RABBITMQ_NODENAME=rabbit@10-245-173-101
# next charm on bare metal
- MachineId: "1"
RABBITMQ_NODENAME=rabbit@fat-machine
# proposed fix charm on bare metal
- MachineId: "2"
RABBITMQ_NODENAME=rabbit@cylindrical-base
# stable charm on bare metal
- MachineId: "3"
RABBITMQ_NODENAME=rabbit@grizzled-family
## JUJU/MAAS VERSION INFO:
# juju version:
jenkins@juju-osci-machine-13:~/bzr⟫ apt-cache policy juju
juju:
Installed: 1.24.2-0ubuntu1~14.04.1~juju1
Candidate: 1.24.2-0ubuntu1~14.04.1~juju1
Version table:
*** 1.24.2-0ubuntu1~14.04.1~juju1 0
500 http://ppa.launchpad.net/juju/stable/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
1.20.11-0ubuntu0.14.04.1 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages
1.18.1-0ubuntu1 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
# maas version:
ubuntu@lescina:~$ apt-cache policy maas
maas:
Installed: 1.8.0+bzr4001-0ubuntu2~trusty1
Candidate: 1.8.0+bzr4001-0ubuntu2~trusty1
Version table:
*** 1.8.0+bzr4001-0ubuntu2~trusty1 0
500 http://ppa.launchpad.net/maas-maintainers/experimental/ubuntu/ trusty/main amd64 Packages
500 http://ppa.launchpad.net/maas-maintainers/stable/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
1.5.4+bzr2294-0ubuntu1.3 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
1.5.4+bzr2294-0ubuntu1.2 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
1.5+bzr2252-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
You have new mail in /var/mail/ubuntu |
|
| 2015-07-16 20:47:36 |
Ryan Beisner |
branch linked |
|
lp:~1chb1n/charms/trusty/rabbitmq-server/fixup-configure-nodename2 |
|
| 2016-05-27 13:45:30 |
Liam Young |
rabbitmq-server (Juju Charms Collection): status |
New |
Fix Released |
|
