I think I spoke to soon, now seeing agent lost after deployment even though the metal nodes come up reliably where they didn't before:
...
2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP group default qlen 1000
inet 10.6.2.153/24 brd 10.6.2.255 scope global eth0
...
3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP group default qlen 1000
...
12: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 9000 qdisc noqueue master juju-br0 state UP group default
...
13: juju-br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP group default
inet 10.6.2.153/24 brd 10.6.2.255 scope global juju-br0
...
juju-br0 is on the bond which is on eth0 + eth1 (w/ no IP)
I think I spoke to soon, now seeing agent lost after deployment even though the metal nodes come up reliably where they didn't before:
... MULTICAST, SLAVE,UP, LOWER_UP> mtu 9000 qdisc mq master bond0 state UP group default qlen 1000
2: eth0: <BROADCAST,
inet 10.6.2.153/24 brd 10.6.2.255 scope global eth0 MULTICAST, SLAVE,UP, LOWER_UP> mtu 9000 qdisc mq master bond0 state UP group default qlen 1000 MULTICAST, MASTER, UP,LOWER_ UP> mtu 9000 qdisc noqueue master juju-br0 state UP group default
...
3: eth1: <BROADCAST,
...
12: bond0: <BROADCAST,
...
13: juju-br0: <BROADCAST, MULTICAST, UP,LOWER_ UP> mtu 9000 qdisc noqueue state UP group default
inet 10.6.2.153/24 brd 10.6.2.255 scope global juju-br0
...
juju-br0 is on the bond which is on eth0 + eth1 (w/ no IP)
EVENTUAL END RESULT:
neutron-gateway/0 blocked idle 1.25.6.1 1 neutron- gateway. maas Missing relations: messaging
nodes-bond-mme/0 active idle 1.25.6.1 2 compute-03.maas
nodes-bond-mme/1 unknown lost 1.25.6.1 3 compute-04.maas agent is lost, sorry! See 'juju status-history nodes-bond-mme/1'
nodes-sriov/0 active idle 1.25.6.1 4 compute-01.maas
nodes-sriov/1 unknown lost 1.25.6.1 5 compute-02.maas agent is lost, sorry! See 'juju status-history nodes-sriov/1'