Bug 1636925
| Summary: | Node service start failed | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Gaoyun Pei <gpei> | ||||
| Component: | Node | Assignee: | Seth Jennings <sjenning> | ||||
| Status: | CLOSED DEFERRED | QA Contact: | Gaoyun Pei <gpei> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.1.0 | CC: | aos-bugs, jmontleo, jokerman, mmccomas, wmeng | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.1.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||
| Doc Text: |
undefined
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-11-30 16:07:20 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: |
|
||||||
Created attachment 1491567 [details]
Full log of atomic-openshift-node service
This was a temporary issue due to the version of golang being used to build the openshift RPMs changing. I think it is already fixed. https://github.com/openshift/os/pull/346 Please verify. |
Description of problem: During installation, node service failed to get started TASK [openshift_control_plane : fail] ****************************************** Monday 08 October 2018 16:54:03 +0800 (0:00:00.113) 0:07:03.742 ******** fatal: [ec2-54-161-31-205.compute-1.amazonaws.com]: FAILED! => {"changed": false, "msg": "Node start failed."} Errors in the log of atomic-openshift-node service "Oct 08 04:54:02 ip-172-18-14-226.ec2.internal atomic-openshift-node[13459]: boringcrypto: unexpected code execution in /usr/bin/hyperkube", "Oct 08 04:54:02 ip-172-18-14-226.ec2.internal atomic-openshift-node[13459]: E1008 04:54:02.766298 13459 runtime.go:66] Observed a panic: \"boringcrypto: invalid code execution\" (boringcrypto: invalid code execution)", The full node service log could be found in attachment. Version-Release number of the following components: openshift-ansible-4.0.0-0.15.0.git.0.51801c6.el7.noarch.rpm ansible 2.6.5-1.el7ae How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Please include the entire output from the last TASK line through the end of output if an error is generated Expected results: Additional info: Please attach logs from ansible-playbook with the -vvv flag