Bug 1651052

Summary: Openshift 3.11 installation on Azure missing samba-client package needed for Azure File
Product: OpenShift Container Platform Reporter: Mike Calizo <mcalizo>
Component: InstallerAssignee: Scott Dodson <sdodson>
Installer sub component: openshift-ansible QA Contact: Johnny Liu <jialiu>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: unspecified    
Version: 3.11.0   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-12-06 13:23:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mike Calizo 2018-11-19 03:38:38 UTC
Description of problem:
Openshift 3.11 installation on Azure missing samba-common, and cifs-utils packages needed for Azure File

Version-Release number of selected component (if applicable):
3.11

How reproducible:
All the time

Steps to Reproduce:
1. Install Openshift on Azure and use Azure File (Application miscellaneous Persistent Storage needs.)
2. It will fail due to missing Samba packages: samba-common, and cifs-utils


Actual results:
Failure to use azure file.

Expected results:
Usable Azure file mounted to a pods

Additional info:

Workaround Found:
Using the link below, azure file can be mounted to a pod.
https://docs.openshift.com/container-platform/3.4/install_config/persistent_storage/persistent_storage_azure_file.html

Work Around Steps:
1. Install samba-client, samba-common, and cifs-utils on all nodes:
$ sudo yum install samba-client samba-common cifs-utils
2. Enable SELinux booleans on all nodes:
$ /usr/sbin/setsebool -P virt_use_samba on
$ /usr/sbin/setsebool -P virt_sandbox_use_samba on

 



Description of problem:

Version-Release number of the following components:
rpm -q openshift-ansible
rpm -q ansible
ansible --version

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated

Expected results:

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 1 Scott Dodson 2018-12-06 13:23:46 UTC

*** This bug has been marked as a duplicate of bug 1624311 ***