-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.19.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
CORENET Sprint 278
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Warning, I am not a CI expert and I didnt write this job but just from my limited investigated.
The job is failing because we are unable to pull images for k-nmstate:
{ 1 events happened too frequently
event happened 108 times, something is wrong: namespace/openshift-nmstate node/worker-1.ostest.test.metalkube.org pod/nmstate-console-plugin-5964f557cb-zbv8h hmsg/d5bf9afefc - reason/Failed Error: ImagePullBackOff (23:41:45Z) result=reject }
This comes from an operator that we install in this job from here in release using a pre-release source:
./ci-operator/step-registry/baremetalds/e2e/ovn/bgp/dualstack-local-gw/baremetalds-e2e-ovn-bgp-dualstack-local-gw-workflow.yaml
specifically the step called: enable-qe-catalogsource
but according to art team this pre-release source isnt a thing anymore:
We probably dont need to use prerelease sources for this job but i am not sure.
Slack conversations with k-nmstate team: https://redhat-internal.slack.com/archives/CP7329Z5Z/p1760349977738629
Slak conversations with art: https://redhat-internal.slack.com/archives/CJARLA942/p1760354263237459
Version-Release number of selected component (if applicable): 4.19
How reproducible: every time
Steps to Reproduce:
1. run ci on CNO / OVN-K
2.
3.
Actual results:
Expected results:
Additional info:
Please fill in the following template while reporting a bug and provide as much relevant information as possible. Doing so will give us the best chance to find a prompt resolution.
Affected Platforms:
Is it an
- internal CI failure
- Yes
- customer issue / SD
- internal RedHat testing failure
If it is an internal RedHat testing failure:
- Please share a kubeconfig or creds to a live cluster for the assignee to debug/troubleshoot along with reproducer steps (specially if it's a telco use case like ICNI, secondary bridges or BM+kubevirt).
If it is a CI failure:
- Did it happen in different CI lanes? If so please provide links to multiple failures with the same error instance
- Did it happen in both sdn and ovn jobs? If so please provide links to multiple failures with the same error instance
- Did it happen in other platforms (e.g. aws, azure, gcp, baremetal etc) ? If so please provide links to multiple failures with the same error instance
- Just baremetald
- When did the failure start happening? Please provide the UTC timestamp of the networking outage window from a sample failure run
- Some where before 2nd oct
- If it's a connectivity issue,
- What is the srcNode, srcIP and srcNamespace and srcPodName?
- What is the dstNode, dstIP and dstNamespace and dstPodName?
- What is the traffic path? (examples: pod2pod? pod2external?, pod2svc? pod2Node? etc)
If it is a customer / SD issue:
- Provide enough information in the bug description that Engineering doesn’t need to read the entire case history.
- Don’t presume that Engineering has access to Salesforce.
- Do presume that Engineering will access attachments through supportshell.
- Describe what each relevant attachment is intended to demonstrate (failed pods, log errors, OVS issues, etc).
- Referring to the attached must-gather, sosreport or other attachment, please provide the following details:
- If the issue is in a customer namespace then provide a namespace inspect.
- If it is a connectivity issue:
- What is the srcNode, srcNamespace, srcPodName and srcPodIP?
- What is the dstNode, dstNamespace, dstPodName and dstPodIP?
- What is the traffic path? (examples: pod2pod? pod2external?, pod2svc? pod2Node? etc)
- Please provide the UTC timestamp networking outage window from must-gather
- Please provide tcpdump pcaps taken during the outage filtered based on the above provided src/dst IPs
- If it is not a connectivity issue:
- Describe the steps taken so far to analyze the logs from networking components (cluster-network-operator, OVNK, SDN, openvswitch, ovs-configure etc) and the actual component where the issue was seen based on the attached must-gather. Please attach snippets of relevant logs around the window when problem has happened if any.
- When showing the results from commands, include the entire command in the output.
- For OCPBUGS in which the issue has been identified, label with “sbr-triaged”
- For OCPBUGS in which the issue has not been identified and needs Engineering help for root cause, label with “sbr-untriaged”
- Do not set the priority, that is owned by Engineering and will be set when the bug is evaluated
- Note: bugs that do not meet these minimum standards will be closed with label “SDN-Jira-template”
- For guidance on using this template please see
OCPBUGS Template Training for Networking components
