| Summary: | OpenShift v3.3 MacOSX Client fails after Mac OSX update to Sierra | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Rafael Benevides <benevides> | ||||
| Component: | oc | Assignee: | Fabiano Franz <ffranz> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Peter Ruan <pruan> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.3.0 | CC: | aos-bugs, ffranz, jcajka, jokerman, mmccomas, nschuetz, sdodson, xiaocwan, xxia | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.3.1 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Cause:
Binaries compiled with Golang versions prior to 1.7 will segfault most of the times in macOS Sierra (10.12) given incompatibilities between the Go syscall wrappers and Darwin.
Consequence:
Users of the OpenShift command-line tools ('oc', 'oadm', and others) in macOS Sierra (10.12) get a stack trace in the attempt of running commands.
Fix:
The Go 1.7 fix was backported by the go-tools team to Go 1.6 which was then used to compile our command-line tools in this release.
Result:
Users of the OpenShift command-line tools can use it normally in macOS Sierra (10.12).
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-10-27 15:42:48 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: | |||||
| Bug Depends On: | 1381593 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Rafael Benevides
2016-09-29 23:59:05 UTC
Created attachment 1209019 [details]
macOS_version
been using the patch for a couple of days with no trackback occurring, marking bug as VERIFIED. I'm moving this back to modified so that we make sure to test with an official build, 3.3.1.2 or later. It was previously verified via a test build. Test again on client/servier 3.3.1.2 on Mac Sierra and it does not reproduce. Peter, could you please help to test again? This could be marked as VERIFIED if not reproduced ever again. I've verified it with 3.3.1.1 and 3.3.1.3, I don't see the traceback anymore. Moving it to VERIFIED. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:2084 |