setting amp-ssh-pub-key after initial deployment requires configure-resources action to take effect
Bug #1937263 reported by
Nobuto Murata
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Octavia Charm |
In Progress
|
Wishlist
|
Unassigned | ||
Bug Description
For debugging purpose, I tried to use the following option to enable SSH access to Amphora instances.
> amp-ssh-key-name
> (string) Name of nova key to use to provide ssh access to Amphora
> VMs. Note that this key must be visible to the project used by Octavia.
>
> amp-ssh-pub-key
> (string) Base64 encoded public ssh key. This will be used when
> creating the key named by amp-ssh-key-name. Note that once the key is
> created it cannot be modified and the only way to do so is to delete it
> and have the charm create a new one.
However, the key wasn't uploaded unless configure-resources action was invoked explicitly. It would be nice the config description is more clear on this requirement.
Revision history for this message
| Nobuto Murata (nobuto) wrote | #1 |
Revision history for this message
| Frode Nordahl (fnordahl) wrote | #2 |
| Changed in charm-octavia: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to charm-octavia (master) | #3 |
| Changed in charm-octavia: | |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on charm-octavia (master) | #4 |
To post a comment you must log in.
As far as I see, create_nova_keypair is only called by src/actions/