Skip to content

NO-JIRA: test(tnf): add Pacemaker health check scenarios and shared two-node utils#30764

Open
jaypoulz wants to merge 1 commit intoopenshift:mainfrom
jaypoulz:tnf-healthcheck-updates
Open

NO-JIRA: test(tnf): add Pacemaker health check scenarios and shared two-node utils#30764
jaypoulz wants to merge 1 commit intoopenshift:mainfrom
jaypoulz:tnf-healthcheck-updates

Conversation

@jaypoulz
Copy link
Contributor

@jaypoulz jaypoulz commented Feb 5, 2026

  • Add tnf_pacemaker_healthcheck.go with disruptive scenarios for Pacemaker health check (degraded/healthy transitions, stale status, etc.).
  • Extend TNF kubelet disruption, node replacement, and recovery tests.
  • Add shared utilities in utils/common.go and utils/services/pacemaker.go for two-node topology and Pacemaker service checks.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 5, 2026

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 5, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 5, 2026

@jaypoulz: This pull request explicitly references no jira issue.

Details

In response to this:

  • Add tnf_pacemaker_healthcheck.go with disruptive scenarios for Pacemaker health check (degraded/healthy transitions, stale status, etc.).
  • Extend TNF kubelet disruption, node replacement, and recovery tests.
  • Add shared utilities in utils/common.go and utils/services/pacemaker.go for two-node topology and Pacemaker service checks.

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 review from jeff-roche and qJkee February 5, 2026 18:43
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 5, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jaypoulz

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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 5, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 5, 2026

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@jaypoulz jaypoulz force-pushed the tnf-healthcheck-updates branch from 31b50db to 1da8eaa Compare February 5, 2026 21:33
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 5, 2026

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@openshift-trt
Copy link

openshift-trt bot commented Feb 6, 2026

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: 1da8eaa

  • "[Monitor:audit-log-analyzer][Jira:"Test Framework"] operator service account vmware-vsphere-csi-driver-operator should not create excessive watch requests" [Total: 2, Pass: 2, Fail: 0, Flake: 0]
  • "[Monitor:audit-log-analyzer][Jira:"Test Framework"] operator service account vsphere-problem-detector-operator should not create excessive watch requests" [Total: 2, Pass: 2, Fail: 0, Flake: 0]

@jaypoulz jaypoulz force-pushed the tnf-healthcheck-updates branch 3 times, most recently from 638b174 to d2b7007 Compare February 7, 2026 01:40
@jaypoulz @cursoragent @claude
NO-JIRA: test(tnf): add Pacemaker health check scenarios and shared t…
54d5efd 
…wo-node utils

- Add tnf_pacemaker_healthcheck.go with disruptive scenarios for Pacemaker
  health check (degraded/healthy transitions, stale status, etc.).
- Extend TNF kubelet disruption, node replacement, and recovery tests.
- Add shared utilities in utils/common.go and utils/services/pacemaker.go
  for two-node topology and Pacemaker service checks.

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Claude <noreply@anthropic.com>
@jaypoulz jaypoulz force-pushed the tnf-healthcheck-updates branch from d2b7007 to 54d5efd Compare February 7, 2026 02:38
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 7, 2026

@jaypoulz: 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/e2e-aws-ovn-serial-2of2 1da8eaa link true /test e2e-aws-ovn-serial-2of2
ci/prow/e2e-aws-ovn-microshift 1da8eaa link true /test e2e-aws-ovn-microshift
ci/prow/e2e-metal-ipi-ovn-ipv6 1da8eaa link true /test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-aws-ovn-serial-1of2 1da8eaa link true /test e2e-aws-ovn-serial-1of2
ci/prow/verify 54d5efd link true /test verify

Full PR test history. Your PR dashboard.

Details

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.

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

Reviewers

@jeff-roche jeff-roche Awaiting requested review from jeff-roche

@qJkee qJkee Awaiting requested review from qJkee

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@jaypoulz @openshift-ci-robot