I have tried to recreate however I am now seeing the agent not coming up
on the unit and can't ssh it it (connection refused):
jenkins@juju-a6a70b-integration-juju2-1:~$ juju status 5 --format=yaml
model:
name: ci-oil-slave14
controller: maas
cloud: maas
version: 2.1-rc2
machines:
"5":
juju-status:
current: pending
since: 23 Feb 2017 00:32:24Z
dns-name: 10.244.242.181
ip-addresses:
- 10.244.242.181
instance-id: 4y4fm8
machine-status:
current: running
message: Deployed
since: 23 Feb 2017 01:07:34Z
series: trusty
containers:
5/lxd/0:
juju-status:
current: pending
since: 23 Feb 2017 00:33:13Z
instance-id: pending
machine-status:
current: pending
since: 23 Feb 2017 00:33:13Z
series: trusty
constraints: tags=integrationnedge1
hardware: arch=amd64 cores=4 mem=8192M
tags=whitelist-nedge,integrationnedge1,hw-integration-xenial
availability-zone=default
"6":
juju-status:
current: started
since: 23 Feb 2017 00:39:37Z
version: 2.1-rc2
dns-name: 10.244.242.231
ip-addresses:
- 10.244.242.231
instance-id: 4y4crh
machine-status:
current: running
message: Deployed
since: 23 Feb 2017 00:39:05Z
series: trusty
containers:
6/lxd/0:
juju-status:
current: started
since: 23 Feb 2017 00:48:04Z
version: 2.1-rc2
dns-name: 10.244.242.105
ip-addresses:
- 10.244.242.105
instance-id: juju-0ce83c-6-lxd-0
machine-status:
current: running
message: Container started
since: 23 Feb 2017 00:47:22Z
series: trusty
constraints: tags=hayward-43
hardware: arch=amd64 cores=8 mem=16384M
tags=hardware-sm15k,hayward-43,hw-integration-xenial
availability-zone=default
applications:
keystone:
charm: cs:keystone-262
series: trusty
os: ubuntu
charm-origin: jujucharms
charm-name: keystone
charm-rev: 262
exposed: false
application-status:
current: active
message: Unit is ready
since: 23 Feb 2017 15:26:39Z
relations:
cluster:
- keystone
identity-service:
- cinder
- glance
- neutron-api
- nexentaedge-swift-gw
- nova-cloud-controller
- openstack-dashboard
shared-db:
- mysql
units:
keystone/0:
workload-status:
current: active
message: Unit is ready
since: 23 Feb 2017 15:26:39Z
juju-status:
current: idle
since: 23 Feb 2017 15:26:44Z
version: 2.1-rc2
leader: true
machine: 6/lxd/0
open-ports:
- 5000/tcp
public-address: 10.244.242.105
version: 9.2.0
nexentaedge-mgmt:
charm: cs:trusty/nexentaedge-mgmt-5
series: trusty
os: ubuntu
charm-origin: jujucharms
charm-name: nexentaedge-mgmt
charm-rev: 5
exposed: false
application-status:
current: waiting
message: waiting for machine
since: 23 Feb 2017 00:32:58Z
relations:
cinder-gw:
- nexentaedge-iscsi-gw
nedge:
- nexentaedge-data
swift-gw:
- nexentaedge-swift-gw
units:
nexentaedge-mgmt/0:
workload-status:
current: waiting
message: waiting for machine
since: 23 Feb 2017 00:32:58Z
juju-status:
current: allocating
since: 23 Feb 2017 00:32:58Z
machine: "5"
public-address: 10.244.242.181
openstack-dashboard:
charm: cs:openstack-dashboard-243
series: trusty
os: ubuntu
charm-origin: jujucharms
charm-name: openstack-dashboard
charm-rev: 243
exposed: false
application-status:
current: waiting
message: waiting for machine
since: 23 Feb 2017 00:33:23Z
relations:
cluster:
- openstack-dashboard
identity-service:
- keystone
units:
openstack-dashboard/0:
workload-status:
current: waiting
message: waiting for machine
since: 23 Feb 2017 00:33:23Z
juju-status:
current: allocating
since: 23 Feb 2017 00:33:23Z
machine: 5/lxd/0
So, I have to get passed that first. This could be a new bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637230
Title:
[2.0] Error calling 'lxd forkstart
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1637230/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
