Bug 1599240

Summary:	Encounter ovs-vswitchd.service failed start cause to openshift install fail in ovs29
Product:	OpenShift Container Platform	Reporter:	Johnny Liu <jialiu>
Component:	Networking	Assignee:	Casey Callendrello <cdc>
Status:	CLOSED DUPLICATE	QA Contact:	Meng Bo <bmeng>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.10.0	CC:	anli, aos-bugs, bbennett, dma, dwalsh, ghuang, hongli, jialiu, jokerman, lvrabec, mgrepl, mmalik, mmccomas, plautrba, qe-baseos-security, ssekidde, weliang, weshi, wmeng
Target Milestone:	---	Keywords:	Regression
Target Release:	3.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1587899	Environment:
Last Closed:	2018-08-07 15:57:32 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:
Bug Depends On:	1587899
Bug Blocks:	1552827

Comment 2 Milos Malik 2018-07-09 09:46:58 UTC

Files like modules.alias.bin, modules.dep.bin and modules.softdep are mislabeled on your machine. Please run following command:

# restorecon -Rv /lib/modules

Comment 3 Scott Dodson 2018-07-09 12:33:13 UTC

If comment 2 fixes it, what's the history of this host? How was it installed? What OS version was it installed with? Is it a custom AMI or something else which may have been modified in some way? It looks like those files are created at kernel installation time, what selinux policy was installed at the time that the current kernel was installed?

Comment 13 Daniel Walsh 2018-07-12 14:15:38 UTC

unlabeled_t means the content was created on a NON SELinux system or was created while SELinux was disabled.  unlabeled_t is what the kernel reports when their is no XATTRS for an SELinux label.  This can happen when someone takes a USB Stick and inserts it into a machine and then mv's the content to a new directory.  Or it can happen when a new file system is created and the creator does not run restorecon on the mount point.

Comment 15 Wenkai Shi 2018-07-18 02:29:14 UTC

Hi Weibin, 
I've checked your installation logs.

As Comment 1 mentioned, it only effect 3.9 fresh install and 3.10 upgrade installation. 

For more details, you can only reproduce it while installation has openvswitch RPM install. For fresh 3.10 installation, there is no openvswitch RPM installed.

In one 3.10 cluster.
# rpm -q openvswitch
package openvswitch is not installed

Comment 16 Casey Callendrello 2018-08-07 15:57:32 UTC


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