update-status failures on s390x
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Charm Helpers |
Fix Released
|
Undecided
|
Unassigned | ||
OpenStack Neutron Open vSwitch Charm |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
On an s390x compute node, neutron-openvswitch fails at the update-status hook. (this cloud is running ocata, with 17.11 charms)
The error is:
2018-02-02 08:19:32 DEBUG update-status Traceback (most recent call last):
2018-02-02 08:19:32 DEBUG update-status File "/var/lib/
2018-02-02 08:19:32 DEBUG update-status main()
2018-02-02 08:19:32 DEBUG update-status File "/var/lib/
2018-02-02 08:19:32 DEBUG update-status assess_
2018-02-02 08:19:32 DEBUG update-status File "/var/lib/
2018-02-02 08:19:32 DEBUG update-status assess_
2018-02-02 08:19:32 DEBUG update-status File "/var/lib/
2018-02-02 08:19:32 DEBUG update-status state, message = _determine_
2018-02-02 08:19:32 DEBUG update-status File "/var/lib/
2018-02-02 08:19:32 DEBUG update-status configs, required_
2018-02-02 08:19:32 DEBUG update-status File "/var/lib/
2018-02-02 08:19:32 DEBUG update-status required_
2018-02-02 08:19:32 DEBUG update-status File "/var/lib/
2018-02-02 08:19:32 DEBUG update-status complete_ctxts = configs.
2018-02-02 08:19:32 DEBUG update-status File "/var/lib/
2018-02-02 08:19:32 DEBUG update-status for i in six.itervalues(
2018-02-02 08:19:32 DEBUG update-status File "/var/lib/
2018-02-02 08:19:32 DEBUG update-status for i in six.itervalues(
2018-02-02 08:19:32 DEBUG update-status File "/var/lib/
2018-02-02 08:19:32 DEBUG update-status self.context()
2018-02-02 08:19:32 DEBUG update-status File "/var/lib/
2018-02-02 08:19:32 DEBUG update-status _ctxt = context()
2018-02-02 08:19:32 DEBUG update-status File "/var/lib/
2018-02-02 08:19:32 DEBUG update-status ctxt.update(
2018-02-02 08:19:32 DEBUG update-status File "/var/lib/
2018-02-02 08:19:32 DEBUG update-status fallback)
2018-02-02 08:19:32 DEBUG update-status File "/var/lib/
2018-02-02 08:19:32 DEBUG update-status addresses = netifaces.
2018-02-02 08:19:32 DEBUG update-status ValueError: You must specify a valid interface name.
2018-02-02 08:19:32 ERROR juju.worker.
As the stack trace says, it happens in ip.py", line 112:
for iface in netifaces.
By running such a loop manually, I could see that it fails 50% of the time, either on a tap device or on a qbr* one:
tapc3c1d498-70
Traceback (most recent call last):
File "./debug_
print(
ValueError: You must specify a valid interface name.
My understanding is that this is a race condition, if an instance is present when netifaces.
At the moment, netifaces.
This results in the neutron-openvswitch unit being in error 50% of the time.
description: | updated |
Changed in charm-helpers: | |
status: | New → Fix Released |
tags: | added: sts |
Fixed in https:/ /github. com/juju/ charm-helpers/ pull/107