acceptance: run python, psql containers as current uid#81460
acceptance: run python, psql containers as current uid#81460craig[bot] merged 1 commit intocockroachdb:masterfrom
python, psql containers as current uid#81460Conversation
|
This change is |
|
it's amissing entry in /etc/passwd. |
403c307 to
714b36f
Compare
`postgres`'s permission checking for certificates has gotten more rigorous since [this commit](https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=a59c79564bdc209a5bc7b02d706f0d7352eb82fa). This has broken a couple `acceptance` tests which do not pin to any specific `postgres` version (see cockroachdb#81313, cockroachdb#81437). Here we attempt to solve the problem "once and for all" by ensuring that these containers run with a UID that is equal to the one that created the certificates. Release note: None
knz
left a comment
There was a problem hiding this comment.
awesome, thanks
Reviewed 6 of 6 files at r1, all commit messages.
Reviewable status:complete! 0 of 0 LGTMs obtained (waiting on @rickystewart)
|
TFTR! bors r=knz |
|
i assume we're backporting these, so i'm adding the tags! |
|
This PR was included in a batch that was canceled, it will be automatically retried |
|
Build succeeded: |
|
Encountered an error creating backports. Some common things that can go wrong:
You might need to create your backport manually using the backport tool. error creating merge commit from 3ef77d5 to blathers/backport-release-21.2-81460: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict [] you may need to manually resolve merge conflicts with the backport tool. Backport to branch 21.2.x failed. See errors above. 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan. |
Manual cherry-pick from cockroachdb#81460. `postgres`'s permission checking for certificates has gotten more rigorous since [this commit](https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=a59c79564bdc209a5bc7b02d706f0d7352eb82fa). This has broken a couple `acceptance` tests which do not pin to any specific `postgres` version (see cockroachdb#81313, cockroachdb#81437). Here we attempt to solve the problem "once and for all" by ensuring that these containers run with a UID that is equal to the one that created the certificates. Release note: None
postgres's permission checking for certificates has gotten morerigorous since this commit.
This has broken a couple
acceptancetests which do not pin to anyspecific
postgresversion (see #81313, #81437).Here we attempt to solve the problem "once and for all" by ensuring that
these containers run with a UID that is equal to the one that created
the certificates.
Release note: None