CONSOLE-4287: Restore kubevirt extensions for the topology plugin
This PR restores kubevirt extensions for topology.
Jira: https://issues.redhat.com/browse/CONSOLE-4287
Screenshots
Before
After
@pcbailey: This pull request references CNV-45158 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.18.0" version, but no target version was set.
In response to this:
This PR restores kubevirt extensions for topology.
Jira: https://issues.redhat.com/browse/CNV-45158
Screenshots
Before
After
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.
@pcbailey: This pull request references CNV-45158 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.18.0" version, but no target version was set.
In response to this:
This PR restores kubevirt extensions for topology.
Jira: https://issues.redhat.com/browse/OCPBUGS-42672
Screenshots
Before
After
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.
@pcbailey: This pull request references Jira Issue OCPBUGS-42672, which is invalid:
- expected the bug to target the "4.18.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:
This PR restores kubevirt extensions for topology.
Jira: https://issues.redhat.com/browse/OCPBUGS-42672
Screenshots
Before
After
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
@upalatucci: This pull request references Jira Issue OCPBUGS-42672, 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.18.0) matches configured target version for branch (4.18.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 openshift-eng/jira-lifecycle-plugin repository.
/jira refresh
@pcbailey: This pull request references Jira Issue OCPBUGS-42672, which is valid.
3 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.18.0) matches configured target version for branch (4.18.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 openshift-eng/jira-lifecycle-plugin repository.
/lgtm
/approve
@pcbailey: This pull request references Jira Issue OCPBUGS-42672, which is invalid:
- expected the story to target the "4.18.0" version, but no target version was set
- expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Code Review 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:
This PR restores kubevirt extensions for topology.
Jira: https://issues.redhat.com/browse/CONSOLE-4287
Screenshots
Before
After
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.
@pcbailey: This pull request references CONSOLE-4287 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.
In response to this:
This PR restores kubevirt extensions for topology.
Jira: https://issues.redhat.com/browse/CONSOLE-4287
Screenshots
Before
After
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.
Docs Approver: /assign @opayne1 PX Approver: /assign @reestr QA Approver: /assign @yapei
VirtualMachines can be shown in topology view but I'm consistently seeing Uncaught runtime errors when navigating through virtualization pages, here is one recording
I'm running following bridge commands locally
./bin/bridge -plugins kubevirt-plugin=http://localhost:9001 -i18n-namespaces=plugin__kubevirt-plugin
https://github.com/user-attachments/assets/6dbcf3e4-6604-4ad8-98f6-8e5c103119ab
@yapei i think this pr is not correlated to the error. We are experiencing the issue even on console latest
Thanks @upalatucci You are right, I tried on latest console master and see the same error
Regarding this PR changes, everything looks good so far
/label qe-approved
@pcbailey: This pull request references CONSOLE-4287 which is a valid jira issue.
In response to this:
This PR restores kubevirt extensions for topology.
Jira: https://issues.redhat.com/browse/CONSOLE-4287
Screenshots
Before
After
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.
/lgtm
/retest
New changes are detected. LGTM label has been removed.
/retest
/retest
/retest
/retest
/retest
/retest
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: pcbailey, upalatucci Once this PR has been reviewed and has the lgtm label, please assign jhadvig for approval. For more information see the 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
@pcbailey: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/frontend | 9ab19c4a2fbe9cf38cbb17c288ded4f1e94e2e02 | link | true | /test frontend |
| ci/prow/okd-scos-images | 9ab19c4a2fbe9cf38cbb17c288ded4f1e94e2e02 | link | true | /test okd-scos-images |
| ci/prow/e2e-gcp-console | 9ab19c4a2fbe9cf38cbb17c288ded4f1e94e2e02 | link | true | /test e2e-gcp-console |
| ci/prow/backend | 9ab19c4a2fbe9cf38cbb17c288ded4f1e94e2e02 | link | true | /test backend |
| ci/prow/images | 9ab19c4a2fbe9cf38cbb17c288ded4f1e94e2e02 | link | true | /test images |
| ci/prow/analyze | 9ab19c4a2fbe9cf38cbb17c288ded4f1e94e2e02 | link | true | /test analyze |
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.
These changes are being added to the dynamic kubevirt-plugin.