OCPBUGS-77422: Remove MCD liveness probe

[pablintino]

Closes: #OCPBUGS-77422

- What I did

The current liveness probe implementation triggers a container restart if long-running operations (like rpm-ostree rebases) exceed the timeout.
This causes the MCD to be killed mid-transaction, leading to inconsistent on-disk state and "content mismatch" errors.

Since the MCD does not serve external API traffic and that a restart won't solve most of the failures of a slow or wrong update, removing the probe is the most simple way of preventing inconsistencies till a proper probe is implemented.

- How to verify it

- Description for the changelog

Remove unused MCD liveness probe to avoid mid-update restarts.

[openshift-ci-robot]

@pablintino: This pull request references Jira Issue OCPBUGS-77422, which is invalid:

• expected dependent Jira Issue OCPBUGS-77421 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New 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.

Details

In response to this:

Closes: #OCPBUGS-77422

- What I did

The current liveness probe implementation triggers a container restart if long-running operations (like rpm-ostree rebases) exceed the timeout.
This causes the MCD to be killed mid-transaction, leading to inconsistent on-disk state and "content mismatch" errors.

Since the MCD does not serve external API traffic and that a restart won't solve most of the failures of a slow or wrong update, removing the probe is the most simple way of preventing inconsistencies till a proper probe is implemented.

- How to verify it

- Description for the changelog

Remove unused MCD liveness probe to avoid mid-update restarts.

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.

[isabella-janssen]

/lgtm
/label backport-risk-assessed

Looks like a clean backport.

[openshift-ci]

@pablintino: all tests passed!

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.

[pablintino]

/jira refresh

[openshift-ci-robot]

@pablintino: This pull request references Jira Issue OCPBUGS-77422, 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.17.z) matches configured target version for branch (4.17.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-77421 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-77421 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
• bug has dependents

Requesting review from QA contact:
/cc @sergiordlr

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.

[sdodson]

/label approved
/verified by CI

[openshift-ci-robot]

@sdodson: This PR has been marked as verified by CI.

Details

In response to this:

/label approved
/verified by CI

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]

@pablintino: Jira Issue Verification Checks: Jira Issue OCPBUGS-77422
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-77422 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Closes: #OCPBUGS-77422

- What I did

The current liveness probe implementation triggers a container restart if long-running operations (like rpm-ostree rebases) exceed the timeout.
This causes the MCD to be killed mid-transaction, leading to inconsistent on-disk state and "content mismatch" errors.

Since the MCD does not serve external API traffic and that a restart won't solve most of the failures of a slow or wrong update, removing the probe is the most simple way of preventing inconsistencies till a proper probe is implemented.

- How to verify it

- Description for the changelog

Remove unused MCD liveness probe to avoid mid-update restarts.

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]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: isabella-janssen, pablintino

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:

• OWNERS

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

[openshift-merge-robot]

Fix included in accepted release 4.17.0-0.nightly-2026-03-05-015007