openstack-origin needs documentation for providing key option
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Keystone Charm |
Fix Released
|
Low
|
Unassigned | ||
keystone (Juju Charms Collection) |
Invalid
|
Low
|
Unassigned |
Bug Description
The OpenStack charms (using Keystone here as an example) provide a config option to specify an arbitrary apt repo, but do not provide a mechanism for adding a corresponding public key.
If a user creates and hosts their own repo outside of launchpad, add-apt-repository does not add the public key to the node. This causes install hook failures, with underlying package authentication errors such as:
WARNING: The following packages cannot be authenticated!`
W: GPG error: http://
Linking for reference:
http://
summary: |
- openstack-origin option needs corresponding pub key option + openstack-origin option needs documentation for providing key option |
summary: |
- openstack-origin option needs documentation for providing key option + openstack-origin needs documentation for providing key option |
Changed in charm-keystone: | |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in keystone (Juju Charms Collection): | |
status: | Triaged → Invalid |
Changed in charm-keystone: | |
milestone: | none → 18.05 |
Changed in charm-keystone: | |
status: | Fix Committed → Fix Released |
This actually isn't a problem. You can indeed import a public key from keyserver. ubuntu. com by appending the key to the deb url entry separated via a |.
e..g this will work:
juju set openstack-origin nova-compute openstack- origin= "deb http:// ppa.launchpad. net/billy- olsen/testfix- kilo/ubuntu vivid main|FA0FD8E1"
The code is common across all the charms and can be found in charm-helpers here:
http:// bazaar. launchpad. net/~charm- helpers/ charm-helpers/ devel/view/ 455.1.1/ charmhelpers/ contrib/ openstack/ utils.py# L314
However, the documentation in the config.yaml doesn't cover this detail and it should.