Bug 741647

Can you still reproduce this?

Yes, reproducible with F16 RC5 Live Desktop.

Not reproducible with RC5 DVD.

This problem should be already fixed.

I have been seeing this message with anaconda running in an F18 VM on an F17 host:

--- Running report_Bugzilla ---
Logging into Bugzilla at https://bugzilla.redhat.com
Checking for duplicates
Creating a new bug
fatal: RPC failed at server.  Either the product 'anaconda release bluesky' does not exist or you don't have access to it.
(exited with 1)

The F18 VM is updated with:

anaconda-18.8-1.fc18.x86_64
libreport-2.0.13-1.fc18.x86_64
libreport-filesystem-2.0.13-1.fc18.x86_64
libreport-gtk-2.0.13-1.fc18.x86_64
libreport-newt-2.0.13-1.fc18.x86_64
libreport-plugin-bugzilla-2.0.13-1.fc18.x86_64
libreport-plugin-kerneloops-2.0.13-1.fc18.x86_64
libreport-plugin-logger-2.0.13-1.fc18.x86_64
libreport-plugin-ureport-2.0.13-1.fc18.x86_64
libreport-python-2.0.13-1.fc18.x86_64
libreport-web-2.0.13-1.fc18.x86_64
python-meh-0.16-1.fc18.noarch

