[CI] test_create_dynamic_range sometimes fails in CI
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Brendan Donegan |
Bug Description
Every so often we're seeing test_create_
testtools.
stderr for maas maas ['ipranges', 'create', 'type=dynamic', 'start_
retcode for maas maas ['ipranges', 'create', 'type=dynamic', 'start_
stdout for maas maas ['ipranges', 'create', 'type=dynamic', 'start_
Traceback (most recent call last):
File "/tmp/autopkgte
self.
File "/usr/lib/
raise mismatch_error
testtools.
It's only occurring every dozen builds or so, so it's not a huge pain at the moment, but we should address it if we can.
Changed in maas: | |
status: | New → Triaged |
assignee: | nobody → Brendan Donegan (brendan-donegan) |
importance: | Undecided → Medium |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
As per conversation on IRC, we should be able to address this be reinstating the test_rack_connected test (it's currently skipped) and modifying it to check the status of the rackd service on the rack controller. Example code:
>>> js = json.loads( rack_controller s_output) service_ set']: get('name' ,'') == 'rackd': 'status' ])
>>> for service in js[0]['
... if service.
... print(service[