Bug 1393994 - Atomic Host will not upgrade due to an Selinux issue
Summary: Atomic Host will not upgrade due to an Selinux issue
Keywords:
Status: CLOSED DUPLICATE of bug 1377932
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: atomic
Version: 7.2
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-10 19:02 UTC by Ryan Cook
Modified: 2016-11-10 19:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-10 19:13:56 UTC
Target Upstream Version:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.