Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 574748 - anaconda/python-meh is filing F-13 bugs with version=rawhide
Summary: anaconda/python-meh is filing F-13 bugs with version=rawhide
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F13Target
TreeView+ depends on / blocked
 
Reported: 2010-03-18 13:06 UTC by James Laska
Modified: 2013-09-02 06:45 UTC (History)
4 users (show)

Fixed In Version: python-meh-0.7.1-1.fc13
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-24 16:20:27 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description James Laska 2010-03-18 13:06:27 UTC 
Description of problem:

Using the save-to-bugzilla feature of anaconda for recording tracebacks when testing Fedora 13 images is filing bugs with version=rawhide.  Apologies, I'm not clear whether this should be filed against anaconda or python-meh.

Version-Release number of selected component (if applicable):
 * anaconda 13.35
 * python-meh-0.7-1.fc13

Steps to Reproduce:

* https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_bugzilla
  
Actual results:

See bug#574743, it was filed against rawhide

Expected results:

Perhaps this should be filed against Fedora 13?

Additional info:

* I'm adding this to F13Beta for discussion whether this bug affects the Alpha criteria "The installer must be able to report failures to Bugzilla, with appropriate information included "
Comment 1 James Laska 2010-03-19 16:24:39 UTC 
Moved to F13Target after discussion in the F13 Beta blocker review meeting.  This would be nice to have for Beta, but we would not hold beta for this bug.
Comment 2 Chris Lumens 2010-03-22 14:54:53 UTC 
Can you point me to a tree that was exhibiting this behavior?
Comment 3 James Laska 2010-03-22 15:14:08 UTC 
(In reply to comment #2)
> Can you point me to a tree that was exhibiting this behavior?    

http://serverbeach1.fedoraproject.org/pub/alt/stage/13-Beta.TC0/Fedora/
Comment 4 Chris Lumens 2010-03-22 16:05:38 UTC 
Okay here's what I think is going on.  In that tree's .buildstamp, we have:

201003152222.i386
Fedora
13-Beta
https://bugzilla.redhat.com

That means product.productVersion is "13-Beta".  Later, we go grab a list of all the valid product versions for Fedora according to bugzilla, 13-Beta is nowhere to be found.  So we fall back to the default of rawhide.

In other words, this should not affect the final release of F13.  If we care enough for the test releases, I can make meh smart enough to recognize this condition and try trimming off the "-whatever" from version numbers.  Do we care enough?

For the future, I do not know how report plans on getting the version number but it may be worth bringing this issue up with them too.  Otherwise we may just see it again on F14.
Comment 5 James Laska 2010-03-22 18:29:56 UTC 
Doesn't seem like a huge problem to release with, but I don't think just filing bugs against rawhide is the right answer either.  Adding jkeating to the list, but I'd propose that .buildstamp:

  201003152222.i386
  Fedora
  13
  https://bugzilla.redhat.com

The datestamp and contents of .treeinfo sha256sum's can be used to determine what particular build this represents.  Jesse, any objections or concerns?
Comment 6 Jesse Keating 2010-03-22 22:08:50 UTC 
To accomplish that, we'd have to start calling the version "13" and not "13-Beta" which would screw up path names and iso names.  So we either have to "hack" it in pungi or hack it in python-meh.
Comment 7 Chris Lumens 2010-03-23 14:58:10 UTC 
I would much rather work around this in meh than do anything crazy in pungi or .buildstamp, as those are going to affect a whole lot more components.

Does updates=http://clumens.fedorapeople.org/574748.img fix this issue?
Comment 8 James Laska 2010-03-23 16:43:58 UTC 
(In reply to comment #7)
> Does updates=http://clumens.fedorapeople.org/574748.img fix this issue?    

Seems to do the trick (see bug#576264 for example).
Comment 9 Fedora Update System 2010-03-24 15:00:23 UTC 
python-meh-0.7.1-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/python-meh-0.7.1-1.fc13
Comment 10 Fedora Update System 2010-03-25 22:30:54 UTC 
python-meh-0.7.1-1.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update python-meh'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/python-meh-0.7.1-1.fc13
Comment 11 Fedora Update System 2010-06-24 16:20:16 UTC 
python-meh-0.7.1-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.