[release-4.3] Bug 1808061: Set the correct namespace for SCC when installed in non default namespace

[openshift-cherrypick-robot]

This is an automated cherry-pick of #68

/assign zvonkok

[openshift-ci-robot]

@openshift-cherrypick-robot: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-4.3] Set the correct namespace for SCC when installed in non default 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.

[ArangoGutierrez]

/test e2e-aws-upgrade

[ArangoGutierrez]

/lgtm

[ArangoGutierrez]

/assign @zvonkok

[ArangoGutierrez]

/retest

[ArangoGutierrez]

/test e2e-aws-upgrade

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Bugzilla bug 1808061, which is invalid:

• expected dependent Bugzilla bug 1807620 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead

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

In response to this:

[release-4.3] Bug 1808061: Set the correct namespace for SCC when installed in non default 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.

[zvonkok]

/bugzilla refresh

[openshift-ci-robot]

@zvonkok: This pull request references Bugzilla bug 1808061, which is invalid:

• expected dependent Bugzilla bug 1807620 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead

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

In response to this:

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

[zvonkok]

/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ArangoGutierrez, openshift-cherrypick-robot, zvonkok

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:

• OWNERS [zvonkok]

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

[zvonkok]

/cherrypick release-4.2

[openshift-cherrypick-robot]

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

In response to this:

/cherrypick release-4.2

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.

[ArangoGutierrez]

/bugzilla refresh

[openshift-ci-robot]

@ArangoGutierrez: This pull request references Bugzilla bug 1808061, which is invalid:

• expected Bugzilla bug 1808061 to depend on a bug targeting the "4.4.0" release and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but no dependents were found

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

In response to this:

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

[zvonkok]

/bugzilla refresh

[openshift-ci-robot]

@zvonkok: This pull request references Bugzilla bug 1808061, which is invalid:

• expected Bugzilla bug 1808061 to depend on a bug targeting the "4.4.0" release and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but no dependents were found

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

In response to this:

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

[zvonkok]

/bugzilla refresh

[openshift-ci-robot]

@zvonkok: This pull request references Bugzilla bug 1808061, which is invalid:

• expected dependent Bugzilla bug 1807620 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead

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

In response to this:

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

[zvonkok]

/bugzilla refresh

[openshift-ci-robot]

@zvonkok: This pull request references Bugzilla bug 1808061, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.3.z) matches configured target release for branch (4.3.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 1807620 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
• dependent Bugzilla bug 1807620 targets the "4.4.0" release, matching the expected (4.4.0) release
• bug has dependents

In response to this:

/bugzilla 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-cherrypick-robot]

@zvonkok: #69 failed to apply on top of branch "release-4.2":

error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	pkg/controller/nodefeaturediscovery/nodefeaturediscovery_controls.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/controller/nodefeaturediscovery/nodefeaturediscovery_controls.go
CONFLICT (content): Merge conflict in pkg/controller/nodefeaturediscovery/nodefeaturediscovery_controls.go
Patch failed at 0001 Set the correct namespace for SCC when installed in non default namespace

In response to this:

/cherrypick release-4.2

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-robot]

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged. Bugzilla bug 1808061 has been moved to the MODIFIED state.

In response to this:

[release-4.3] Bug 1808061: Set the correct namespace for SCC when installed in non default 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.

[zvonkok]

/cherrypick release-4.2

[openshift-cherrypick-robot]

@zvonkok: new pull request created: #79

In response to this:

/cherrypick release-4.2

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.