authorized_keys created by add_user job gets stomped on by GCP metadata agent apparently.

[smgoller]

Context: Using bbl to deploy a bosh environment.

bbl (bosh boot loader) has a command to allow you to ssh to the bosh director or to the jumpbox it's created. It uses the add_user job from os-conf-release to create a user and add a key to its authorized_users file. Unfortunately, after awhile the ssh key stops working. SSHing into the bbl-created jumpbox via alternative means reveals that the authorized_keys file has been stomped on by something, presumably Google's metadata agent that updates these sorts of things.

[bosh-admin-bot]

This issue was marked as Stale because it has been open for 21 days without any activity. If no activity takes place in the coming 7 days it will automatically be close. To prevent this from happening remove the Stale label or comment below.

[bosh-admin-bot]

This issue was closed because it has been labeled Stale for 7 days without subsequent activity. Feel free to re-open this issue at any time by commenting below.