On a freshly-bootstrapped LXC environment, trying to deploy a new service will allocate an instance which stays in the "pending" state indefinitely.
1. I'm using juju 0.6.0.1 for Ubuntu 12.04.
2. Make sure that a) the directory containing the local environment and b) /var/lib/lxc are both completely empty.
3. "juju boostrap"
4. "juju status" will display the new environment
5. "juju deploy <charm>"
6. "juju status" will show output similar to status.txt, attached.
I'm not sure where to look for potential problems, but I also found some interesting content in the unit's container.log (attached). output.log is linked to a file containing only "/usr/bin/python: No module named juju.agents" several times. unit.log is a link to a non-existent file.
On a freshly- bootstrapped LXC environment, trying to deploy a new service will allocate an instance which stays in the "pending" state indefinitely.
1. I'm using juju 0.6.0.1 for Ubuntu 12.04.
2. Make sure that a) the directory containing the local environment and b) /var/lib/lxc are both completely empty.
3. "juju boostrap"
4. "juju status" will display the new environment
5. "juju deploy <charm>"
6. "juju status" will show output similar to status.txt, attached.
I'm not sure where to look for potential problems, but I also found some interesting content in the unit's container.log (attached). output.log is linked to a file containing only "/usr/bin/python: No module named juju.agents" several times. unit.log is a link to a non-existent file.