| 2013-11-05 18:48:32 |
Kent Baxley |
bug |
|
|
added bug |
| 2013-11-05 18:48:32 |
Kent Baxley |
attachment added |
|
machine-1.log https://bugs.launchpad.net/bugs/1248283/+attachment/3900833/+files/machine-1.log |
|
| 2013-11-06 00:08:13 |
Curtis Hovey |
tags |
|
deploy maas-provider |
|
| 2013-11-06 00:08:17 |
Curtis Hovey |
tags |
deploy maas-provider |
dbus deploy maas-provider |
|
| 2013-11-06 00:40:29 |
Curtis Hovey |
summary |
Juju deploy of Charm in MAAS provider failing after successful bootstrap. Juju status stuck in “Pending” state |
Juju deploy of Charm in MAAS fails because dbus fails |
|
| 2013-11-06 00:40:40 |
Curtis Hovey |
affects |
juju-core |
lxc (Ubuntu) |
|
| 2013-11-06 04:39:20 |
Serge Hallyn |
lxc (Ubuntu): status |
New |
Incomplete |
|
| 2013-11-06 04:42:16 |
Serge Hallyn |
lxc (Ubuntu): status |
Incomplete |
New |
|
| 2013-11-06 16:47:18 |
Launchpad Janitor |
lxc (Ubuntu): status |
New |
Confirmed |
|
| 2013-11-06 16:55:26 |
Jeff Marcom |
bug task added |
|
lxc |
|
| 2013-11-06 16:55:37 |
Jeff Marcom |
bug task deleted |
lxc |
|
|
| 2013-11-06 16:56:03 |
Jeff Marcom |
bug task added |
|
juju-core |
|
| 2013-11-06 16:57:20 |
Jeff Marcom |
juju-core: status |
New |
Confirmed |
|
| 2013-11-06 17:02:20 |
Chris Glass |
affects |
lxc (Ubuntu) |
juju-core (Ubuntu) |
|
| 2013-11-06 17:02:38 |
Chris Glass |
tags |
dbus deploy maas-provider |
dbus deploy landscape maas-provider |
|
| 2013-11-06 17:06:00 |
Geoff Teale |
bug |
|
|
added subscriber Geoff Teale |
| 2013-11-06 18:49:24 |
Curtis Hovey |
juju-core: status |
Confirmed |
Triaged |
|
| 2013-11-06 18:49:33 |
Curtis Hovey |
juju-core: importance |
Undecided |
High |
|
| 2013-11-06 18:50:59 |
Curtis Hovey |
affects |
juju-core (Ubuntu) |
maas |
|
| 2013-11-06 18:51:16 |
Curtis Hovey |
maas: status |
Confirmed |
New |
|
| 2013-11-06 23:46:50 |
Julian Edwards |
maas: status |
New |
Incomplete |
|
| 2013-11-07 16:31:05 |
Andreas Hasenack |
bug |
|
|
added subscriber Andreas Hasenack |
| 2013-11-13 17:06:06 |
Chris Glass |
bug |
|
|
added subscriber Landscape Bugs |
| 2013-11-25 13:12:02 |
Robie Basak |
description |
I'm running a MAAS and Juju enviornment using 64-bit Ubuntu Server 13.10 for the MAAS node as well as all juju nodes, including the bootstrap node.
I can't seem to deploy any charms to the nodes without the services getting stuck in a 'pending' state. The problem seems to be that upon charm deployment dbus for some reason is stopped, and thus the whole process of deploying the charm gets stuck.
It is almost verbatim of the problem someone appears to have hit on raring, too:
http://askubuntu.com/questions/364714/juju-deploy-of-charm-mysql-in-maas-provider-failing-after-successful-bootstrap
For me, however, it's not just mysql...it's any service I try to deploy.
juju release: 1.16.2-0ubuntu1~ubuntu13.10.1~juju1
maas version: 1.4+bzr1693+dfsg-0
Ubuntu OS: 13.10, 64-bit for everything
Steps to reproduce:
1) Set up a maas server using 13.10 with all the latest updates.
2) Install juju-core from the stable ppa (1.16.2 in this case).
3) Enlist and commission some nodes.
4) download some charms locally (I'm in a semi-restricted network environment, so, it's easier for me to pull down the charms locally). For example, bzr branch lp:charms/rabbitmq-server
5) bootstrap the juju environment. Due to restrictions in my network I have to use "juju bootstrap --upload-tools". Firewall blocks the ability to run "juju sync-tools" beforehand.
6) Once the environment is bootstrapped, try to deploy a charm. This is what I used:
juju deploy --repository=charms/ local:rabbitmq-server --show-log.
Actual results:
Installation of the OS goes fine, along with the cloud-init after reboot. I can also ssh into the node via juju.
The charm, however, stays in a 'pending' state long after it is deployed on the server.
ssh-ing into the node and looking at /var/log/juju/machine-x.log reveals that the deployment stage fails due to being unable to connect to the system bus.
This seems to prevent the charm from ever deploying.
Expected results:
OS installs and charm deploys without issue.
Workaround:
I can work around this by ssh-ing into the node and starting dbus by hand. I then go back and re-deploy the charm via juju using:
juju destroy-unit rabbitmq-server/0
juju destroy-service rabbitmq-server
juju deploy --to 1 --repository=charms/ local:rabbitmq-server --show-log
At that point everything starts working again. I can even deploy another charm onto the same machine without problems once dbus is up and going.
I'm not sure what or why dbus is failing to start and I can't tell if dbus was running and it suddenly shut down prior to charm deployment.
I've attached a machine log from an attempt to deploy rabbitmq-server onto a bare metal node using 13.10. The same thing happens to any charm I try to deploy in this manner.
Let me know if you need anything else. |
[Impact]
juju fails to deploy charms on Saucy.
[Steps to Reproduce]
On Saucy:
root@foo:~# dpkg-query -W dbus
dbus 1.6.12-0ubuntu10
root@foo:~# status dbus
dbus start/running, process 817
root@foo:~# service networking restart
networking stop/waiting
networking start/running
root@foo:~# status dbus
dbus stop/waiting
Verified on amd64. I believe this also affects armhf.
[Analysis]
Either:
1) dbus shouldn't fail when networking is restarted; or
2) juju should not restart networking in this way as a runcmd in cloud-init userdata, and then expect dbus to work.
The relevant part of juju's userdata is:
- "cat > /etc/network/eth0.config << EOF\niface eth0 inet manual\n\nauto br0\niface
br0 inet dhcp\n bridge_ports eth0\nEOF\n"
- sed -i "s/iface eth0 inet dhcp/source \/etc\/network\/eth0.config/" /etc/network/interfaces
- service networking restart
I assume juju is restarting networking to set up the bridge that it configured; in this case, an "ifdown eth0" and a subsequent "ifup"s as required should suffice. No need to restart everything (eg. lo, etc) which I [rbasak] presume is causing the issue.
Note that dbus appears to silently fail; if it is going to stop, it should do so with a sensible log message.
[Original Description]
I'm running a MAAS and Juju enviornment using 64-bit Ubuntu Server 13.10 for the MAAS node as well as all juju nodes, including the bootstrap node.
I can't seem to deploy any charms to the nodes without the services getting stuck in a 'pending' state. The problem seems to be that upon charm deployment dbus for some reason is stopped, and thus the whole process of deploying the charm gets stuck.
It is almost verbatim of the problem someone appears to have hit on raring, too:
http://askubuntu.com/questions/364714/juju-deploy-of-charm-mysql-in-maas-provider-failing-after-successful-bootstrap
For me, however, it's not just mysql...it's any service I try to deploy.
juju release: 1.16.2-0ubuntu1~ubuntu13.10.1~juju1
maas version: 1.4+bzr1693+dfsg-0
Ubuntu OS: 13.10, 64-bit for everything
Steps to reproduce:
1) Set up a maas server using 13.10 with all the latest updates.
2) Install juju-core from the stable ppa (1.16.2 in this case).
3) Enlist and commission some nodes.
4) download some charms locally (I'm in a semi-restricted network environment, so, it's easier for me to pull down the charms locally). For example, bzr branch lp:charms/rabbitmq-server
5) bootstrap the juju environment. Due to restrictions in my network I have to use "juju bootstrap --upload-tools". Firewall blocks the ability to run "juju sync-tools" beforehand.
6) Once the environment is bootstrapped, try to deploy a charm. This is what I used:
juju deploy --repository=charms/ local:rabbitmq-server --show-log.
Actual results:
Installation of the OS goes fine, along with the cloud-init after reboot. I can also ssh into the node via juju.
The charm, however, stays in a 'pending' state long after it is deployed on the server.
ssh-ing into the node and looking at /var/log/juju/machine-x.log reveals that the deployment stage fails due to being unable to connect to the system bus.
This seems to prevent the charm from ever deploying.
Expected results:
OS installs and charm deploys without issue.
Workaround:
I can work around this by ssh-ing into the node and starting dbus by hand. I then go back and re-deploy the charm via juju using:
juju destroy-unit rabbitmq-server/0
juju destroy-service rabbitmq-server
juju deploy --to 1 --repository=charms/ local:rabbitmq-server --show-log
At that point everything starts working again. I can even deploy another charm onto the same machine without problems once dbus is up and going.
I'm not sure what or why dbus is failing to start and I can't tell if dbus was running and it suddenly shut down prior to charm deployment.
I've attached a machine log from an attempt to deploy rabbitmq-server onto a bare metal node using 13.10. The same thing happens to any charm I try to deploy in this manner.
Let me know if you need anything else. |
|
| 2013-11-25 13:15:08 |
Robie Basak |
maas: status |
Incomplete |
Invalid |
|
| 2013-11-25 13:15:37 |
Robie Basak |
bug task added |
|
dbus (Ubuntu) |
|
| 2013-11-25 13:16:03 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
| 2013-11-25 13:16:34 |
Robie Basak |
tags |
dbus deploy landscape maas-provider |
dbus deploy landscape maas-provider midway |
|
| 2013-11-26 16:17:36 |
Robie Basak |
bug task added |
|
juju-core (Ubuntu) |
|
| 2013-11-26 16:17:46 |
Robie Basak |
nominated for series |
|
Ubuntu Trusty |
|
| 2013-11-26 16:17:46 |
Robie Basak |
bug task added |
|
dbus (Ubuntu Trusty) |
|
| 2013-11-26 16:17:46 |
Robie Basak |
bug task added |
|
juju-core (Ubuntu Trusty) |
|
| 2013-11-26 16:18:06 |
Robie Basak |
juju-core (Ubuntu Trusty): status |
New |
Triaged |
|
| 2013-11-26 16:18:08 |
Robie Basak |
juju-core (Ubuntu Trusty): importance |
Undecided |
High |
|
| 2013-11-26 16:19:13 |
Robie Basak |
nominated for series |
|
Ubuntu Saucy |
|
| 2013-11-26 16:19:13 |
Robie Basak |
bug task added |
|
dbus (Ubuntu Saucy) |
|
| 2013-11-26 16:19:13 |
Robie Basak |
bug task added |
|
juju-core (Ubuntu Saucy) |
|
| 2013-11-26 16:19:22 |
Robie Basak |
juju-core (Ubuntu Saucy): status |
New |
Triaged |
|
| 2013-11-26 16:19:25 |
Robie Basak |
juju-core (Ubuntu Saucy): importance |
Undecided |
High |
|
| 2013-11-26 16:19:35 |
Robie Basak |
bug task deleted |
dbus (Ubuntu Saucy) |
|
|
| 2013-11-26 16:19:40 |
Robie Basak |
bug task deleted |
dbus (Ubuntu Trusty) |
|
|
| 2013-11-27 17:59:38 |
Antonio Rosales |
tags |
dbus deploy landscape maas-provider midway |
dbus deploy landscape maas-provider midway ubuntu-openstack |
|
| 2013-11-28 07:43:29 |
William Reade |
juju-core: milestone |
|
1.17.1 |
|
| 2014-01-23 10:39:08 |
Martin Packman |
juju-core: milestone |
1.17.1 |
1.18.0 |
|
| 2014-01-24 14:29:54 |
Launchpad Janitor |
dbus (Ubuntu): status |
New |
Confirmed |
|
| 2014-02-11 16:32:16 |
Robie Basak |
dbus (Ubuntu): importance |
Undecided |
Low |
|
| 2014-02-11 22:57:31 |
Serge Hallyn |
summary |
Juju deploy of Charm in MAAS fails because dbus fails |
dbus does not restart when 'restart networking' command is issued. |
|
| 2014-02-11 23:10:59 |
Serge Hallyn |
summary |
dbus does not restart when 'restart networking' command is issued. |
juju userdata should not restart networking |
|
| 2014-02-11 23:13:01 |
Serge Hallyn |
dbus (Ubuntu): status |
Confirmed |
Invalid |
|
| 2014-03-19 13:33:30 |
Martin Packman |
juju-core: milestone |
1.20.0 |
1.18.0 |
|
| 2014-03-20 09:11:24 |
Andrew Wilkins |
juju-core: status |
Triaged |
In Progress |
|
| 2014-03-20 09:11:27 |
Andrew Wilkins |
juju-core: assignee |
|
Andrew Wilkins (axwalk) |
|
| 2014-03-20 09:11:30 |
Andrew Wilkins |
juju-core: milestone |
1.18.0 |
1.17.6 |
|
| 2014-03-20 10:54:32 |
Andrew Wilkins |
branch linked |
|
lp:~axwalk/juju-core/lp1271144-maas-bridge-utils |
|
| 2014-03-20 10:54:37 |
Andrew Wilkins |
juju-core: status |
In Progress |
Fix Committed |
|
| 2014-03-20 16:59:11 |
Curtis Hovey |
juju-core: status |
Fix Committed |
Fix Released |
|
| 2014-03-24 16:55:07 |
Launchpad Janitor |
juju-core (Ubuntu Trusty): status |
Triaged |
Fix Released |
|
| 2014-03-24 17:07:15 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/juju-core |
|
| 2014-04-14 16:59:08 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/ubuntu/precise/juju-core/cloud-tools |
|
| 2014-12-05 06:34:16 |
Rolf Leggewie |
juju-core (Ubuntu Saucy): status |
Triaged |
Won't Fix |
|
| 2015-02-06 15:52:44 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-cloud-archive/ubuntu/precise/juju-core/precise-ctools |
|
