Spurious test failure: rndc hits “address in use” error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
High
|
Unassigned |
Bug Description
Thanks to improved logging, we now get decent output when rndc fails during test runs. As it turns out, the write_dns_config() task restarts the name server but finds the server's port in use:
warning: /tmp/tmp7Xz17g/
Abridged callback:
src/maasserver/
management=
src/maasserver/
maas_
…. (save() call chain leading to post-save signal) ….
src/maasserver/
add_
src/maasserver/
zones=
…. (celery ‘delay’ call chain) …
src/provisionin
func(*args, **kwargs)
src/provisionin
callback.
…. (celery ‘delay’ call chain) …
src/provisionin
func(*args, **kwargs)
src/provisionin
callback.
…. (celery ‘delay’ call chain) …
src/provisionin
func(*args, **kwargs)
src/provisionin
execute_
src/provisionin
call_
src/provisionin
return subprocess.
ExternalProcess
None
Download link for full test output: https:/
Changed in maas: | |
status: | Triaged → Won't Fix |