(In reply to comment #5)
> I have been seeing this message with anaconda running in an F18 VM on an F17
> host:
> 
> --- Running report_Bugzilla ---
> Logging into Bugzilla at https://bugzilla.redhat.com
> Checking for duplicates
> Creating a new bug
> fatal: RPC failed at server.  Either the product 'anaconda release bluesky'
> does not exist or you don't have access to it.
> (exited with 1)
> 
> The F18 VM is updated with:
> 
> anaconda-18.8-1.fc18.x86_64
> libreport-2.0.13-1.fc18.x86_64
> libreport-filesystem-2.0.13-1.fc18.x86_64
> libreport-gtk-2.0.13-1.fc18.x86_64
> libreport-newt-2.0.13-1.fc18.x86_64
> libreport-plugin-bugzilla-2.0.13-1.fc18.x86_64
> libreport-plugin-kerneloops-2.0.13-1.fc18.x86_64
> libreport-plugin-logger-2.0.13-1.fc18.x86_64
> libreport-plugin-ureport-2.0.13-1.fc18.x86_64
> libreport-python-2.0.13-1.fc18.x86_64
> libreport-web-2.0.13-1.fc18.x86_64
> python-meh-0.16-1.fc18.noarch

The "anaconda release bluesky" indeed doesn't exist in bugzilla, so either anaconda or python-meh has to pass the proper name to libreport.

(In reply to comment #6) 
> The "anaconda release bluesky" indeed doesn't exist in bugzilla, so either
> anaconda or python-meh has to pass the proper name to libreport.
"anaconda release bluesky" is a string used when no .buildstamp file is available, which happens out of the installation media and in some pre-release builds.

Please change the product name to some valid string ("Fedora Rawhide" probably) before filing a new bug in such cases.

(In reply to comment #7)
> (In reply to comment #6) 
> > The "anaconda release bluesky" indeed doesn't exist in bugzilla, so either
> > anaconda or python-meh has to pass the proper name to libreport.
> "anaconda release bluesky" is a string used when no .buildstamp file is
> available, which happens out of the installation media and in some
> pre-release builds.
> 
> Please change the product name to some valid string ("Fedora Rawhide"
> probably) before filing a new bug in such cases.

Thanks. I was running anaconda-18.8-1.fc18.x86_64 from the command line in an installed system.[1]

Couldn't anaconda provide a message saying "no .buildstamp file is available", so searching BZ and the internet for "anaconda release bluesky" is not needed?

And offer suggestions, such as "Please change the product name to some valid string ("Fedora Rawhide" probably)"?

[1] Running F18 from hda:
$ qemu-kvm -m 1024 -hda f18-test-1.img -hdb f18-test-2.img -cdrom ~/xfr/fedora/F18/F18-Alpha/RC3/Fedora-18-Alpha-x86_64-DVD.iso -vga qxl
Cross reference: Bug 858862

I have reproduced this problem using firstboot exceptions with F18 installed in a VM.

When anaconda is installed, the file libreport*/os_release contains the string:
"anaconda release bluesky".

When anaconda is removed, the file libreport*/os_release contains the string:
"Fedora release 18 (Spherical Cow)".

By changing the string "anaconda release bluesky" to "Fedora release 18 (Spherical Cow)" in os_release, I was able to use abrt to report:
Bug 862978 - Error: unsupported locale setting.

When anaconda is installed, the file "version", containing "bluesky", is also created.

# egrep -r 'bluesky|release|firstboot' libreport*/{os_release,version,package} | sort
libreport-2012-10-04-13:44:37-495/os_release:Fedora release 18 (Spherical Cow)
libreport-2012-10-04-13:44:37-495/package:firstboot-18.4-1.fc18.x86_64
libreport-2012-10-04-13:48:58-513/os_release:anaconda release bluesky
libreport-2012-10-04-13:48:58-513/package:firstboot-18.4-1.fc18.x86_64
libreport-2012-10-04-13:48:58-513/version:bluesky

abrt-2.0.13-1.fc18.x86_64
anaconda-18.8-2.fc18.x86_64
firstboot-18.4-1.fc18.x86_64
libreport-2.0.14-1.fc18.x86_64
python-meh-0.16-1.fc18.noarch

Created attachment 621906 [details]
tar file containing two libreport* directories

For completeness, here are two libreport* directories, one created when anaconda was installed, and one created when anaconda was not installed.

With anaconda:    libreport-2012-10-04-13:48:58-513/
Without anaconda: libreport-2012-10-04-13:44:37-495/

Created attachment 621916 [details]
/var/log/messages

This file shows the context in which the libreport* files were created.

[snippet from /var/log/messages]
...
Oct  4 13:44:37 localhost abrtd: Directory 'libreport-2012-10-04-13:44:37-495' creation detected
Oct  4 13:44:37 localhost firstboot[495]: Unhandled exception in firstboot occured.
...
Oct  4 13:48:58 localhost abrtd: Directory 'libreport-2012-10-04-13:48:58-513' creation detected
Oct  4 13:48:58 localhost firstboot[513]: Unhandled exception in firstboot occured.
...

Without anaconda: libreport-2012-10-04-13:44:37-495/
With anaconda:    libreport-2012-10-04-13:48:58-513/
(I listed them in time-reversed order in Comment 10. Sorry about that.)

Notes: There is a reboot in between.
I worked around some timezone-related bugs before running these two tests, so there are time jumps earlier in the file.
firewalld was also crashing during booting.

Created attachment 621921 [details]
screenshot of the abrt gui with two exception report windows

This screenshot shows that the os_release for an earlier firstboot exception was "anaconda release bluesky", while the os_release for the firewalld exception was "Fedora release 18 (Spherical Cow)". The timestamp shows that they occurred 11 seconds apart.

The string "bluesky" appears in anaconda here:
http://git.fedorahosted.org/cgit/anaconda.git/plain/pyanaconda/product.py

# First, load in the defaults.  In order of precedence:  contents of
# .buildstamp, environment, stupid last ditch hardcoded defaults.
config = ConfigParser.ConfigParser()
config.add_section("Main")
config.set("Main", "Arch", os.environ.get("ANACONDA_PRODUCTARCH", os.uname()[4]))
config.set("Main", "BugURL", os.environ.get("ANACONDA_BUGURL", "your distribution provided bug reporting tool"))
config.set("Main", "IsFinal", os.environ.get("ANACONDA_ISFINAL", "false"))
config.set("Main", "Product", os.environ.get("ANACONDA_PRODUCTNAME", "anaconda"))
config.set("Main", "UUID", "")
config.set("Main", "Version", os.environ.get("ANACONDA_PRODUCTVERSION", "bluesky"))

(In reply to comment #13)
> The string "bluesky" appears in anaconda here:
> http://git.fedorahosted.org/cgit/anaconda.git/plain/pyanaconda/product.py
> 
> # First, load in the defaults.  In order of precedence:  contents of
> # .buildstamp, environment, stupid last ditch hardcoded defaults.
> config = ConfigParser.ConfigParser()
> config.add_section("Main")
> config.set("Main", "Arch", os.environ.get("ANACONDA_PRODUCTARCH",
> os.uname()[4]))
> config.set("Main", "BugURL", os.environ.get("ANACONDA_BUGURL", "your
> distribution provided bug reporting tool"))
> config.set("Main", "IsFinal", os.environ.get("ANACONDA_ISFINAL", "false"))
> config.set("Main", "Product", os.environ.get("ANACONDA_PRODUCTNAME",
> "anaconda"))
> config.set("Main", "UUID", "")
> config.set("Main", "Version", os.environ.get("ANACONDA_PRODUCTVERSION",
> "bluesky"))
Yeah, that's what I was pointing out in comment #7

Why libreport looks for the version to a different places when anaconda is installed and when it is not installed I have no idea. Suggestions, Jiri?

@steve Tyler

I have the same problem when trying to start system-config-kickstart in
 Fedora 17 (Beefy Miracle)
I seem unable to  find that string "anaconda release bluesky" not in /var/log:

[root@cal-26 ~]# grep -i anaconda /var/log/*
grep: /var/log/anaconda: Is a directory
grep: /var/log/audit: Is a directory
grep: /var/log/ceph: Is a directory
grep: /var/log/chrony: Is a directory
grep: /var/log/ConsoleKit: Is a directory
grep: /var/log/cups: Is a directory
grep: /var/log/gdm: Is a directory
grep: /var/log/glusterfs: Is a directory
grep: /var/log/jboss-as: Is a directory
grep: /var/log/jetty: Is a directory
grep: /var/log/libvirt: Is a directory
grep: /var/log/mail: Is a directory
/var/log/messages:Oct 11 11:31:49 cal-26 yum[9992]: Erased: anaconda-17.29-1.fc17.x86_64
/var/log/messages:Oct 11 11:32:09 cal-26 yum[10004]: Installed: anaconda-17.29-1.fc17.x86_64
grep: /var/log/nginx: Is a directory
grep: /var/log/ntpstats: Is a directory
grep: /var/log/ovirt-engine: Is a directory
grep: /var/log/ppp: Is a directory
grep: /var/log/prelink: Is a directory
grep: /var/log/sa: Is a directory
grep: /var/log/speech-dispatcher: Is a directory
grep: /var/log/spice-vdagentd: Is a directory
grep: /var/log/sssd: Is a directory
/var/log/yum.log:May 11 17:08:57 Updated: anaconda-17.26-1.fc17.x86_64
/var/log/yum.log:May 22 08:38:35 Updated: anaconda-17.28-1.fc17.x86_64
/var/log/yum.log:May 29 08:45:33 Updated: anaconda-17.29-1.fc17.x86_64
/var/log/yum.log:Oct 11 11:31:49 Erased: anaconda-17.29-1.fc17.x86_64
/var/log/yum.log:Oct 11 11:32:09 Installed: anaconda-17.29-1.fc17.x86_64
[root@cal-26 ~]# 

and no anywhere in a libreport file
[root@cal-26 ~]# updatedb
[root@cal-26 ~]# locate libreport | xargs -n 1 grep -i bluesky
grep: /etc/libreport: Is a directory
grep: /etc/libreport/events: Is a directory
grep: /etc/libreport/events.d: Is a directory
grep: /etc/libreport/plugins: Is a directory
grep: /usr/share/doc/libreport-2.0.14: Is a directory
[root@cal-26 ~]# locate libreport | xargs -n 1 grep -i anaconda
grep: /etc/libreport: Is a directory
grep: /etc/libreport/events: Is a directory
grep: /etc/libreport/events.d: Is a directory
grep: /etc/libreport/plugins: Is a directory
                --only=anaconda --only=bootloader --only=devicemapper \
grep: /usr/share/doc/libreport-2.0.14: Is a directory
[root@cal-26 ~]# 
[root@cal-26 ~]# locate libreport | xargs -n 1 grep -i os_release
grep: /etc/libreport: Is a directory
grep: /etc/libreport/events: Is a directory
grep: /etc/libreport/events.d: Is a directory
grep: /etc/libreport/plugins: Is a directory
    <requires-items>component,duphash,os_release</requires-items>
    <requires-items>analyzer,reason,executable,pkg_epoch,pkg_name,pkg_version,pkg_release,pkg_arch,os_release,architecture,core_backtrace</requires-items>
Binary file /usr/lib64/libreport-web.so matches
Binary file /usr/lib64/libreport-web.so.0 matches
Binary file /usr/lib64/libreport-web.so.0.0.1 matches
Binary file /usr/lib64/libreport.so.0 matches
Binary file /usr/lib64/libreport.so.0.0.1 matches
grep: /usr/share/doc/libreport-2.0.14: Is a directory


still  I see in the AttributeError tab: box os_release  marked  and "anaconda release bluesky" next to it.

If only I could uncheck that box... :-) It looks

Suggestions to get system-config-kickstart working on fedora 17 or to get at least the bug reported, are welcome.

(In reply to comment #15)
... 
> I have the same problem when trying to start system-config-kickstart in
>  Fedora 17 (Beefy Miracle)
> I seem unable to  find that string "anaconda release bluesky" not in
...

Thanks for your report. What is the output from this?

# grep -rl bluesky /var/spool/abrt
$ grep -rl bluesky $HOME/.cache/abrt

I found the string "anaconda release bluesky" in the file os_release:
# locate os_release

If you change "anaconda release bluesky" to "Fedora 17 (Beefy Miracle)" in os_release, you might be able to report the bug with abrt-gui.

To work around the problem in the future, this might work:

# yum erase anaconda
Delete any previous abrt problem reports.
Run system-config-kickstart to reproduce the crash.

For the record, what is the output from this?

$ rpm -qa 'abrt*' 'libreport*' | sort

(In reply to comment #16)
...
> To work around the problem in the future, this might work:
> 
> # yum erase anaconda
> Delete any previous abrt problem reports.
> Run system-config-kickstart to reproduce the crash.

I don't know what I'm talking about ... :-)
system-config-kickstart *requires* anaconda.
So removing anaconda might work if it is not required ...

(In reply to comment #16)
...
> If you change "anaconda release bluesky" to "Fedora 17 (Beefy Miracle)" in
> os_release, you might be able to report the bug with abrt-gui.
...

From Comment 9 and a retest, the string should be changed to:

"Fedora release 17 (Beefy Miracle)"
        ^^^^^^^
Sorry about the confusion ...

@Steve Tyler 
Thanks for looking into this, these are the results.

reply to comment 16:
[root@cal-26 ~]# grep -rl bluesky /var/spool/abrt
[root@cal-26 ~]# 
[jringoot@cal-26 ~]$ grep -rl bluesky $HOME/.cache/abrt
[jringoot@cal-26 ~]$ 

(next one should also answer comment 19) 
[root@cal-26 ~]# locate os_release | xargs -n 1 cat
Fedora release 17 (Beefy Miracle)Fedora release 17 (Beefy Miracle)Fedora release 17 (Beefy Miracle)Fedora release 17 (Beefy Miracle)Fedora release 17 (Beefy Miracle)[root@cal-26 ~]# 

Like you say in comment 18: indeed system-config-kickstart *requires* anaconda.

reply to comment 17:
[root@cal-26 ~]# rpm -qa 'abrt*' 'libreport*' | sort
abrt-2.0.13-1.fc17.x86_64
abrt-addon-ccpp-2.0.13-1.fc17.x86_64
abrt-addon-kerneloops-2.0.13-1.fc17.x86_64
abrt-addon-python-2.0.13-1.fc17.x86_64
abrt-addon-vmcore-2.0.13-1.fc17.x86_64
abrt-addon-xorg-2.0.13-1.fc17.x86_64
abrt-dbus-2.0.13-1.fc17.x86_64
abrt-desktop-2.0.13-1.fc17.x86_64
abrt-gui-2.0.13-1.fc17.x86_64
abrt-libs-2.0.13-1.fc17.x86_64
abrt-plugin-bodhi-2.0.13-1.fc17.x86_64
abrt-retrace-client-2.0.13-1.fc17.x86_64
libreport-2.0.14-1.fc17.x86_64
libreport-filesystem-2.0.14-1.fc17.x86_64
libreport-gtk-2.0.14-1.fc17.x86_64
libreport-newt-2.0.14-1.fc17.x86_64
libreport-plugin-bugzilla-2.0.14-1.fc17.x86_64
libreport-plugin-kerneloops-2.0.14-1.fc17.x86_64
libreport-plugin-logger-2.0.14-1.fc17.x86_64
libreport-plugin-ureport-2.0.14-1.fc17.x86_64
libreport-python-2.0.14-1.fc17.x86_64
libreport-web-2.0.14-1.fc17.x86_64
[root@cal-26 ~]#

OS release string can overridden by the bugzilla plugin configuration. (It doesn't mean that the content of the os_release file will be changed, it only means that the bugzilla plugin will use a configured value instead of a value from the os_release file)


You can set the bugzilla os release string by issuing of the following command

$ echo "Bugzilla_OSRelease=Fedora release 17 (Beefy Miracle)" >> /etc/libreport/events/report_Bugzilla.conf


or in the bugzilla configuration dialogue

Configure Bugzilla -> Advanced -> OS release string

"Configure Bugzilla" will appear before submitting of the first bug if the bugzilla plugin is not configured yet


The configuration dialog can be opened from abrt-gui

Edit -> Pereference -> select Bugzilla row -> Configure Event

@Jakub Filak thanks for looking into this.

I tried both:
$ echo "Bugzilla_OSRelease=Fedora release 17 (Beefy Miracle)" >> /etc/libreport/events/report_Bugzilla.conf
and from abrt-gui:

Edit -> Pereference -> select Bugzilla row -> Configure Event

I filled in there what I found as last line on 
[root@cal-26 ~]# cat /etc/*release
Fedora release 17 (Beefy Miracle)
NAME=Fedora
VERSION="17 (Beefy Miracle)"
ID=fedora
VERSION_ID=17
PRETTY_NAME="Fedora 17 (Beefy Miracle)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:17"
Fedora release 17 (Beefy Miracle)
Fedora release 17 (Beefy Miracle)


In the bugreport it remains: "anaconda release bluesky"

I haven't found yet how to attach the screenshots here, so I mailed them directly to you.

Thanks, Joost and Jakub. It's "check", if not "checkmate". :-)

The F18-workaround (edit os_release) is obviously not going to work in F17 ...

Joost: You can always open a bug report against system-config-kickstart manually and attach the backtrace file. To attach a file, click "Add an attachment" near the top of the bug report page. Do you have reproducer for the system-config-kickstart crash?

Jakub: Did the fix Jiri mentions in Comment 4 go into F17?

The string "bluesky" appears in anaconda here:

$ rpm -ql anaconda | xargs grep -ls bluesky
/usr/lib64/python2.7/site-packages/pyanaconda/product.py
/usr/lib64/python2.7/site-packages/pyanaconda/product.pyc
/usr/lib64/python2.7/site-packages/pyanaconda/product.pyo

And for the record, here is what I have on a fully updated F17 system:

$ rpm -q abrt libreport anaconda python-meh system-config-kickstart | sort
abrt-2.0.13-1.fc17.x86_64
anaconda-17.29-1.fc17.x86_64
libreport-2.0.14-1.fc17.x86_64
python-meh-0.12-1.fc17.noarch
system-config-kickstart-2.8.8-2.fc17.noarch

Created attachment 625986 [details]
screenshot showing "anaconda release bluesky" in F17 abrt gui

Here is an F17 reproducer:

$ LANG=foo.UTF-8 system-config-kickstart

(process:3069): Gtk-WARNING **: Locale not supported by C library.
	Using the fallback 'C' locale.
/usr/share/system-config-kickstart/kickstartGui.py:103: GtkWarning: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
  xml = gtk.glade.XML ("/usr/share/system-config-kickstart/system-config-kickstart.glade", domain="system-config-kickstart")

$ rpm -q abrt libreport anaconda python-meh system-config-kickstart | sort
abrt-2.0.13-1.fc17.x86_64
anaconda-17.29-1.fc17.x86_64
libreport-2.0.14-1.fc17.x86_64
python-meh-0.12-1.fc17.noarch
system-config-kickstart-2.8.8-2.fc17.noarch

Created attachment 625987 [details]
bugzilla-event-configuration

Created attachment 625988 [details]
bugreport_anaconda_release_bluesky

(In reply to comment #26)
> Created attachment 625988 [details]
> bugreport_anaconda_release_bluesky

Thanks, Joost. That bug seems to have already been reported.

A search for this error (which I typed into gedit from the screenshot):
AttributeError: 'module' object has no attribute 'Firewall'

finds this:
Bug 820748 - system-config-kickstart is broken 

NB: To find it in BZ, you have to select all possible values for "Status" and paste the error message into the "Comment" field.

(In reply to comment #23)
I see the following function in file libreport/src/report-python/__init__.py

def getProduct_fromPRODUCT():
    try:
        from pyanaconda import product
        return product.productName
    except:
        try:
            import product
            return product.productName
        except:
            return ""

which causes that the os_release file always contains "anaconda release bluesky" if anaconda is installed. This function was introduced as a fix for bug #725857 (during clean installation the /etc/system-release doesn't exist). It is obvious that the obtaining of product name needs more work.

Anyway, you should be able to report a bug if you configure the bugzilla plugin as I described in Comment 21 . I verified it on this test case https://fedoraproject.org/wiki/QA:Testcase_Libreport_anaconda

(In reply to comment #20)
> @Steve Tyler 
> Thanks for looking into this, these are the results.
> 
> reply to comment 16:
> [root@cal-26 ~]# grep -rl bluesky /var/spool/abrt
> [root@cal-26 ~]# 
> [jringoot@cal-26 ~]$ grep -rl bluesky $HOME/.cache/abrt
> [jringoot@cal-26 ~]$ 
...

I found the libreport* directories in /tmp:

[stephent@walnut tmp]$ ls -1d /tmp/libreport*
/tmp/libreport-2012-10-12-05:36:32-2916
/tmp/libreport-2012-10-12-05:47:06-3088
[stephent@walnut tmp]$ grep -r bluesky /tmp/libreport*
/tmp/libreport-2012-10-12-05:36:32-2916/version:bluesky
/tmp/libreport-2012-10-12-05:36:32-2916/os_release:anaconda release bluesky
/tmp/libreport-2012-10-12-05:47:06-3088/version:bluesky
/tmp/libreport-2012-10-12-05:47:06-3088/os_release:anaconda release bluesky

(In reply to comment #28)
> (In reply to comment #23)
> I see the following function in file libreport/src/report-python/__init__.py
> 
> def getProduct_fromPRODUCT():
...
> Anyway, you should be able to report a bug if you configure the bugzilla
> plugin as I described in Comment 21 . I verified it on this test case
> https://fedoraproject.org/wiki/QA:Testcase_Libreport_anaconda

Thanks for the additional details. I tried what you suggested in Comment 21 and set the "OS release string" to "Fedora release 17 (Beefy Miracle)" from abrt-gui.

I hacked up a test program that installs a libreport handler with a fake component name and that generates an exception. BZ did not complain about "anaconda release bluesky" and instead reported an invalid component. Does that mean the the reporting process got past the os_release test?

I am reluctant to file fake bug reports against real components. Does the abrt project have an abrt-test component that could be used?

--- Running report_Bugzilla ---
Logging into Bugzilla at https://bugzilla.redhat.com
Checking for duplicates
Creating a new bug
fatal: RPC failed at server.  There is no component named 'FOO-system-config-kickstart-BAR' in the 'Fedora' product.
(exited with 1)

Created attachment 626209 [details]
libreport-test-1.py program that generates an exception handled by libreport

This is definitely not production quality ... :-)

(In reply to comment #22)
... 
> In the bugreport it remains: "anaconda release bluesky"
...

I believe that when the report is sent to BZ, the string in the os_release file is overridden by the string set in abrt-gui. IOW, the string in the os_release file is ignored ...

Were you able to send a report to BZ?

Created attachment 626381 [details]
libreport-test-1.py program that generates an exception handled by libreport

The method in Comment 21 works fine -- set the "OS release string" to "Fedora release 17 (Beefy Miracle)" from abrt-gui. Thanks!

The attached test program sets the component and version as follows:
    config = Config(programName="libreport", 
                    programVersion="@VERSION@")

--- Running report_Bugzilla ---
Logging into Bugzilla at https://bugzilla.redhat.com
Checking for duplicates
Creating a new bug
New bug id: 865975
Adding attachments to bug 865975
Logging out
Status: NEW https://bugzilla.redhat.com/show_bug.cgi?id=865975

@steve tyler
I manually changed the os_release file  so that it contains the string you suggested, it now stops at the next problem string:
[root@cal-26 libreport-2012-10-15-10:07:15-12785]# pwd
/tmp/libreport-2012-10-15-10:07:15-12785
[root@cal-26 libreport-2012-10-15-10:07:15-12785]# echo "Fedora release 17 (Beefy Miracle)" > os_release

[root@cal-26 libreport-2012-10-15-10:07:15-12785]# 
--- Running report_Bugzilla ---
Logging into Bugzilla at https://bugzilla.redhat.com
Checking for duplicates
Creating a new bug
fatal: RPC failed at server.  There is no component named 'system' in the 'Fedora' product.
(exited with 1)

even after [root@cal-26 libreport-2012-10-15-10:07:15-12785]# echo "Bugzilla_OSRelease=Fedora release 17 (Beefy Miracle)" >> /etc/libreport/events/report_Bugzilla.conf
als in the bugzilla configuration dialogue abrt-gui (which looks identical) it is now Fedora release 17 (Beefy Miracle).

same problem: 
--- Running report_Bugzilla ---
Logging into Bugzilla at https://bugzilla.redhat.com
Checking for duplicates
Creating a new bug
fatal: RPC failed at server.  There is no component named 'system' in the 'Fedora' product.
(exited with 1)

(In reply to comment #34)
...
> fatal: RPC failed at server.  There is no component named 'system' in the
> 'Fedora' product.
...

Thanks for your report. Maybe that should be 'system-config-kickstart'. What is in the files libreport*/component?

$ find /tmp/libreport-* -name component -execdir cat '{}' ';' -execdir echo ';' | sort
(The files don't have newlines ...)

There are some libreport*/component files with 'system' and some with 'system-config-kickstart' in /tmp on my system. I don't know why.

[root@cal-26 ~]# find /tmp/libreport-* -name component -execdir cat '{}' ';' -execdir echo ';' | sort
system
system
system
system
system
system
system
system
system
system
system
system
system
system
system
system
system
[root@cal-26 ~]#

Ok thanks Steve, I was able to generate a bugreport after:
[root@cal-26 libreport-2012-10-15-13:32:25-7322]# pwd
/tmp/libreport-2012-10-15-13:32:25-7322
[root@cal-26 libreport-2012-10-15-13:32:25-7322]#  echo "Fedora release 17 (Beefy Miracle)" > os_release
[root@cal-26 libreport-2012-10-15-13:32:25-7322]#  echo "system-config-kickstart" > component
[root@cal-26 libreport-2012-10-15-13:32:25-7322]# 


--- Running report_Bugzilla ---
Logging into Bugzilla at https://bugzilla.redhat.com
Checking for duplicates
Creating a new bug
New bug id: 866442
Adding attachments to bug 866442
Not attaching empty file 'other involved packages'
Logging out
Status: NEW https://bugzilla.redhat.com/show_bug.cgi?id=866442

(In reply to comment #34)
> @steve tyler
> I manually changed the os_release file  so that it contains the string you
> suggested, it now stops at the next problem string:
> [root@cal-26 libreport-2012-10-15-10:07:15-12785]# pwd
> /tmp/libreport-2012-10-15-10:07:15-12785
> [root@cal-26 libreport-2012-10-15-10:07:15-12785]# echo "Fedora release 17
> (Beefy Miracle)" > os_release
> 
> [root@cal-26 libreport-2012-10-15-10:07:15-12785]# 
> --- Running report_Bugzilla ---
> Logging into Bugzilla at https://bugzilla.redhat.com
> Checking for duplicates
> Creating a new bug
> fatal: RPC failed at server.  There is no component named 'system' in the
> 'Fedora' product.
> (exited with 1)
> 
> even after [root@cal-26 libreport-2012-10-15-10:07:15-12785]# echo
> "Bugzilla_OSRelease=Fedora release 17 (Beefy Miracle)" >>
> /etc/libreport/events/report_Bugzilla.conf
> als in the bugzilla configuration dialogue abrt-gui (which looks identical)
> it is now Fedora release 17 (Beefy Miracle).
> 
> same problem: 
> --- Running report_Bugzilla ---
> Logging into Bugzilla at https://bugzilla.redhat.com
> Checking for duplicates
> Creating a new bug
> fatal: RPC failed at server.  There is no component named 'system' in the
> 'Fedora' product.
> (exited with 1)

You've found a new bug. See #866526

Thank-you both.

Here's another new bug:
Bug 866563 - '@VERSION@' displayed in exception report, not version string

BZ tip: BZ will generate a bug link when you type in a string like Bug 866526. That works for comments too: Comment 37.

5.8.1. Autolinkification
https://bugzilla.redhat.com/docs/en/html/hintsandtips.html#AEN2656

Fixed in git

commit ea3428c63f6f1058d64fc1f32686c0cccee90b3c
Author: Jakub Filak <jfilak>
Date:   Mon Oct 15 17:21:01 2012 +0200

    get product/version from system configuration
    
    - try to get product/version from system configuration at first attempt
    - if system configuration is missing obtain product/component from
      anaconda
    - closes #741647
    
    Signed-off-by: Jakub Filak <jfilak>

abrt-2.0.17-1.fc17,libreport-2.0.17-1.fc17,btparser-0.21-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/abrt-2.0.17-1.fc17,libreport-2.0.17-1.fc17,btparser-0.21-1.fc17

Package abrt-2.0.17-1.fc17, libreport-2.0.17-1.fc17, btparser-0.21-1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-2.0.17-1.fc17 libreport-2.0.17-1.fc17 btparser-0.21-1.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16846/abrt-2.0.17-1.fc17,libreport-2.0.17-1.fc17,btparser-0.21-1.fc17
then log in and leave karma (feedback).

I'm not sure if this matters, but os_version does not have the release name: "(Spherical Cow)"

[joeblow@localhost xfr]$ cat /tmp/libreport-2012-10-25-06\:23\:41-1582/os_release | xargs
Fedora release 18
[joeblow@localhost xfr]$ cat ~/.cache/abrt/spool/ccpp-2012-10-25-06\:28\:29-1697/os_release | xargs
Fedora release 18 (Spherical Cow)
[joeblow@localhost xfr]$ rpm -q abrt libreport btparser python-meh
abrt-2.0.17-2.fc18.x86_64
libreport-2.0.17-1.fc18.x86_64
btparser-0.21-1.fc18.x86_64
python-meh-0.17-1.fc18.noarch

abrt-2.0.18-1.fc17,libreport-2.0.18-1.fc17,btparser-0.22-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/abrt-2.0.18-1.fc17,libreport-2.0.18-1.fc17,btparser-0.22-1.fc17

Package abrt-2.0.18-1.fc17, libreport-2.0.18-1.fc17, btparser-0.22-1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-2.0.18-1.fc17 libreport-2.0.18-1.fc17 btparser-0.22-1.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-17495/abrt-2.0.18-1.fc17,libreport-2.0.18-1.fc17,btparser-0.22-1.fc17
then log in and leave karma (feedback).

abrt-2.0.18-1.fc17, libreport-2.0.18-1.fc17, btparser-0.22-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.