console
console copied to clipboard
openshift
[release-4.16] OCPBUGS-41993: Console user settings resources misses ownerRef, removing a user results in remaining data
This is an automated cherry-pick of #14240
/assign Lucifergene
@openshift-cherrypick-robot: Jira Issue OCPBUGS-39601 has been cloned as Jira Issue OCPBUGS-41993. Will retitle bug to link to clone. /retitle [release-4.16] OCPBUGS-41993: Console user settings resources misses ownerRef, removing a user results in remaining data
In response to this:
This is an automated cherry-pick of #14240
/assign Lucifergene
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 openshift-eng/jira-lifecycle-plugin repository.
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-41993, which is invalid:
- expected dependent Jira Issue OCPBUGS-39601 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
This is an automated cherry-pick of #14240
/assign Lucifergene
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 openshift-eng/jira-lifecycle-plugin repository.
@openshift-cherrypick-robot: 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-sigs/prow repository. I understand the commands that are listed here.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@Lucifergene: This pull request references Jira Issue OCPBUGS-41993, which is valid. The bug has been moved to the POST state.
7 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.16.z) matches configured target version for branch (4.16.z)
- bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
- release note text is set and does not match the template
- dependent bug Jira Issue OCPBUGS-39601 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
- dependent Jira Issue OCPBUGS-39601 targets the "4.17.0" version, which is one of the valid target versions: 4.17.0
- bug has dependents
Requesting review from QA contact: /cc @sanketpathak
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 openshift-eng/jira-lifecycle-plugin repository.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Lucifergene, openshift-cherrypick-robot Once this PR has been reviewed and has the lgtm label, please assign florkbr for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@Lucifergene: once the present PR merges, I will cherry-pick it on top of release-4.15 in a new PR and assign it to you.
In response to this:
/cherry-pick release-4.15
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-sigs/prow repository.
@vikram-raj: GitHub didn't allow me to assign the following users: jhadvig.
Note that only openshift members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
In response to this:
/assign @jhadvig
For Approve
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-sigs/prow repository.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
Not needed in 4.16 as we did this change for Sandbox cluster and they are moving to 4.17.
/close
@vikram-raj: Closed this PR.
In response to this:
Not needed in 4.16 as we did this change for Sandbox cluster and they are moving to 4.17.
/close
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-sigs/prow repository.
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-41993. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.
In response to this:
This is an automated cherry-pick of #14240
/assign Lucifergene
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 openshift-eng/jira-lifecycle-plugin repository.