Skip to content

Comments

[release-4.20] OCPBUGS-72558: SyncState shouldn't assume ANTENNA-DISCONNECTED#624

Merged
openshift-merge-bot[bot] merged 1 commit intoredhat-cne:release-4.20from
openshift-cherrypick-robot:cherry-pick-613-to-release-4.20
Jan 14, 2026
Merged

[release-4.20] OCPBUGS-72558: SyncState shouldn't assume ANTENNA-DISCONNECTED#624
openshift-merge-bot[bot] merged 1 commit intoredhat-cne:release-4.20from
openshift-cherrypick-robot:cherry-pick-613-to-release-4.20

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #613

/assign josephdrichard

ANTENNA-DISCONNECTED is only intended for when the antenna is disconnected,
so we shouldn't use it as a catch-all for GNSS failures.

Fix is ti default to FAILURE-NOFIX rather than ANTENNA-DISCONNECTED
as the reason for loss of GNSS.
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-63435 has been cloned as Jira Issue OCPBUGS-72558. Will retitle bug to link to clone.
/retitle [release-4.20] OCPBUGS-72558: SyncState shouldn't assume ANTENNA-DISCONNECTED

Details

In response to this:

This is an automated cherry-pick of #613

/assign josephdrichard

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 changed the title [release-4.20] OCPBUGS-63435: SyncState shouldn't assume ANTENNA-DISCONNECTED [release-4.20] OCPBUGS-72558: SyncState shouldn't assume ANTENNA-DISCONNECTED Jan 9, 2026
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-72558, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

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.

Details

In response to this:

This is an automated cherry-pick of #613

/assign josephdrichard

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.

@nocturnalastro
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link

@nocturnalastro: This pull request references Jira Issue OCPBUGS-72558, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

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.

Details

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.

@josephdrichard
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link

@josephdrichard: This pull request references Jira Issue OCPBUGS-72558, 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.20.z) matches configured target version for branch (4.20.z)
  • bug is in the state ASSIGNED, 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-63435 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-63435 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
  • bug has dependents

Requesting review from QA contact:
/cc @yliu127

Details

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

openshift-ci bot commented Jan 14, 2026

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: yliu127.

Note that only redhat-cne members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

@josephdrichard: This pull request references Jira Issue OCPBUGS-72558, 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.20.z) matches configured target version for branch (4.20.z)
  • bug is in the state ASSIGNED, 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-63435 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-63435 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
  • bug has dependents

Requesting review from QA contact:
/cc @yliu127

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.

@nocturnalastro
Copy link
Contributor

/label backport-risk-assessed

@nocturnalastro
Copy link
Contributor

/approved

@nocturnalastro
Copy link
Contributor

/verified later @hhassid

@openshift-ci-robot
Copy link

@nocturnalastro: This PR has been marked to be verified later by @hhassid.

Details

In response to this:

/verified later @hhassid

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.

@nocturnalastro
Copy link
Contributor

/lgtm

@nocturnalastro
Copy link
Contributor

/approved

@nocturnalastro
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 14, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nocturnalastro, openshift-cherrypick-robot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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-merge-bot openshift-merge-bot bot merged commit 62de5d1 into redhat-cne:release-4.20 Jan 14, 2026
9 of 15 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-72558: 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-72558 has been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #613

/assign josephdrichard

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.

@josephdrichard
Copy link
Contributor

/cherry-pick release-4.19

@openshift-cherrypick-robot
Copy link
Author

@josephdrichard: new pull request created: #625

Details

In response to this:

/cherry-pick release-4.19

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants