OCPBUGS-43834: Enabling topology e2e tests on CI
CI is stable in 4.17 with no topology-ci.feature file issue
@sanketpathak: This pull request references Jira Issue OCPBUGS-43834, which is invalid:
- expected dependent Jira Issue OCPBUGS-39573 to target a version in 4.17.0, 4.17.z, but it targets "4.18.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.
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
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.
/retest
/test e2e-gcp-console
@sanketpathak: 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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: sanketpathak, The-Anton
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~frontend/packages/topology/integration-tests/OWNERS~~ [sanketpathak]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/backport-risk-assessed
/label backport-risk-assessed
@lokanandaprabhu: Can not set label backport-risk-assessed: Must be member in one of these teams: []
In response to this:
/label backport-risk-assessed
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.
/label backport-risk-assessed
/label cherry-pick-approved
/jira refresh
@sanketpathak: This pull request references Jira Issue OCPBUGS-43834, which is invalid:
- expected dependent Jira Issue OCPBUGS-39573 to target a version in 4.17.0, 4.17.z, but it targets "4.18.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
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.
/jira refresh
@sanketpathak: This pull request references Jira Issue OCPBUGS-43834, which is invalid:
- expected the bug to target either version "4.16." or "openshift-4.16.", but it targets "4.15.z" instead
- expected dependent Jira Issue OCPBUGS-39573 to target a version in 4.17.0, 4.17.z, but it targets "4.15.z" 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 openshift-eng/jira-lifecycle-plugin repository.
/jira refresh
@sanketpathak: This pull request references Jira Issue OCPBUGS-43834, 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-39573 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-39573 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
- 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.
@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: sanketpathak.
Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.
In response to this:
@sanketpathak: This pull request references Jira Issue OCPBUGS-43834, 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-39573 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-39573 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
- 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.
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.
@sanketpathak: Jira Issue OCPBUGS-43834: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-43834 has been moved to the MODIFIED state.
In response to this:
CI is stable in 4.17 with no topology-ci.feature file issue
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.
[ART PR BUILD NOTIFIER]
Distgit: openshift-enterprise-console This PR has been included in build openshift-enterprise-console-container-v4.16.0-202411070938.p0.g95cf5fd.assembly.stream.el9. All builds following this will include this PR.
Fix included in accepted release 4.16.0-0.nightly-2024-11-07-112601
/cherry-pick 4.15
@sanketpathak: cannot checkout 4.15: error checking out "4.15": exit status 1 error: pathspec '4.15' did not match any file(s) known to git
In response to this:
/cherry-pick 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.
/cherry-pick release-4.15
@sanketpathak: new pull request created: #14567
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.