-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
builds-1.1
-
None
-
False
-
-
False
-
-
Description of problem:
If we create a build requiring git credential before creating the secret and we create the secret after build creation, the build cannot start.
Prerequisites (if any, like setup, operators/versions):
OCP 4.16.17 installed
OpenShift Build Operator 1.1.0 is installed
Steps to Reproduce
# Create a new namespace called redhat-saia
- Create the build (see attachment: build-single-serve-runtimes.yaml
) in the namespace redhat-saia.
- Create the secret git-redhat-saia (see attachment: secret-git-redhat-saia.yaml
I have ofscuated the token,) in the namespace redhat-sais
The build fails to start with BuildRegistrationFailed reason on Succeeded condition with the message: the Build is not registered correctly, build: single-serve-runtimes, registered status: False, reason: SpecSourceSecretRefNotFound
Expected results:
The build start
Workaround: Delete the build and recreate it, it will work.
Reproducibility (Always/Intermittent/Only Once): Always
Acceptance criteria: We should be able to run a build after the referenced secret.git.cloneSecret has been created.
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):
BuildRun YAML buildrun-single-serve-runtimes-fcrl5.yaml
) No logs are generated by the buildrun.
*
- is incorporated by
-
BUILD-1169 Remove "registered secret" feature
-
- Backlog
-
- links to