-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all,
Final TC2 images have been uploaded to EC2 and are available at
ami-3392b55a : us-east-1 image for i386 ami-f794b39e : us-east-1 image for x86_64
additionally if your looking to the AMI's they have been added to files in the release tree http://dl.fedoraproject.org/pub/alt/stage/20-TC2/Images/i386/Fedora-Images-i... http://dl.fedoraproject.org/pub/alt/stage/20-TC2/Images/x86_64/Fedora-Images...
when we get to final and the images are uploaded to all regions they will all be listed and the file will be gpg signed in the final tree
Dennis
Dennis Gilmore dennis@ausil.us writes:
Hi all,
Final TC2 images have been uploaded to EC2 and are available at
ami-3392b55a : us-east-1 image for i386 ami-f794b39e : us-east-1 image for x86_64
I ran basic tests agains them and they're ok. The only issue I still see is wrong SELinux context for several files:
# restorecon -Rvn -e/dev -e/proc -e/sys -e/run -e/tmp/ / restorecon reset /var/cache/yum context system_u:object_r:file_t:s0->system_u:object_r:rpm_var_cache_t:s0 restorecon reset /var/log/boot.log context system_u:object_r:var_log_t:s0->system_u:object_r:plymouthd_var_log_t:s0 restorecon reset /boot/extlinux/ldlinux.sys context system_u:object_r:file_t:s0->system_u:object_r:boot_t:s0
On Thu, Nov 21, 2013 at 01:30:15PM +0100, Vitaly Kuznetsov wrote:
I ran basic tests agains them and they're ok. The only issue I still see is wrong SELinux context for several files:
# restorecon -Rvn -e/dev -e/proc -e/sys -e/run -e/tmp/ / restorecon reset /var/cache/yum context system_u:object_r:file_t:s0->system_u:object_r:rpm_var_cache_t:s0 restorecon reset /var/log/boot.log context system_u:object_r:var_log_t:s0->system_u:object_r:plymouthd_var_log_t:s0 restorecon reset /boot/extlinux/ldlinux.sys context system_u:object_r:file_t:s0->system_u:object_r:boot_t:s0
That's weird. We're running fixfiles at the end of the build process to clean up anything like that.
Matthew Miller mattdm@fedoraproject.org writes:
On Thu, Nov 21, 2013 at 01:30:15PM +0100, Vitaly Kuznetsov wrote:
I ran basic tests agains them and they're ok. The only issue I still see is wrong SELinux context for several files:
# restorecon -Rvn -e/dev -e/proc -e/sys -e/run -e/tmp/ / restorecon reset /var/cache/yum context system_u:object_r:file_t:s0->system_u:object_r:rpm_var_cache_t:s0 restorecon reset /var/log/boot.log context system_u:object_r:var_log_t:s0->system_u:object_r:plymouthd_var_log_t:s0 restorecon reset /boot/extlinux/ldlinux.sys context system_u:object_r:file_t:s0->system_u:object_r:boot_t:s0
That's weird. We're running fixfiles at the end of the build process to clean up anything like that.
I looked into kickstart, you do '/usr/sbin/fixfiles -R -a restore'. I tried running it manually on fresh instance:
# /usr/sbin/fixfiles -R -a restore 75k/sbin/restorecon set context /boot/extlinux/ldlinux.sys->system_u:object_r:boot_t:s0 failed:'Operation not permitted' 80k/sbin/restorecon set context /boot/extlinux/ldlinux.sys->system_u:object_r:boot_t:s0 failed:'Operation not permitted' 177k/sbin/restorecon set context /boot/extlinux/ldlinux.sys->system_u:object_r:boot_t:s0 failed:'Operation not permitted'
However /boot/extlinux/ldlinux.sys is the only file needs fixind after this:
# restorecon -Rvn -e/dev -e/proc -e/sys -e/run -e/tmp/ / restorecon reset /boot/extlinux/ldlinux.sys context system_u:object_r:file_t:s0->system_u:object_r:boot_t:s0
Anyway, https://bugzilla.redhat.com/show_bug.cgi?id=1033274 as suggested by dwalsh)
On Thu, Nov 21, 2013 at 09:13:19PM +0100, Vitaly Kuznetsov wrote:
177k/sbin/restorecon set context /boot/extlinux/ldlinux.sys->system_u:object_r:boot_t:s0 failed:'Operation not permitted'
However /boot/extlinux/ldlinux.sys is the only file needs fixind after this:
Oh, that makes sense, as that file is marked immutable (becuase the system won't boot if it moves). I don't think restorecon will move it, so I'll look at making it temporarily mutable and then put that back again.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/21/2013 03:13 PM, Vitaly Kuznetsov wrote:
Matthew Miller mattdm@fedoraproject.org writes:
On Thu, Nov 21, 2013 at 01:30:15PM +0100, Vitaly Kuznetsov wrote:
I ran basic tests agains them and they're ok. The only issue I still see is wrong SELinux context for several files:
# restorecon -Rvn -e/dev -e/proc -e/sys -e/run -e/tmp/ / restorecon reset /var/cache/yum context system_u:object_r:file_t:s0->system_u:object_r:rpm_var_cache_t:s0 restorecon reset /var/log/boot.log context system_u:object_r:var_log_t:s0->system_u:object_r:plymouthd_var_log_t:s0
restorecon reset /boot/extlinux/ldlinux.sys context system_u:object_r:file_t:s0->system_u:object_r:boot_t:s0
That's weird. We're running fixfiles at the end of the build process to clean up anything like that.
I looked into kickstart, you do '/usr/sbin/fixfiles -R -a restore'. I tried running it manually on fresh instance:
# /usr/sbin/fixfiles -R -a restore 75k/sbin/restorecon set context /boot/extlinux/ldlinux.sys->system_u:object_r:boot_t:s0 failed:'Operation not permitted' 80k/sbin/restorecon set context /boot/extlinux/ldlinux.sys->system_u:object_r:boot_t:s0 failed:'Operation not permitted' 177k/sbin/restorecon set context /boot/extlinux/ldlinux.sys->system_u:object_r:boot_t:s0 failed:'Operation not permitted'
However /boot/extlinux/ldlinux.sys is the only file needs fixind after this:
# restorecon -Rvn -e/dev -e/proc -e/sys -e/run -e/tmp/ / restorecon reset /boot/extlinux/ldlinux.sys context system_u:object_r:file_t:s0->system_u:object_r:boot_t:s0
Anyway, https://bugzilla.redhat.com/show_bug.cgi?id=1033274 as suggested by dwalsh)
Any change something is mounted on top of these files/directories when the fixfiles is run.
-
Daniel J Walsh -
Dennis Gilmore -
Matthew Miller -
Vitaly Kuznetsov