On Tue, Dec 03, 2013 at 04:42:44PM +0100, Vitaly Kuznetsov wrote: > The only issue compared to TC3 is one more file with wrong selinux > context (/var/log/cron). > So, for TC4: > # restorecon -R -v -n -e /proc -e /sys -e /dev -e/run -e/tmp / > restorecon reset /var/log/cron context > system_u:object_r:var_log_t:s0->system_u:object_r:cron_log_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
These files don't exist initially -- I expect that just creating them before the fixfiles is run in the kickstart should do it. > restorecon reset /var/cache/yum context > system_u:object_r:file_t:s0->system_u:object_r:rpm_var_cache_t:s0 This _does_ exist, though, so it's more of a puzzle. Any guesses? > restorecon reset /boot/extlinux/ldlinux.sys context > system_u:object_r:file_t:s0->system_u:object_r:boot_t:s0 And this is because it's immutable. > not sure if it deserves BZ and against what if it does. Last time I > created https://bugzilla.redhat.com/show_bug.cgi?id=1033274 against > anaconda but it seems misplaced. Since we're building with appliance-creator, anaconda isn't involved. That will change in the future.... In the meantime, we have to hack around it with kickstart kludges. Can you test http://mattdm.fedorapeople.org/tmp/Fedora20-sda.qcow2 to see if it's any better? -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mat...@fedoraproject.org> -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
