checkbox-cli remote-control traceback
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Next Generation Checkbox (CLI) |
Invalid
|
High
|
Maciej Kisielewski |
Bug Description
Launched checkbox remote-service on a node, then launched checkbox-cli remote-control on my MAAS server.
I then chose the "All Smoke Tests" option from the list of test plans and hit Enter and the tool crashed with this traceback:
Traceback (most recent call last):
File "/usr/lib/
return self._dispatch()
File "/usr/lib/
result = ingredient.
File "/usr/lib/
return self._dispatch(
File "/usr/lib/
return self._dispatch_
File "/usr/lib/
return self._dispatch(
File "/usr/lib/
retval = command.
File "/usr/lib/
self.
File "/usr/lib/
}[state]()
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
pass_required = self.sa.
File "/usr/lib/
return syncreq(self, consts.
File "/usr/lib/
return conn.sync_
File "/usr/lib/
raise obj
_get_exception_
========= Remote Traceback (1) =========
Traceback (most recent call last):
File "/usr/lib/
res = self._HANDLERS[
File "/usr/lib/
return self._access_
File "/usr/lib/
return accessor(obj, name, *args)
AttributeError: 'SessionAssistant2' object has no attribute 'prepare_
Please report a bug including the information from the paragraph above. To
report the bug visit https:/
We are sorry for the inconvenience!
There was nothing on the Remote system console related to this.
Changed in checkbox-ng: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Maciej Kisielewski (kissiel) |
Changed in checkbox-ng: | |
milestone: | none → 1.3.0 |
Changed in checkbox-ng: | |
status: | In Progress → Invalid |
After more digging I realized the Remote wasn't on the same checkbox-ng version the Local was on. Had a PPA issue that needed to be corrected. Once the Remote was successfully updated this issue went away.
That said, tracebacks like this should be handled better and the error output should be more useful.
On the remote I had version 1.0.0 and on the Local I had version 1.1.0, hence the issue. Both are now on 1.1.0 and working fine.