Skip to content

Conversation

@ncaak
Copy link
Contributor

@ncaak ncaak commented Oct 23, 2025

Bug: In some cases, after a crashloop, the VMs' virt-launcher pods are stuck in Pending status and do not contain a compute container to retrieve the logs from. If any pods are in this situation, the Gatherer receives an error from the API. The Gatherer then returns with the error, but not with logs from the pods that are running normally.
Fix: Only gathering logs from the virt-launcher pods that are in Running status.

Categories

  • Bugfix
  • Data Enhancement
  • Feature
  • Backporting
  • Others (CI, Infrastructure, Documentation)

Documentation

  • docs/gathered-data.md

Breaking Changes

No

References

https://issues.redhat.com/browse/OCPBUGS-63015

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 23, 2025
@openshift-ci-robot
Copy link
Contributor

@ncaak: This pull request references Jira Issue OCPBUGS-63015, which is invalid:

  • expected the bug to target the "4.21.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:

Bug: In some cases, after a crashloop, the VMs' virt-launcher pods are stuck in Pending status and do not contain a compute container to retrieve the logs from. If any pods are in this situation, the Gatherer receives an error from the API. The Gatherer then returns with the error, but not with logs from the pods that are running normally.
Fix: Only gathering logs from the virt-launcher pods that are in Running status.

Categories

  • Bugfix
  • Data Enhancement
  • Feature
  • Backporting
  • Others (CI, Infrastructure, Documentation)

Documentation

  • docs/gathered-data.md

Breaking Changes

No

References

https://issues.redhat.com/browse/OCPBUGS-63015

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 openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Oct 23, 2025
@openshift-ci
Copy link

openshift-ci bot commented Oct 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ncaak

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 23, 2025
@ncaak
Copy link
Contributor Author

ncaak commented Oct 23, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 23, 2025
@openshift-ci-robot
Copy link
Contributor

@ncaak: This pull request references Jira Issue OCPBUGS-63015, 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.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @BaiyangZhou

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 openshift-ci bot requested a review from BaiyangZhou October 23, 2025 08:35
@ncaak
Copy link
Contributor Author

ncaak commented Oct 23, 2025

/verified later @BaiyangZhou

@openshift-ci-robot openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Oct 23, 2025
@openshift-ci-robot
Copy link
Contributor

@ncaak: This PR has been marked to be verified later by @BaiyangZhou.

In response to this:

/verified later @BaiyangZhou

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.

@ncaak
Copy link
Contributor Author

ncaak commented Oct 23, 2025

/test e2e-gcp-ovn-techpreview

@ncaak
Copy link
Contributor Author

ncaak commented Oct 23, 2025

/test okd-scos-e2e-aws-ovn

3 similar comments
@ncaak
Copy link
Contributor Author

ncaak commented Oct 24, 2025

/test okd-scos-e2e-aws-ovn

@ncaak
Copy link
Contributor Author

ncaak commented Oct 24, 2025

/test okd-scos-e2e-aws-ovn

@ncaak
Copy link
Contributor Author

ncaak commented Oct 24, 2025

/test okd-scos-e2e-aws-ovn

return common.LogContainersFilter{
Namespace: metav1.NamespaceAll,
LabelSelector: "kubevirt.io=virt-launcher",
FieldSelector: "status.phase=Running",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you also consider gathering data from containers that are marked as Succeeded or Failed? Or is the Running phase sufficient for us?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that's the work I'm checking on other ticket → OCPBUGS-63396

@BaiyangZhou
Copy link

/test okd-scos-e2e-aws-ovn

@openshift-ci
Copy link

openshift-ci bot commented Oct 27, 2025

@ncaak: 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.

@opokornyy
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 27, 2025
@BaiyangZhou
Copy link

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Oct 27, 2025
@openshift-ci-robot
Copy link
Contributor

@ncaak: This pull request references Jira Issue OCPBUGS-63015, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @BaiyangZhou

In response to this:

Bug: In some cases, after a crashloop, the VMs' virt-launcher pods are stuck in Pending status and do not contain a compute container to retrieve the logs from. If any pods are in this situation, the Gatherer receives an error from the API. The Gatherer then returns with the error, but not with logs from the pods that are running normally.
Fix: Only gathering logs from the virt-launcher pods that are in Running status.

Categories

  • Bugfix
  • Data Enhancement
  • Feature
  • Backporting
  • Others (CI, Infrastructure, Documentation)

Documentation

  • docs/gathered-data.md

Breaking Changes

No

References

https://issues.redhat.com/browse/OCPBUGS-63015

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-merge-bot openshift-merge-bot bot merged commit b84f719 into openshift:master Oct 27, 2025
11 checks passed
@openshift-ci-robot
Copy link
Contributor

@ncaak: Jira Issue OCPBUGS-63015: All pull requests linked via external trackers have merged:

This pull request has the verified-later tag and will need to be manually moved to VERIFIED after testing. Jira Issue OCPBUGS-63015 has been moved to the MODIFIED state.

In response to this:

Bug: In some cases, after a crashloop, the VMs' virt-launcher pods are stuck in Pending status and do not contain a compute container to retrieve the logs from. If any pods are in this situation, the Gatherer receives an error from the API. The Gatherer then returns with the error, but not with logs from the pods that are running normally.
Fix: Only gathering logs from the virt-launcher pods that are in Running status.

Categories

  • Bugfix
  • Data Enhancement
  • Feature
  • Backporting
  • Others (CI, Infrastructure, Documentation)

Documentation

  • docs/gathered-data.md

Breaking Changes

No

References

https://issues.redhat.com/browse/OCPBUGS-63015

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-merge-robot
Copy link
Contributor

Fix included in accepted release 4.21.0-0.nightly-2025-10-30-060549

@ncaak
Copy link
Contributor Author

ncaak commented Nov 7, 2025

/cherry-pick release-4.20

@openshift-cherrypick-robot

@ncaak: new pull request created: #1174

In response to this:

/cherry-pick release-4.20

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR verified Signifies that the PR passed pre-merge verification criteria verified-later

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants