Skip to content

[patch] patch postgredb-tekton-results-postgres-0 PVC with storageclass when no default available #67

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

Open
wants to merge 13 commits into
base: stable
Choose a base branch
from

Conversation

sanjayprab
Copy link
Contributor

@sanjayprab sanjayprab commented Apr 7, 2025

External Issue - ibm-mas/cli#1511
Internal issue - https://jsw.ibm.com/browse/MASCORE-6225

When Openshift-pipelines operator is installed as part of tekton pipeline,
the postgredb-tekton-results-postgres-0 PVC was not getting ready since there's no default storageclass set in cluster.
since this PVC doesn't come up and was in pending state, it causing the tekton-results-postgres statefulSet also to be in pending,
due to these resources not coming up, the MAS pre-install-check in the pipeline times out checking the health of this statefulSet, causing failure in pipeline.

Solution - with this fix, we will determine the default storage class and patch the PVC. If for some reason, there's no recognizable storage class to use, the patch will fail

fvt test:
#2715 and #2716 tested with this changes
image

@anilprajapatiibm anilprajapatiibm marked this pull request as ready for review April 23, 2025 06:57
Copy link
Contributor

@durera durera left a comment

Choose a reason for hiding this comment

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

This has been sitting around for a month .. please resolve the merge conflicts with the May catalog update branch that I just merged into stable and we will get this done

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