cloud-init

Cloud init fails to install public keys when there's multiple AuthorizedKeysFile locations in sshd_config

Bug #1600223 reported by karena
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
New
Undecided
Unassigned

Bug Description

Our sshd_config file contains multiple locations:

AuthorizedKeysFile /usr/share/keys/mo-nonops/%u.pub /usr/share/keys/mo-ops/%u.pub /usr/share/keys/mo-qa/%u.pub /usr/share/fish-keys/%u.pub /etc/ssh/authorized_keys/%u.pub %h/.ssh/authorized_keys

When launching an instance, cloud init log shows that the default user's public key is created, but in fact no file exists.

When changing AuthorizedKeysFile to contain one single location, this issue is "resolved".

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

Other bug subscribers

Remote bug watches

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