Missing network binding after Juju upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
After upgrading Juju from 2.6 to 2.9 we cannot upgrade the nrpe charm because of a missing network binding:
208 2021-11-09 13:19:30 INFO unit.nrpe-
1 2021-11-09 13:19:30 WARNING unit.nrpe-
2 2021-11-09 13:19:30 WARNING unit.nrpe-
3 2021-11-09 13:19:30 WARNING unit.nrpe-
4 2021-11-09 13:19:30 WARNING unit.nrpe-
5 2021-11-09 13:19:30 WARNING unit.nrpe-
6 2021-11-09 13:19:30 WARNING unit.nrpe-
7 2021-11-09 13:19:30 WARNING unit.nrpe-
8 2021-11-09 13:19:30 WARNING unit.nrpe-
9 2021-11-09 13:19:30 WARNING unit.nrpe-
10 2021-11-09 13:19:30 WARNING unit.nrpe-
11 2021-11-09 13:19:30 WARNING unit.nrpe-
12 2021-11-09 13:19:30 WARNING unit.nrpe-
13 2021-11-09 13:19:30 WARNING unit.nrpe-
14 2021-11-09 13:19:30 WARNING unit.nrpe-
15 2021-11-09 13:19:30 WARNING unit.nrpe-
16 2021-11-09 13:19:30 WARNING unit.nrpe-
17 2021-11-09 13:19:30 ERROR juju.worker.
18 2021-11-09 13:19:30 DEBUG juju.machinelock machinelock.go:186 machine lock released for nrpe-host/45 uniter (run install hook)
The nagios <--> nrpe relation is in place
Potentially interesting is this information from the Juju database:
[0] $ bsondump machines.bson 2>/dev/null | jq 'select(
[] #<- empty json array.
(The unit is running on 0/kvm/0)
And
[1] $ bsondump machines.bson 2>/dev/null \| jq 'select(
[{
"value": "10.150.0.107",
"addresstype": "ipv4",
"networkscope": "local-cloud",
"origin": "provider",
"spaceid": "4"
},{
"value": "10.152.0.61",
"addresstype": "ipv4",
"networkscope": "local-cloud",
"origin": "provider",
"spaceid": "8"
},
...
]
description: | updated |
This feels like a case where 2.6 didn't record some sort of information that 2.9 depends on, which we very likely have an upgrade step to sort out for most cases. I have the feeling we missed the case where the underlying 'machine' is a nested KVM guest.
I do believe you can 'juju refresh --force-units' (juju upgrade-charm) to change the content on disk even if the charm is failing a hook. However, that wouldn't necessarily fix the issue about why Juju doesn't know the network information for that unit.