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
Build macos oc
binary with CGO_ENABLED=1 so that it honours /etc/resolver?
#23266
Comments
This will allow us to add instance IP on fly so user doesn't need to do it manually. As preflight check we are also changing the permission for host /etc/resolv.conf file to provide RW access to current user. Upstream side issue to make sure oc should honour the resolver file. - openshift/origin#23266
especially: golang/go#12524 (comment) Enabling |
After building
The binary from
|
oc
doesn't honour /etc/resolver for mac.oc
binary with CGO_ENABLED=1 so that it honours /etc/resolver?
kubernetes/kubernetes#23130 upstream issue from kubernetes side. |
This seems to impact odo as well - does that need to be raised as a separate issue in their tracker? |
Note this affects |
@derekwaynecarr how to handle this? So far we haven't gotten anywhere with this and it affects us on macOS, and we find out the workaround with |
Does |
I just tried it, and yes it behaves the same, it needs an entry in /etc/hosts and is not making use of /etc/resolver/ |
There is no impact to the software delivered, but rather inthe build process as Apple-branded hardware needs to be involved, although this can be solved by using CircleCI. |
If we want that fixed, this has to be fixed upstream first, imo. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/lifecycle frozen |
This issue is solved in openshift/oc#315 |
/close |
@praveenkumar: Closing this issue. In 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 kubernetes/test-infra repository. |
Version
Steps To Reproduce
/etc/resolve.conf
but use/etc/resolver/<whatever_dns>
, in our case we use/etc/resolver/testing
./etc/resolv.conf
Current Result
User need to add the dns details to
/etc/resolv.conf
, where most of the app on the Mac does honour the resolver file and works.Expected Result
Openshift client binary should also honour the
resolver
directory files.Additional Information
[try to run
$ oc adm diagnostics
(oroadm diagnostics
) command if possible][if you are reporting issue related to builds, provide build logs with
BUILD_LOGLEVEL=5
][consider attaching output of the
$ oc get all -o json -n <namespace>
command to the issue][visit https://docs.openshift.org/latest/welcome/index.html]
The text was updated successfully, but these errors were encountered: