Temporary patch for incorrect test user key file ownership #1837
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jefferbrecht
changed the title
When we create test VMs, we include an SSH pubkey for a test user as metadata. The guest agent sees this and creates a system user (with a `~/.ssh/authorized_keys` file holding the key we defined) accordingly. On some DLVM images, the `~/.ssh/authorized_keys` file subsequently gets its ownership attributes corrupted during startup. This prevents us from being able to SSH into the VM for the remainder of the test. This change deploys a workaround that manually patches over the corruption at VM startup.
jefferbrecht
force-pushed
the
jefferbrecht-dlvm-workaround
branch
from
b225135
to
2662063
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When we create test VMs, we include an SSH pubkey for a test user as metadata. The guest agent sees this and creates a system user (with a
~/.ssh/authorized_keysfile holding the key we defined) accordingly. On some DLVM images, the~/.ssh/authorized_keysfile subsequently gets its ownership attributes corrupted during startup. This prevents us from being able to SSH into the VM for the remainder of the test.This PR deploys a workaround that manually patches over the corruption at VM startup.
Related issue
b/380470389
How has this been tested?
Tests passed locally
Checklist: