console
console copied to clipboard
openshift
[release-4.10] Bug 2101666: [OSD] ClusterVersion YAML editor should be read only
https://bugzilla.redhat.com/show_bug.cgi?id=2101666 https://bugzilla.redhat.com/show_bug.cgi?id=2102096
Signed-off-by: Pavel Kratochvil [email protected]
@raspbeep: This pull request references Bugzilla bug 2101666, which is invalid:
- expected the bug to target the "4.10.z" release, but it targets "---" instead
- expected Bugzilla bug 2101666 to depend on a bug targeting a release in 4.11.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:
Bug 2101666: [OSD] ClusterVersion YAML editor should be read only
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[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @raspbeep. Thanks for your PR.
I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
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.
@raspbeep: This pull request references Bugzilla bug 2101666, which is invalid:
- expected Bugzilla bug 2101666 to depend on a bug targeting a release in 4.11.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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.
@raspbeep: This pull request references Bugzilla bug 2101666, which is invalid:
- expected the bug to target the "4.10.z" release, but it targets "---" instead
- expected Bugzilla bug 2101666 to depend on a bug targeting a release in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:
[release-4.10] Bug 2101666: [OSD] ClusterVersion YAML editor should be read only
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.
@raspbeep: This pull request references Bugzilla bug 2101666, which is invalid:
- expected the bug to target the "4.10.z" release, but it targets "---" instead
- expected Bugzilla bug 2101666 to depend on a bug targeting a release in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:
[release-4.10] Bug 2101666: [OSD] ClusterVersion YAML editor should be read only
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.
@jhadvig: This pull request references Bugzilla bug 2101666, which is invalid:
- expected Bugzilla bug 2101666 to depend on a bug targeting a release in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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.
@raspbeep: This pull request references Bugzilla bug 2101666, which is invalid:
- expected Bugzilla bug 2101666 to depend on a bug targeting a release in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:
[release-4.10] Bug 2101666: [OSD] ClusterVersion YAML editor should be read only
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.
@raspbeep: This pull request references Bugzilla bug 2101666, which is invalid:
- expected Bugzilla bug 2101666 to depend on a bug targeting a release in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:
[release-4.10] Bug 2101666: [OSD] ClusterVersion YAML editor should be read only
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.
@raspbeep: This pull request references [Jira Issue OCPBUGS-382](https://issues.redhat.com//browse/OCPBUGS-382), which is invalid:
- expected [Jira Issue OCPBUGS-382](https://issues.redhat.com//browse/OCPBUGS-382) to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found
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:
https://issues.redhat.com/browse/OCPBUGS-382
Signed-off-by: Pavel Kratochvil [email protected]
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.
@raspbeep: 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.10] OCPBUGS-382: [OSD] ClusterVersion YAML editor should be read only
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.
@jhadvig: This pull request references [Jira Issue OCPBUGS-382](https://issues.redhat.com//browse/OCPBUGS-382), which is invalid:
- expected [Jira Issue OCPBUGS-382](https://issues.redhat.com//browse/OCPBUGS-382) to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found
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
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.
@jhadvig: This pull request references [Jira Issue OCPBUGS-382](https://issues.redhat.com//browse/OCPBUGS-382), which is invalid:
- expected dependent Jira Issue OCPBUGS-383 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is Closed (Current Release) instead
- expected dependent Jira Issue OCPBUGS-383 to target a version in 4.11.0, 4.11.z, but it targets "4.11" 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
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.
@jhadvig: This pull request references [Jira Issue OCPBUGS-382](https://issues.redhat.com//browse/OCPBUGS-382), which is invalid:
- expected dependent Jira Issue OCPBUGS-383 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is Closed (Current Release) 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
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.
@jhadvig: This pull request references [Jira Issue OCPBUGS-382](https://issues.redhat.com//browse/OCPBUGS-382), which is valid. The bug has been moved to the POST state.
6 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.10.z) matches configured target version for branch (4.10.z)
- bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST)
- dependent bug Jira Issue OCPBUGS-383 is in the state Verified (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
- dependent Jira Issue OCPBUGS-383 targets the "4.11.0" version, which is one of the valid target versions: 4.11.0, 4.11.z
- bug has dependents
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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jhadvig, raspbeep
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~frontend/OWNERS~~ [jhadvig]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/retest-required
Remaining retests: 0 against base HEAD 59246a360402d0c8720fb601bea4716e3833a17b and 2 for PR HEAD e9bf66fb6969bb461d404e5ae6bc5a050b1b519a in total
@raspbeep: 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.