Created attachment 757311 [details]
File: anaconda-tb

Created attachment 757312 [details]
File: anaconda.log

Created attachment 757313 [details]
File: backtrace

Created attachment 757314 [details]
File: environ

Created attachment 757315 [details]
File: ifcfg.log

Created attachment 757316 [details]
File: lsblk_output

Created attachment 757317 [details]
File: nmcli_dev_list

Created attachment 757318 [details]
File: packaging.log

Created attachment 757319 [details]
File: program.log

Created attachment 757320 [details]
File: storage.log

Created attachment 757321 [details]
File: syslog

Description of problem:
Started installation from behind a firewall. This makes finding a mirror fail. After entering a valid URL pointing to a valid repository and selecting package selection screen, this bug comes up.

Version-Release number of selected component:
anaconda-19.30.2-1

Additional info:
reporter:       libreport-2.1.4
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:UUID=1add3c37-adc9-4aa2-b3f2-7f0fa76108c0
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.9.4-300.fc19.x86_64
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        19-TC1

Truncated backtrace:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/software.py", line 360, in on_environment_selection_changed
    self.on_environment_toggled(None, model.get_path(itr))
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/software.py", line 344, in on_environment_toggled
    for groupid in self.payload.environmentGroups(self.environment):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 1121, in environmentGroups
    raise NoSuchGroup(environmentid)
NoSuchGroup: None

Did some more testing.

Ifound, that this error comes up if anaconda can not find a repo immediatly after startup. I triggered it from behind a firewall, so anaconda could not query the mirrorlist. This makes anaconda not to look for the default mirrorlist, but does report back an error to the installation source item. But it is also trigered by using the askmethod commandline option. And also by supplying an invalid inst.repo url on the commandline. 

A work around is to put a valid inst.repo on the commandline.

The error does not reproduce if you boot with a valid inst.repo url on the commandline, then in the UI change the installation source to an invalid repo url, so you trigger an error state. And next change back to a valid repo url.

anaconda-19.30.4-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/anaconda-19.30.4-1.fc19

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

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.