Bug 1393994

Summary:	Atomic Host will not upgrade due to an Selinux issue
Product:	Red Hat Enterprise Linux 7	Reporter:	Ryan Cook <rcook>
Component:	atomic	Assignee:	Lokesh Mandvekar <lsm5>
Status:	CLOSED DUPLICATE	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	walters
Target Milestone:	rc	Keywords:	Extras
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-10 19:13:56 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:

Description Ryan Cook 2016-11-10 19:02:11 UTC

Description of problem: Issues when trying to upgrade Atomic on AWS. The AMI is super old but when currently attempting to upgrade the error "error: fsetxattr: Invalid argument" occurs.


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

How reproducible:
-bash-4.2# atomic host upgrade
Updating from: rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard

Receiving objects: 10% (183/1752) 2.1 MB/s 19.3 MB
error: fsetxattr: Invalid argument


Steps to Reproduce:
1. deploy ami-8e5a67e4
2. Register system 
3. run atomic host upgrade

Actual results:
-bash-4.2# atomic host upgrade
Updating from: rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard

Receiving objects: 10% (183/1752) 2.1 MB/s 19.3 MB
error: fsetxattr: Invalid argument

Expected results:
1 metadata, 1545 content objects fetched; 245044 KiB transferred in 224 seconds
Copying /etc changes: 31 modified, 4 removed, 55 added
Transaction complete; bootconfig swap: yes deployment count change: 1

Additional info:
Work around is setenforce 0

Comment 1 Colin Walters 2016-11-10 19:13:56 UTC

Yep, basically we suck.

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