origin: timezone and certification expired
Version
Origin 1.2
Steps To Reproduce
- Choose timezone to Asia/Shanghai install CentOS 7 minimal in a VM, the host machine timezone is Asia/Shanghai too.
- use openshift-ansible to install Origin 1.2
- reboot the VM
Current Result
The openshift-master is not started, and report error as following:
x509: certificate has expired or is not yet valid
Then set the clock to 8 hours(The UTC and CST is differ 8 hours) later in the VM and restart openshift-master and openshift-node service, it will start OK.
Expected Result
start ok.
This is an issue about certification generation, I guess. But after all, I did not find some clue in openshift-ansible or opensfhit origin source code. Does someone meet the same issue or have some suggestions?
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 18 (6 by maintainers)
Okay, so I think I’ve discovered a problem (whether or not it is the problem is another story). It looks like we are currently configuring ntp/chrony after we generate the certs, which could definitely lead to a similar issue as the one reported.