Skip to content

[release-4.19] OCPBUGS-67264: cherry pick to few fixes that needed for missing services and configuration #5490

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
openshift-cherrypick-robot wants to merge 3 commits into
base: release-4.19
Choose a base branch
from
Open

[release-4.19] OCPBUGS-67264: cherry pick to few fixes that needed for missing services and configuration #5490

openshift-cherrypick-robot wants to merge 3 commits into from

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented Dec 12, 2025

This is an automated cherry-pick of #5480

/assign yuqi-zhang

@aabughosh
Add hostIP 127.0.0.1 to machine-config-daemon port 8798
9f5fb4a 
- Added `hostIP: 127.0.0.1` to the containerPort 8798 to explicitly indicate
  that the health port is only bound to localhost.
- Matches the existing behavior in logs:
    "Starting health listener on 127.0.0.1:8798"
  and address config: Addr: "127.0.0.1:8798"
- This is informational and clarifies that this port is not externally exposed.
@aabughosh
add a relevant svc to the crio port
0a9871c
@aabughosh
add missing ports in contaiterport on the daemoset
507dbb2
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Dec 12, 2025
Merged
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 12, 2025

@openshift-cherrypick-robot: Jira Issue OCPBUGS-65545 has been cloned as Jira Issue OCPBUGS-67264. Will retitle bug to link to clone.

Jira Issue OCPBUGS-67007 has been cloned as Jira Issue OCPBUGS-67265. Will retitle bug to link to clone.
/retitle [release-4.19] OCPBUGS-67264, OCPBUGS-67265: cherry pick to few fixes that needed for missing services and configuration

In response to this:

This is an automated cherry-pick of #5480

/assign yuqi-zhang

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.19] OCPBUGS-65545, OCPBUGS-67007: cherry pick to few fixes that needed for missing services and configuration [release-4.19] OCPBUGS-67264, OCPBUGS-67265: cherry pick to few fixes that needed for missing services and configuration Dec 12, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Dec 12, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 12, 2025

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

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

This pull request references Jira Issue OCPBUGS-67265, which is invalid:

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

In response to this:

This is an automated cherry-pick of #5480

/assign yuqi-zhang

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 Dec 12, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please ask for approval from yuqi-zhang. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@yuqi-zhang yuqi-zhang changed the title [release-4.19] OCPBUGS-67264, OCPBUGS-67265: cherry pick to few fixes that needed for missing services and configuration [release-4.19] OCPBUGS-67264: cherry pick to few fixes that needed for missing services and configuration Dec 12, 2025
@yuqi-zhang
Copy link
Contributor

yuqi-zhang commented Dec 12, 2025

/jira refresh

removed one of the bugs to make it easier to backport

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 12, 2025

@yuqi-zhang: This pull request references Jira Issue OCPBUGS-67264, which is invalid:

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

/jira refresh

removed one of the bugs to make it easier to backport

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.

@yuqi-zhang yuqi-zhang mentioned this pull request Dec 12, 2025
Closed
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 12, 2025

@openshift-cherrypick-robot: 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-gcp-op-single-node 507dbb2 link true /test e2e-gcp-op-single-node
ci/prow/unit 507dbb2 link true /test unit
ci/prow/e2e-gcp-op 507dbb2 link true /test e2e-gcp-op

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.

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

Reviewers

@cheesesashimi cheesesashimi Awaiting requested review from cheesesashimi

@djoshy djoshy Awaiting requested review from djoshy

Assignees

@yuqi-zhang yuqi-zhang

Labels

jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. 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.

4 participants

@openshift-cherrypick-robot @openshift-ci-robot @yuqi-zhang @aabughosh