-
Notifications
You must be signed in to change notification settings - Fork 265
[release-4.18] OCPBUGS-47651: Re-disable metrics server #2622
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.
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
[release-4.18] OCPBUGS-47651: Re-disable metrics server #2622
Conversation
The metrics server was incorectly enabled in acd67b4 Revert this behavior by specifying the metrics port in the options. Signed-off-by: Patryk Diak <pdiak@redhat.com>
|
@openshift-cherrypick-robot: Detected clone of Jira Issue OCPBUGS-42189 with correct target version. Will retitle the PR to link to the clone. DetailsIn response to this:
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-cherrypick-robot: This pull request references Jira Issue OCPBUGS-47651, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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. |
|
@pperiyasamy ptal |
|
/jira refresh |
|
@kyrtapz: This pull request references Jira Issue OCPBUGS-47651, which is valid. The bug has been moved to the POST state. 7 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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. |
|
/lgtm Thanks @kyrtapz ! |
|
/label qe-approved build openshift/cluster-network-operator#2622 steps: 1. create 4.18 compact OCP cluster % oc get node NAME STATUS ROLES AGE VERSION ip-10-0-17-167.us-east-2.compute.internal Ready control-plane,master,worker 80m v1.31.4 ip-10-0-44-12.us-east-2.compute.internal Ready control-plane,master,worker 80m v1.31.4 ip-10-0-64-33.us-east-2.compute.internal Ready control-plane,master,worker 80m v1.31.4 2. create hostnetwork pod, listening on port 8080 % oc get pod -n ns1 -owide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES hello-pod 1/1 Running 0 5s 10.0.17.167 ip-10-0-17-167.us-east-2.compute.internal 3. check on the node which hostnetowrk pod lands on, the pod is listening on port 8080 % oc debug node/ip-10-0-17-167.us-east-2.compute.internal Starting pod/ip-10-0-17-167us-east-2computeinternal-debug-swjbq ... To use host binaries, run `chroot /host` Pod IP: 10.0.17.167 If you don't see a command prompt, try pressing enter. sh-5.1# netstat -tulpen | grep 8080 tcp6 0 0 :::8080 :::* LISTEN 1000740000 881647 54436/hello_openshi 4. check the network-operator pod is not in CrashLoopBackOff state, and there is no error message about metrics server % oc get pod -n openshift-network-operator NAME READY STATUS RESTARTS AGE iptables-alerter-4c6wc 1/1 Running 0 81m iptables-alerter-9jxh4 1/1 Running 0 81m iptables-alerter-qp8ps 1/1 Running 0 81m network-operator-7bc857cd77-k8d8d 1/1 Running 2 (72m ago) 83m <--- no CrashLoopBackOff % oc describe pod/network-operator-7bc857cd77-k8d8d -n openshift-network-operator | grep "metrics server" % oc describe pod/network-operator-7bc857cd77-k8d8d -n openshift-network-operator | grep "address already in use" % 5. check cluster-network-operator is not DEGRADED % oc get co | grep network network 4.18.0-0.ci.test-2025-01-21-122114-ci-ln-qlnfv4b-latest True False False 83m |
|
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-47651, which is valid. 7 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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. |
|
/test e2e-aws-ovn-ipsec-upgrade |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kyrtapz, openshift-cherrypick-robot, pperiyasamy The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required |
|
/label backport-risk-assessed |
|
/label cherry-pick-approved |
|
/retest-required |
|
@openshift-cherrypick-robot: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
c1a7028
into
openshift:release-4.18
|
@openshift-cherrypick-robot: Jira Issue OCPBUGS-47651: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-47651 has been moved to the MODIFIED state. DetailsIn response to this:
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. |
|
[ART PR BUILD NOTIFIER] Distgit: cluster-network-operator |
|
Fix included in accepted release 4.18.0-0.nightly-2025-08-06-094134 |
This is an automated cherry-pick of #2516
/assign kyrtapz