Description of problem: atomic-openshift and atomic-openshift-client will be installed as the prerequrement on nfs server. In fact they aren't the essential packages for nfs server. By the way, due to these packages will be installed, if we install ose3.1 using a-o-i 3.2 on RHEL+docker 1.9, it will hit the "docker conflicts with atomic-openshift-3.1.1.6" messages. see the Additional info: Version-Release number of selected component (if applicable): atomic-openshift-utils-3.0.72 How reproducible: always Steps to Reproduce: 1. Specify a standalone host as nfs server in inventory file 2. Install openshift 3. rpm -qa|grep atomic-openshift Actual results: #rpm -qa|grep atomic-openshift atomic-openshift-clients-3.2.0.11-1.git.0.6696e29.el7.x86_64 atomic-openshift-3.2.0.11-1.git.0.6696e29.el7.x86_64 Expected results: Additional info: TASK: [openshift_common | Install the base package for versioning] ************ failed: [10.14.6.130] => {"changed": true, "rc": 1, "results": ["Loaded plugins: product-id, search-disabled-repos, subscription-manager\nThis system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.\nResolving Dependencies\n--> Running transaction check\n---> Package atomic-openshift.x86_64 0:3.1.1.6-5.git.35.0742c54.el7aos will be installed\n--> Processing Dependency: atomic-openshift-clients = 3.1.1.6-5.git.35.0742c54.el7aos for package: atomic-openshift-3.1.1.6-5.git.35.0742c54.el7aos.x86_64\n--> Running transaction check\n---> Package atomic-openshift-clients.x86_64 0:3.1.1.6-5.git.35.0742c54.el7aos will be installed\n--> Processing Conflict: docker-1.9.1-25.el7.x86_64 conflicts atomic-openshift < 3.2\n--> Finished Dependency Resolution\n You could try using --skip-broken to work around the problem\n You could try running: rpm -Va --nofiles --nodigest\n"]} msg: Error: docker conflicts with atomic-openshift-3.1.1.6-5.git.35.0742c54.el7aos.x86_64
Verify this bug with openshift-ansible-3.0.75-1.git.0.83b3b91.el7.noarch.rpm After installation, log into the nfs server host, no openshift related package installed.
Found the PR is breaking other things, here is nfs setting options in my inventory: openshift_hosted_registry_storage_kind=nfs openshift_hosted_registry_storage_nfs_options='*(rw,root_squash,sync,no_wdelay)' openshift_hosted_registry_storage_nfs_directory=/var/lib/exports openshift_hosted_registry_storage_volume_name=regpv openshift_hosted_registry_storage_access_modes=['ReadWriteMany'] openshift_hosted_registry_storage_volume_size=17G After installation is done, go to nfs server, checking: # cat /etc/exports /exports/registry *(rw,root_squash) Found nfs server is exporting wrong dir, not the specified one in pv definition, that will make docker-registry deploy failure. $ oc get po NAME READY STATUS RESTARTS AGE docker-registry-1-deploy 0/1 DeadlineExceeded 0 7h docker-registry-2-79t61 0/1 ContainerCreating 0 7h docker-registry-2-deploy 1/1 Running 0 7h $ oc describe po docker-registry-2-79t61 <--snip--> Events: FirstSeen LastSeen Count From SubobjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 7h 7h 1 {default-scheduler } Normal Scheduled Successfully assigned docker-registry-2-79t61 to openshift-xxx 7h 7h 20 {kubelet openshift-xxx} Warning FailedMount Unable to mount volumes for pod "docker-registry-2-79t61_default(0b15a785-fd51-11e5-97d3-fa163ee13a09)": Mount failed: exit status 32 Mounting arguments: openshift-xxx:/var/lib/exports/regpv /var/lib/origin/openshift.local.volumes/pods/0b15a785-fd51-11e5-97d3-fa163ee13a09/volumes/kubernetes.io~nfs/regpv-volume nfs [] Output: Job for rpc-statd.service failed because the control process exited with error code. See "systemctl status rpc-statd.service" and "journalctl -xe" for details. mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified 7h 7h 20 {kubelet openshift-xxx} Warning FailedSync Error syncing pod, skipping: Mount failed: exit status 32 Mounting arguments: openshift-xxx:/var/lib/exports/regpv /var/lib/origin/openshift.local.volumes/pods/0b15a785-fd51-11e5-97d3-fa163ee13a09/volumes/kubernetes.io~nfs/regpv-volume nfs [] Output: Job for rpc-statd.service failed because the control process exited with error code. See "systemctl status rpc-statd.service" and "journalctl -xe" for details. mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified This is breaking installation, so raise its severity.
Proposed fix: https://github.com/openshift/openshift-ansible/pull/1733
Verified this bug with that latest openshift-ansible master branch, and PASS. No openshift rpm packages are installed on nfs server, and nfs pv storage created on this NFS server is running well.
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. https://access.redhat.com/errata/RHBA-2016:1065