gpg --batch --verify during maas install causes Unhandled Error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Expired
|
Undecided
|
Unassigned | ||
simplestreams |
Incomplete
|
Medium
|
Unassigned |
Bug Description
After MAAS installation regiond.log shows an Unhandled Error and exception for:
subprocess.
Reproducible by installing 1.9.3 from ppa:maas/stable
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 1.9.3+bzr4577-
ii maas-cli 1.9.3+bzr4577-
ii maas-cluster-
ii maas-common 1.9.3+bzr4577-
ii maas-dhcp 1.9.3+bzr4577-
ii maas-dns 1.9.3+bzr4577-
ii maas-enlist 0.4+bzr38-0ubuntu1 amd64 MAAS enlistment tool
ii maas-proxy 1.9.3+bzr4577-
ii maas-region-
ii maas-region-
ii python-django-maas 1.9.3+bzr4577-
ii python-maas-client 1.9.3+bzr4577-
ii python-
Changed in maas: | |
status: | New → Incomplete |
Changed in simplestreams: | |
status: | New → Incomplete |
importance: | Undecided → Medium |
I tested this quickly on MAAS 2.0 ~b6 and didn't see the problem there.
Checking `man gpg`:
"""
RETURN VALUE
The program returns 0 if everything was fine, 1 if at least a signature was bad, and other error codes for fatal errors.
"""
So for whatever reason, this GPG verify operation is failing. I'd need to look into how this happens and what exactly we're verifying.
After looking at the log, it looks like the error is from simplestreams. I'm guessing the GPG signature of the image descriptions did not properly verify, but I'd have to check the code.
Here's the backtrace:
https:/ /paste. ubuntu. com/16928395/