Bug 1489014 - Installing openshift with cri-o fails - node service does not start
Summary: Installing openshift with cri-o fails - node service does not start
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.7.0
Assignee: Scott Dodson
QA Contact: Vikas Laad
URL:
Whiteboard:
Depends On: 1493714
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-06 15:13 UTC by Vikas Laad
Modified: 2017-11-01 12:05 UTC (History)
5 users (show)

Fixed In Version: openshift-ansible-3.7.0-0.125.1.git.0.99e6845
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-11-01 12:04:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Vikas Laad 2017-09-06 15:13:20 UTC 
Description of problem:
Installer fails with error node service failed to start.

Sep  5 18:58:04 ip-172-31-61-65 atomic-openshift-node: I0905 18:58:04.770138   13841 start_node.go:251] Reading node configuration from /etc/origin/node/node-config.yaml
Sep  5 18:58:04 ip-172-31-61-65 atomic-openshift-node: Invalid NodeConfig /etc/origin/node/node-config.yaml
Sep  5 18:58:04 ip-172-31-61-65 atomic-openshift-node: flag: Invalid value: "experimental-cri": is not a valid flag
Sep  5 18:58:04 ip-172-31-61-65 systemd: atomic-openshift-node.service: main process exited, code=exited, status=255/n/a
Sep  5 18:58:04 ip-172-31-61-65 dnsmasq[12792]: setting upstream servers from DBus
Sep  5 18:58:04 ip-172-31-61-65 dnsmasq[12792]: using nameserver 172.31.0.2#53
Sep  5 18:58:04 ip-172-31-61-65 systemd: Failed to start OpenShift Node.
Sep  5 18:58:04 ip-172-31-61-65 systemd: Unit atomic-openshift-node.service entered failed state.
Sep  5 18:58:04 ip-172-31-61-65 systemd: atomic-openshift-node.service failed.


Version-Release number of the following components:
rpm -q openshift-ansible 
openshift-ansible-3.7.0-0.123.0.git.0.248cba6.el7.noarch

rpm -q ansible
ansible-2.3.2.0-1.el7.noarch

ansible --version
ansible 2.3.2.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = Default w/o overrides
  python version = 2.7.5 (default, May  3 2017, 07:55:04) [GCC 4.8.5 20150623 (Red Hat 4.8.5-14)]

How reproducible:
Always

Steps to Reproduce:
1. Install opeishift with   openshift_use_crio: true
2. Installer fails due to above error.

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated
     Message:  Unable to restart service atomic-openshift-node: Job for atomic-openshift-node.service failed because the control process exited with error code. See "systemctl status atomic-openshift-node.service" and "journalctl -xe" for details.


Expected results:
Install should successfully install openshift.

Additional info:
Please attach logs from ansible-playbook with the -vvv flag
Comment 1 Seth Jennings 2017-09-06 15:18:18 UTC 
openshift-ansible PR:
https://github.com/openshift/openshift-ansible/pull/5313
Comment 2 Vikas Laad 2017-09-06 18:57:06 UTC 
tested from master branch of openshift-ansible, playbook runs witho
Comment 3 Vikas Laad 2017-09-06 19:00:55 UTC 
setting it back to modified, still testing it.
Comment 7 Vikas Laad 2017-10-09 16:27:02 UTC 
I am able to create env and node service starts after getting v3.7 crio image.
Note You need to log in before you can comment on or make changes to this bug.