I cannot recreate the issue. Can you include the full error message:
oauthConfig.identityProvider.provider.bindPassword.file: Invalid value: "/tmp/bindpassword....
Does the user the openshift process is starting as have read permissions to /tmp/bindpassword.txt
The '/etc/origin/master/bindpassword.txt' is working well one and '/tmp/bindpassword.txt' doesn't work well for 'systemctl restart aotmic-openshift-master':
# ls -lahZ /tmp/bindpassword.txt
-rw-r--r--. root root unconfined_u:object_r:user_tmp_t:s0 /tmp/bindpassword.txt
# ls -lahZ /etc/origin/master/bindpassword.txt
-rw-r--r--. root root unconfined_u:object_r:etc_t:s0 /etc/origin/master/bindpassword.txt
# md5sum /tmp/bindpassword.txt
# md5sum /etc/origin/master/bindpassword.txt
@Ge could you try using https://github.com/openshift/origin/pull/12761 ?
@Ge that PR is merged now so the latest master should give better logging info.
Verified in openshift:
# ls -lahZ bindpassword.txt
-rw-r--r--. root root unconfined_u:object_r:user_tmp_t:s0 bindpassword.txt
# ls -lahZ /root/openshift.local.config/master/bindpassword.txt
-rw-r--r--. root root unconfined_u:object_r:admin_home_t:s0 /root/openshift.local.config/master/bindpassword.txt
@Ge new master logs please.
@Mo, I also read the logs before sent to u, and could not find the /tmp/bindpassword info even if I really used this in master-config.yaml file, but could find the login user: 'newton' info, I suppose you could find the critical infomation by reading log. I used the '--loglevel=5' when starting openshift, I'm not sure if it's enough. BTW, the difference between I filing the bug and verify it is: I filing the buy on ocp enc, so I could get the error msg by 'journalctl -l -u atomic-openshift-master', and verify it on origin env and used 'openshift start' mode, so 'journalctl' could not find the righ service name for openshift, I can only get the master log by "openshift start xxxxx &> master.log", it there any idea for this situation?
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.