Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade from PG 13 to PG 15 & move to sclorg images #1069

Closed
wants to merge 1 commit into from

Conversation

rooftopcellist
Copy link
Contributor

Thank you for your contribution!

If your PR needs a changelog entry:

If not, please add [noissue] to your commit message

@openshift-ci
Copy link

openshift-ci bot commented Aug 27, 2023

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rooftopcellist
Once this PR has been reviewed and has the lgtm label, please assign ipanova for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@@ -1089,7 +1089,7 @@ spec:
- name: RELATED_IMAGE_PULP_REDIS
value: redis:latest
- name: RELATED_IMAGE_PULP_POSTGRES
value: postgres:13
value: quay.io/sclorg/postgresql-15-c9s:latest
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @rooftopcellist!

Thank you for your contribution!
By default, this new image will run as user 1000 in vanilla k8s. Because of that, when the bkp-manager container tries to make a copy of /var/lib/pulp/tmp/<worker files> (which has 0700 permission and is owned by user 700), it is getting permission denied error and failing the backup task.

The old image (postgres:13 from dockerhub) had the access permissions because it was running with uid 0 (root).

@rooftopcellist
Copy link
Contributor Author

Closing this PR as this work will continue in another repo.

@app-sre-bot
Copy link

Can one of the admins verify this patch?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants