Skip to content

[patch] day2 fix for devops slack secret issue#425

Merged
anilprajapatiibm merged 2 commits into
stablefrom
rbacmode
Jul 17, 2026
Merged

[patch] day2 fix for devops slack secret issue#425
anilprajapatiibm merged 2 commits into
stablefrom
rbacmode

Conversation

@unnati-solanki-git
unnati-solanki-git marked this pull request as ready for review July 15, 2026 18:48
@unnati-solanki-git
unnati-solanki-git requested a review from a team as a code owner July 15, 2026 18:48
@anilprajapatiibm
anilprajapatiibm added this pull request to the merge queue Jul 17, 2026
Merged via the queue into stable with commit bca8e90 Jul 17, 2026
3 checks passed
@anilprajapatiibm
anilprajapatiibm deleted the rbacmode branch July 17, 2026 06:53
prveenkumr added a commit that referenced this pull request Jul 25, 2026
…rets regardless of Slack config

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.
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.

2 participants