canonical-certification-server crashes on resume of a session
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Next Generation Checkbox (CLI) |
Fix Released
|
High
|
Jeff Lane |
Bug Description
I'm running multiple 17.10 regression test runs on boldore, a Cisco UCS C240 M4 (VIC) server in 1SS, because it's showing inconsistent and flaky behavior on some CPU tests, including occasional system hangs. Unfortunately, upon resuming, I'm seeing the following:
$ canonical-
=======
There is 1 incomplete session that might be resumed
Do you want to resume session 'canonical-
r => resume this session
n => next session
c => create new session
d => delete old sessions
[rncd]: r
WARNING:
WARNING:
WARNING:
ERROR:plainbox.
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/
if not self._maybe_
File "/usr/lib/
return self._run_
File "/usr/lib/
self.
File "/usr/lib/
metadata = self.ctx.
File "/usr/lib/
raise exc
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
self.
File "/usr/lib/
os.
PermissionError: [Errno 13] Permission denied: '/home/
Please report a bug including the information from the paragraph above. To
report the bug visit https:/
We are sorry for the inconvenience!
I noticed the "PermissionError" warning, and saw that /home/ubuntu/
I'm attaching a copy of the ~/.cache/plainbox directory tree for the server in question.
Related branches
- Checkbox Developers: Pending requested
-
Diff: 12 lines (+0/-1)1 file modifiedunits/virtualization/jobs.pxu (+0/-1)
Changed in checkbox-ng: | |
assignee: | Jeff Lane (bladernr) → nobody |
Changed in checkbox-ng: | |
status: | Confirmed → Fix Committed |
milestone: | none → 0.36.0 |
tags: | added: hwcert-server |
Changed in checkbox-ng: | |
milestone: | 0.36.0 → 1.0.0 |
Changed in checkbox-ng: | |
status: | Fix Committed → Fix Released |
I noticed this today too. It looks like for whatever reason running lxd init in the lxd test as root is causing this. I think it's safe to drop the enhanced permissions, but I'll need to check that out more thoroughly.