cannot install 3.10

[dusansusic]

Unable to install OpenShift 3.10

• Your ansible version per ansible --version
  2.4.3.0

If you're operating from a git clone:

• The output of git describe
  susie@xps:~/tmp/openshift-ansible$ git describe
  openshift-ansible-3.10.47-1-14-g1aae9201c

Steps To Reproduce

1. [step 1]
   git clone https://github.com/openshift/openshift-ansible.git
   cd openshift-ansible/
   run ansible installer
   git checkout release-3.10

2. [step 2]
   add inventory file

[OSEv3:children]
masters
nodes
etcd

[OSEv3:vars]
ansible_ssh_user=rh
ansible_become=yes
ansible_ssh_private_key_file=/home/rh/.ssh/id_rsa
deployment_type=origin
containerized=true
openshift_master_default_subdomain=openshift.example.com
openshift_hosted_metrics_deploy=false
openshift_disable_check=docker_storage,memory_availability,disk_availability,docker_image_availability
openshift_master_overwrite_named_certificates=true
openshift_master_identity_providers=[{'name': 'htpasswd_auth', 'login': 'true', 'challenge': 'true', 'kind': 'HTPasswdPasswordIdentityProvider'}]
openshift_master_htpasswd_users={'${openshift_web_username}': '${openshift_web_password}'}
openshift_hosted_router_selector='region=infra'
openshift_registry_selector='region=infra'
enable_excluders=false
osm_cluster_network_cidr=10.10.0.0/14
openshift_logging_install_logging=false
openshift_web_console_install=true
openshift_web_console_prefix=docker.io/openshift/origin-
openshift_release=v3.10
openshift_image_tag=v3.10.0
openshift_pkg_version=-3.10.0
openshift_master_cluster_hostname=*masterPublicDNS*
openshift_public_hostname=*masterPublicDNS*

[masters]
${masterPublicIP} openshift_schedulable=True

[etcd]
${masterPublicIP}

[nodes]
${masterPublicIP} openshift_hostname=${masterFQDN} openshift_node_group_name='node-config-master-infra'
${node0PublicIP} openshift_hostname=${node0FQDN} openshift_node_group_name='node-config-infra'
${node1PublicIP} openshift_hostname=${node1FQDN} openshift_node_group_name='node-config-infra'

environment variables above are replaced correctly.

Expected Results

Installed OpenShift 3.10

ERROR LOG

TASK [openshift_storage_glusterfs : load kernel modules] ***********************
Thursday 13 September 2018  11:43:47 +0000 (0:00:00.058)       0:02:29.478 **** 
fatal: [13.57.15.225]: FAILED! => {"changed": false, "msg": "Unable to start service systemd-modules-load.service: Job for systemd-modules-load.service failed because the control process exited with error code. See \"systemctl status systemd-modules-load.service\" and \"journalctl -xe\" for details.\n"}
fatal: [54.193.88.85]: FAILED! => {"changed": false, "msg": "Unable to start service systemd-modules-load.service: Job for systemd-modules-load.service failed because the control process exited with error code. See \"systemctl status systemd-modules-load.service\" and \"journalctl -xe\" for details.\n"}
fatal: [54.219.181.201]: FAILED! => {"changed": false, "msg": "Unable to start service systemd-modules-load.service: Job for systemd-modules-load.service failed because the control process exited with error code. See \"systemctl status systemd-modules-load.service\" and \"journalctl -xe\" for details.\n"}

[Episodio1]

Although it won't fix your problem, at least try to install as official doc says (preinstalling some packages, for example Ansible 2.6) from https://docs.okd.io/latest/install/host_preparation.html
If that is too much information, this guy (from RedHat it seems) made a simple executable script that does all installation: https://github.com/gshipley/installcentos
Once you install this way, then post your problem ;)

[dusansusic]

@Episodio1 i am running prerequirements.yaml playbook before deploy_cluster.yaml just as it is in official documentation.

I am using RedHat 7.2, not centos and ansbible 2.4.3.0 (version that is min required version by official docs).

Thanks anyways.

[nagonzalez]

Looks like it's failing here:

openshift-ansible/roles/openshift_storage_glusterfs/tasks/kernel_modules.yml

Line 14 in 0b1a5b7

- name: load kernel modules

What's the output of:

systemctl status systemd-modules-load.service
journalctl -xe

[dusansusic]

● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2018-09-24 11:45:52 UTC; 23min ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 15340 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
 Main PID: 15340 (code=exited, status=1/FAILURE)

Sep 24 11:45:52 ip-192-168-88-25.susie.internal systemd[1]: Starting Load Kernel Modules...
Sep 24 11:45:52 ip-192-168-88-25.susie.internal systemd-modules-load[15340]: Inserted module 'dm_thin_pool'
Sep 24 11:45:52 ip-192-168-88-25.susie.internal systemd-modules-load[15340]: Inserted module 'target_core_user'
Sep 24 11:45:52 ip-192-168-88-25.susie.internal systemd-modules-load[15340]: Failed to insert 'xen_netfront': No such device
Sep 24 11:45:52 ip-192-168-88-25.susie.internal systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
Sep 24 11:45:52 ip-192-168-88-25.susie.internal systemd[1]: Failed to start Load Kernel Modules.
Sep 24 11:45:52 ip-192-168-88-25.susie.internal systemd[1]: Unit systemd-modules-load.service entered failed state.
Sep 24 11:45:52 ip-192-168-88-25.susie.internal systemd[1]: systemd-modules-load.service failed.

seems that:

Sep 24 11:45:52 ip-192-168-88-25.susie.internal systemd-modules-load[15340]: Failed to insert 'xen_netfront': No such device is casuing this. How to solve it?

[nagonzalez]

Might be a RHEL 7.2 issue.

Can you test on RHEL 7.4 or 7.5 per https://docs.okd.io/3.10/install/prerequisites.html

[dusansusic]

@nagonzalez hello, thanks for answer, this error is shown when using RHEL 7.4, AMI ami-1607ba6e on us-west-2 provided by RedHat.

[dwmkerr]

This worked for me when I moved to RHEL 7.5:

dwmkerr/terraform-aws-openshift#65

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.