Regiond crashes: sequence item 0: expected str instance, ConnectionLost found
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Triaged
|
Undecided
|
Unassigned | ||
3.5 |
Triaged
|
Undecided
|
Unassigned |
Bug Description
Running HA MAAS using MAAS 3.5 while trying to add new bare-metal nodes regiond crashes on one of the maas hosts because the connection to the bare-metal host was closed unexpectedly.
the machine is being created in MAAS with:
maas root machines create hostname=beartic power_type=ipmi architecture=
and this is the 6th machine being added to the MAAS, the first 5 all succeeded.
from the attached logs, on host 10.244.40.32 you can see the regiond going down at the same time the call to create the machine:
Apr 9 18:56:51 swoobat regiond[1297846]: maasserver.
Apr 9 18:56:51 swoobat regiond[1297846]: Traceback (most recent call last):
Apr 9 18:56:51 swoobat regiond[1297846]: File "/usr/lib/
Apr 9 18:56:51 swoobat regiond[1297846]: raise exc from exc.__cause__
Apr 9 18:56:51 swoobat regiond[1297846]: File "/usr/lib/
Apr 9 18:56:51 swoobat regiond[1297846]: with post_commit_hooks:
Apr 9 18:56:51 swoobat regiond[1297846]: File "/usr/lib/
Apr 9 18:56:51 swoobat regiond[1297846]: self.fire()
Apr 9 18:56:51 swoobat regiond[1297846]: File "/usr/lib/
Apr 9 18:56:51 swoobat regiond[1297846]: result = func(*args, **kwargs)
Apr 9 18:56:51 swoobat regiond[1297846]: File "/usr/lib/
Apr 9 18:56:51 swoobat regiond[1297846]: self._fire_
Apr 9 18:56:51 swoobat regiond[1297846]: File "/usr/lib/
Apr 9 18:56:51 swoobat regiond[1297846]: result.
Apr 9 18:56:51 swoobat regiond[1297846]: File "/usr/lib/
Apr 9 18:56:51 swoobat regiond[1297846]: raise self.value.
Apr 9 18:56:51 swoobat regiond[1297846]: twisted.
Apr 9 18:56:51 swoobat regiond[1297846]: During handling of the above exception, another exception occurred:
Apr 9 18:56:51 swoobat regiond[1297846]: Traceback (most recent call last):
Apr 9 18:56:51 swoobat regiond[1297846]: File "/usr/lib/
Apr 9 18:56:51 swoobat regiond[1297846]: response = self.process_
Apr 9 18:56:51 swoobat regiond[1297846]: File "/usr/lib/
Apr 9 18:56:51 swoobat regiond[1297846]: response = middleware_
Apr 9 18:56:51 swoobat regiond[1297846]: File "/usr/lib/
Apr 9 18:56:51 swoobat regiond[1297846]: self.log_
Apr 9 18:56:51 swoobat regiond[1297846]: File "/usr/lib/
Apr 9 18:56:51 swoobat regiond[1297846]: logger.error(" Exception: %s ".center(79, "#") % str(exception))
Apr 9 18:56:51 swoobat regiond[1297846]: File "/usr/lib/
Apr 9 18:56:51 swoobat regiond[1297846]: s.append(" ".join(self.args))
Apr 9 18:56:51 swoobat regiond[1297846]: TypeError: sequence item 0: expected str instance, ConnectionLost found
Apr 9 18:56:51 swoobat regiond[1297846]: regiond: [info] 127.0.0.1 POST /MAAS/api/
I am unsure why the connection to the host was lost, but the error needs to be handled in a way that doesnt take down all of regiond, which comes up about 30 seconds later.
The logs are attached, but the testrun can be found at:
https:/
and the maas logs can also be found at:
https:/
Changed in maas: | |
milestone: | none → 3.6.0 |
status: | New → Triaged |