F12 update issues

Matthias Clasen mclasen at redhat.com
Tue Mar 2 16:33:59 UTC 2010

On Tue, 2010-03-02 at 11:04 -0500, James Laska wrote:
> On Tue, 2010-03-02 at 10:13 -0500, Matthias Clasen wrote:
> > Hey,
> > 
> > I just set up a fresh F12 vm, then I logged in and tried to update the
> > system. I was greeted with an 'internal system error' dialog. After
> > seeking advice I learned that I need to manually update yum and
> > PackageKit before doing the wholesale system update. 
> > 
> > I think this is a pretty dire issue, essentially a dead-on-arrival
> > system. One more reason why we need to batch updates and test them as a
> > whole.
> > What mechanisms to we have in place to prevent issues like this from
> > repeating in F13 ? 
> Without understanding the root cause of the failure, it's hard to say.
> If you can provide a bz, we'll be happy to include this into the mix
> with current AutoQA initiatives.

When I asked hughsie, he pointed me at


> > Does autoqa run any 'update a fresh install to all
> > current updates' kind of test ? 
> No, we do not have such at test at this time.  What test(s) would you
> like to see covered by doing a GOLD install + upgrade?  Is this for
> depsclosure or conflicts detection?  Is there any existing automated
> functional verification you'd like to have AutoQA provide regular
> results for?  Again, I'll probably have a more appropriate
> recommendation once we figure out what the core problem is.  

The problem I was facing is very easy to reproduce, and very hard to
deal with for regular users. 

1) Install from the live cd
2) Log in
3) Run System > Administration > Software Updates
4) Get an unintelligable error dialog

So, I think having an automated test that basically does these steps and
verifies that the current set of updates can be successfully installed
on a GOLD install would be very useful.

More information about the test mailing list