Details
-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
False
-
None
-
False
Description
Description of problem:
When starting a new pipeline through the "new pipeline" form and adding a secret (image registry or git / basic auth) at the bottom, the set password is not persisted in the secret.
Workaround : After the pipeline fails for the first time, the secret itself can be fixed by setting the password directly on the secret again.
Prerequisites (if any, like setup, operators/versions):
Tested on OCP 4.14 and Pipelines 1.14.3
Steps to Reproduce
- Create any pipeline (e.g through new app form)
- Click on "Start Pipeline"
- Scroll down to "Show credential options" and then "add Secret"
- Enter a image Registry / Basic Auth Secret
- Enter username and password
- Run the pipeline
Actual results:
- The pipeline will fail if it is using the secret
- The created secret has no password set (only the username)
Expected results:
- The pipeline succeeds using the secret
- The password is set in the secret
Reproducibility (Always/Intermittent/Only Once):
Always
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):