-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Revert back to hostnamectl and previous default of not setting hostname #5340
Conversation
CC: @detiber |
@sdodson note that the hostname module SHOULD work on atomic host, once we have ansible 2.4. |
The old default was "{{ not openshift.common.version_gte_3_1_or_1_1 }}" just default to false instead, master branch will never be used with 3.0 hostname module doesn't work on atomic host Fixes BZ 1489913
thanks, amended my comment with a link to that |
aos-ci-test |
1 similar comment
aos-ci-test |
[test] |
Evaluated for openshift ansible test up to f255cca |
continuous-integration/openshift-jenkins/test FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_openshift_ansible/638/) (Base Commit: 69f0384) (PR Branch Commit: f255cca) |
did positive and negative testing locally. |
The old default was "{{ not openshift.common.version_gte_3_1_or_1_1 }}"
just default to false instead, master branch will never be used with 3.0
hostname module doesn't work on atomic host
Fixes BZ 1489913