live migration between different instances of nova-compute application fail on ssh key
Bug #1822027 reported by
Xav Paice
This bug report is a duplicate of:
Bug #1468871: SSH pubkeys handled per relation-id only.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Nova Compute Charm |
New
|
Undecided
|
Unassigned | ||
Bug Description
We have a cloud running 18.11 charms, Queens, where we have two applications for nova-compute, necessitated by totally different settings for each application. The two are in different host aggregates, and both are related to the same nova-cloud-
We can live-migrate within the application just fine because the ssh key exchange works, but when we try to live-migrate between hosts in nova-compute-foo and nova-compute-bar there's no relation over which to exchange ssh keys, so the migration fails.
Should we be adding a relation here between the two compute applications, or is this just by design?
Revision history for this message
| James Page (james-page) wrote | #1 |
Revision history for this message
| Peter Sabaini (peter-sabaini) wrote | #2 |
Revision history for this message
| Peter Sabaini (peter-sabaini) wrote | #3 |
To post a comment you must log in.
I think this was by design, mainly because nova used to be really bad a pre-checking targets for live migration.
As this is now a much improved feature in Nova, it might make sense to expanded the SSH key sharing cross relation id.
I'd quite like to see if we could not do SSH key sharing for live migration; something involving vault might be good as the SSH sharing code is super slow in the charms.