Skip to content
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.

Sign up for GitHub

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

Jump to bottom

TektonResult installation fails if targerNamespace is different #2023

Closed
khrm opened this issue Feb 22, 2024 · 1 comment · Fixed by #2022
Closed

TektonResult installation fails if targerNamespace is different #2023

khrm opened this issue Feb 22, 2024 · 1 comment · Fixed by #2022
Assignees
@khrm
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@khrm
Copy link
Contributor

khrm commented Feb 22, 2024

Expected Behavior

Tekton Result should installed and we should get:

 oc get TektonResult result -w
result   v0.9.1    True

Actual Behavior

Installation fails and we get:

 oc get TektonResult result -w
NAME     VERSION   READY   REASON
result   v0.9.1    False   Installer set not ready: Install failed with message: namespaces "tekton-pipelines" not found

Steps to Reproduce the Problem

  1. Install v0.70 operator
  2. Instal TektonResult CR.
@khrm khrm added the kind/bug Categorizes issue or PR as related to a bug. label Feb 22, 2024
@khrm
Copy link
Contributor Author

khrm commented Feb 22, 2024

/assign @khrm

@khrm khrm mentioned this issue Feb 22, 2024
Merged
4 tasks
@khrm khrm changed the title TektonResult installaiton fails if targerNamespace is different TektonResult installation fails if targerNamespace is different Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@khrm khrm

Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix filter and Transform for TektonResult khrm/operator
1 participant
@khrm