[patch] pipeline-db2-license secret not created when Slack is not configured Slack config - #434
Merged
Conversation
…figured Slack config [fix] pipeline-db2-license secret not created when Slack is not configured The prepareUpdateSecrets() function in tekton.py was introduced in PR #425 ("day2 fix for devops slack secret issue") which added an early return when slack_token or slack_channel are not provided. This inadvertently placed the pipeline-db2-license secret creation after the early return, meaning the secret was never created for users who do not have Slack configured. The PipelineRun template (pipelinerun-update.yml.j2) unconditionally binds the shared-db2 workspace to secretName: pipeline-db2-license. When the secret does not exist, the update-db2 task pod is stuck in Init:0/2 with repeated FailedMount errors, blocking the entire mas-update pipeline run. Fix: move pipeline-db2-license secret creation before the Slack guard so it is always created regardless of whether Slack credentials are provided. Fixes: update-db2 pod stuck at Init:0/2 — FailedMount: secret "pipeline-db2-license" not found
prveenkumr
changed the title
Contributor
Author
|
test passed in day290 pipeline: |
anilprajapatiibm
approved these changes
Jul 27, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 27, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 27, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 27, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 27, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 27, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 28, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The prepareUpdateSecrets() function in tekton.py was introduced in PR #425 ("day2 fix for devops slack secret issue") which added an early return when slack_token or slack_channel are not provided. This inadvertently placed the pipeline-db2-license secret creation after the early return, meaning the secret was never created for users who do not have Slack configured.
The PipelineRun template (pipelinerun-update.yml.j2) unconditionally binds the shared-db2 workspace to secretName: pipeline-db2-license. When the secret does not exist, the update-db2 task pod is stuck in Init:0/2 with repeated FailedMount errors, blocking the entire mas-update pipeline run.
Fix: move pipeline-db2-license secret creation before the Slack guard so it is always created regardless of whether Slack credentials are provided.
Fixes: update-db2 pod stuck at Init:0/2 — FailedMount: secret "pipeline-db2-license" not found