OCPBUGS-18439: use active namespace in Create cta href of create action for operator backed

[vikram-raj]

Fixes: https://issues.redhat.com/browse/OCPBUGS-18439

Descriptions:

• Use active namespace instead of reading the namespace from the csv metadata as if disableCopiedCSVs is true then we get the csvs from the Openshift namespace.

GIF:

Screen.Recording.2023-09-04.at.7.43.33.PM.mov

Test steps:

1. Install Camel-k operator (community version, stable channel)
2. Disable copies of CSV by setting 'OLMConfig.spec.features.disableCopiedCSVs' to 'true'
3. Create a new namespace/project
4. Go to Developer Catalog -> Operator backed
5. Select operator backed Integration card and click on create
6. Click on Create
7. On the Search page select the Integration resource. and You will see the Integration is being created in the active namespace

[openshift-ci-robot]

@vikram-raj: This pull request references Jira Issue OCPBUGS-18439, which is invalid:

• expected the bug to target the "4.14.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Fixes: https://issues.redhat.com/browse/OCPBUGS-18439

Descriptions:

• Use active namespace instead of reading the namespace from the csv metadata as if disableCopiedCSVs is true then we get the csvs from the Openshift namespace.

GIF:

Screen.Recording.2023-09-04.at.7.43.33.PM.mov

Test steps:

1. Install Camel-k operator (community version, stable channel)
2. Disable copies of CSV by setting 'OLMConfig.spec.features.disableCopiedCSVs' to 'true'
3. Create a new namespace/project
4. Go to Developer Catalog -> Operator backed
5. Select operator backed Integration card and click on create
6. Click on Create
7. On the Search page select the Integration resource. and You will see the Integration is being created in the active namespace

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[vikram-raj]

/jira refresh

[openshift-ci-robot]

@vikram-raj: This pull request references Jira Issue OCPBUGS-18439, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.14.0) matches configured target version for branch (4.14.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[vikram-raj]

/cc @jerolimov

[lokanandaprabhu]

Tested using cluster bot. Working fine.

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lokanandaprabhu, vikram-raj

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• frontend/packages/operator-lifecycle-manager/OWNERS [vikram-raj]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[vikram-raj]

/label acknowledge-critical-fixes-only

[vikram-raj]

/cherry-pick release-4.13

[openshift-cherrypick-robot]

@vikram-raj: once the present PR merges, I will cherry-pick it on top of release-4.13 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.13

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-bot]

/jira refresh

The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.

[openshift-ci-robot]

@openshift-bot: This pull request references Jira Issue OCPBUGS-18439, which is invalid:

• expected the bug to target the "4.15.0" version, but it targets "4.14.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[vikram-raj]

/jira refresh

[openshift-ci-robot]

@vikram-raj: This pull request references Jira Issue OCPBUGS-18439, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.15.0) matches configured target version for branch (4.15.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci]

@vikram-raj: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[openshift-ci-robot]

@vikram-raj: Jira Issue OCPBUGS-18439: All pull requests linked via external trackers have merged:

• openshift/console#13132

Jira Issue OCPBUGS-18439 has been moved to the MODIFIED state.

In response to this:

Fixes: https://issues.redhat.com/browse/OCPBUGS-18439

Descriptions:

• Use active namespace instead of reading the namespace from the csv metadata as if disableCopiedCSVs is true then we get the csvs from the Openshift namespace.

GIF:

Screen.Recording.2023-09-04.at.7.43.33.PM.mov

Test steps:

1. Install Camel-k operator (community version, stable channel)
2. Disable copies of CSV by setting 'OLMConfig.spec.features.disableCopiedCSVs' to 'true'
3. Create a new namespace/project
4. Go to Developer Catalog -> Operator backed
5. Select operator backed Integration card and click on create
6. Click on Create
7. On the Search page select the Integration resource. and You will see the Integration is being created in the active namespace

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-cherrypick-robot]

@vikram-raj: new pull request created: #13143

In response to this:

/cherry-pick release-4.13

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[vikram-raj]

/cherry-pick release-4.14

[openshift-cherrypick-robot]

@vikram-raj: new pull request created: #13150

In response to this:

/cherry-pick release-4.14

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-merge-robot]

Fix included in accepted release 4.15.0-0.nightly-2023-09-14-125123

[openshift-merge-robot]

Fix included in accepted release 4.15.0-0.nightly-2023-09-15-090049

[openshift-merge-robot]

Fix included in accepted release 4.15.0-0.nightly-2023-09-16-110027