Hide Forgot
Description of problem: For system rolling restart. I can't see the warning message. I also have no way to abort the 'system restart'. Version-Release number of selected component (if applicable): atomic-openshift-utils-3.0.29-1 How reproducible: always Steps to Reproduce: 1. in inventory file: set openshift_rolling_restart_mode=system 2. ansible-playbook -i /root/config/ose31nativeha /root/openshift-ansible/playbooks/byo/openshift-master/restart.yml Actual results: Masters were restart by rolling. But there are no window to display warning message and the user can't abort 'system restart' Expected results: 1) The following message should be received by all Terminal. Warning: Running playbook from a host that will be restarted! Press CTRL+C and A to abort playbook execution. You may continue by pressing ENTER but the playbook will stop executing once this system restarts and services must be manually verified. 2) There is time for admin to abort 'system restart' Additional info:
Are you running ansible from a host outside the cluster or on a host which will be rebooted as part of the rolling restart? The message should only be shown when running the playbook from a host that will be rebooted, such as the first master.
(In reply to Andrew Butcher from comment #2) > Are you running ansible from a host outside the cluster or on a host which > will be rebooted as part of the rolling restart? The message should only be > shown when running the playbook from a host that will be rebooted, such as > the first master. Oh,I am running outside masters. Will try to run on master soon.
Andrew, yes, the warning message works well if the ansible is running on masters. On question is about the post step if Enter is press. Could you just restart service rather than restart system?
We will continue with system restarts if the user decides to continue since they configured openshift_rolling_restart_mode=system, but we'll the update the message and call attention to the openshift_rolling_restart_mode variable, letting the user know they can change the restart method to 'services' and relaunch the playbook.