Bug 1665155
| Summary: | 1/3 machine-config-server pods in CrashLoopBackoff because hypershift is using port 49500 on the master | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Mike Fiedler <mifiedle> | ||||
| Component: | OLM | Assignee: | Evan Cordell <ecordell> | ||||
| Status: | CLOSED UPSTREAM | QA Contact: | Jian Zhang <jiazha> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.1.0 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.1.0 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-01-23 19:18:27 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Not occurring on current builds. |
Created attachment 1519854 [details] System logs from master where 49500 in use Description of problem: After deploying a 4.0 cluster with the v0.9.1 next gen installer (OCP bits, not OKD) Version-Release number of selected component (if applicable): How reproducible: Unknown. I will tear down this cluster and try it again. Steps to Reproduce: 1. _OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE=registry.svc.ci.openshift.org/ocp/release:4.0.0-0.nightly-2019-01-08-152529 2. Run next gen install v0.9.1 to install the standard 3 master/3 node config 3. oc get pods -n openshift-machine-config-operator Actual results: machine-config-server-cmb7b 0/1 CrashLoopBackOff 21 1h [fedora@ip-172-31-53-199 aaa]$ oc logs machine-config-server-cmb7b I0110 15:14:16.689500 1 start.go:37] Version: 4.0.0-0.125.0.0-dirty I0110 15:14:16.690711 1 api.go:53] launching server I0110 15:14:16.690885 1 api.go:53] launching server F0110 15:14:16.691050 1 api.go:61] Machine Config Server exited with error: listen tcp :49500: bind: address already in use Go to the system where that pod is running: [core@ip-10-0-26-87 ~]$ sudo netstat -tunapl | grep 49500 tcp 0 0 10.0.26.87:49500 10.0.45.22:2379 ESTABLISHED 7647/hypershift Expected results: No pods crash looping Additional info: Attaching system logs from the master where 49500 was already in use.