Running os-nova-install with --limit may not distribute SSH keys correctly

Bug #1887952 reported by Andrew Bonney
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Opinion
Undecided
Unassigned

Bug Description

This issue is similar to https://bugs.launchpad.net/openstack-ansible/+bug/1830037 but affects the os_nova role.

If the os-nova-install playbook runs against a limited subset of compute nodes then the 'nova_pubkey' fact will only get set for these cases: https://github.com/openstack/openstack-ansible-os_nova/blob/master/tasks/nova_compute_key_populate.yml#L38

When the key distribution runs and this fact isn't defined, some hosts' keys will fail to be distributed to the hosts within the limit: https://github.com/openstack/openstack-ansible-os_nova/blob/master/templates/nova-key-insert.sh.j2#L21

Revision history for this message
Dmitriy Rabotyagov (noonedeadpunk) wrote :

Hi Andrew,

I guess it's not a big, but as designed as for now.
To get keys distributed you need to run os-nova-install playbook across all nova_compute hosts but with specifying the nova-keys tag instead of doing limit. But we will think about the better ways to do that.

Changed in openstack-ansible:
status: New → Opinion
Revision history for this message
Andrew Bonney (andrewbonney) wrote :

That makes sense. At least that gives me a quicker way to fix things if I get into problems as a result of using --limit. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.