On Thu, 2014-01-16 at 14:19 -0600, Dan Mossor wrote:
On 01/16/2014 10:33 AM, Chris Murphy wrote:
>
> On Jan 16, 2014, at 9:03 AM, Ankur Sinha <sanjay.ankur(a)gmail.com> wrote:
>
>>
>> It definitely isn't dnf mucking up. This is the second time I've fresh
>> installed today, and I haven't used dnf at all. I installed my apps,
>> updated, and I got a bunch of scriptlet failures:
>
> 1. I just did a rollback to a bit over 2 weeks ago and simply did yum update. Half
the proposed updates are from u-t.
>
> 2. During updating, there are two dozen items:
>
> warning: group root- does not exist - using root
>
> Otherwise the update completes without errors.
>
> 3. Reboot, download and install kernel 3.13 rc8 (which is what I was originally
having scriplet errors with) and it installs fine.
>
> So I can't reproduce the problem with yum. So I have no idea what's causing
this.
>
>
> Chris Murphy
>
Chris, the error was narrowed down to
selinux-policy-targeted-3.12.1-116. See
https://bugzilla.redhat.com/show_bug.cgi?id=1054350
selinux was denying rpm access, but wasn't logging it for some reason. I
saw no output in any of the logs while reproducing the error.
selinux-policy{-targeted}-3.12.1-117 fixes the problem at hand, and can
only be applied with selinux in permissive mode. while in enforcing, the
update fails.
Dan (Walsh), Miroslav - perhaps in light of this saga it might be wise
to set the autopush threshold for selinux-policy updates higher than 3?
As most people run with selinux on, selinux-policy updates tend to get a
lot of karma, and we might stand a better chance of avoiding bad updates
like this going to stable if we set the karma threshold higher so it
doesn't get hit quite so fast, and problems like this have time to come
to light...
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net