Proposing as a Fedora 21 Blocker as per release criteria 2.3.3:

"When using a dedicated installer image that contains packages, the installer must be able to use the install medium as a package source."

This install image does not allow the use of the image as install media.

+1 blocker

+1 blocker

I've also verified that the same behavior is occurring with the network install as well.

The .comps.xml file on the DVD is missing the <environment> entries.

Problems with the network install are something different.

Discussed in 2014-09-03 Blocker review meeting. Accepted as a blocker because it violates the Alpha criterion: "When using a dedicated installer image that contains packages, the installer must be able to use the install medium as a package source."

I believe the Server install kickstart does not in fact include any environment groups:

## common stuff
@guest-agents
@standard
@core
@multimedia
@hardware-support

# Some development tools
@development-libs
@development-tools
@c-development
@rpm-development-tools
@fedora-packager

# Fedora Server.
# Including this causes the fedora-release-server package to be included,
# which in turn enables server-product-environment, and due to to its priority
# this will be the default environment.
@server-product
@headless-management
@container-management

# Common server packages
@mysql
@sql-server
@web-server

# Web Server environment
@haproxy
@mongodb
@perl-web
@python-web
@php
@rubyonrails
@tomcat

# Infrastructure Server
@directory-server
@dogtag
@dns-server
@freeipa-server
@ftp-server
@mail-server
@network-server
@printing
@smb-server
@virtualization
@load-balancer
@ha

@javaenterprise

# “uservisible” groups we want to offer
@editors
@network-server
@system-tools
@text-internet

I don't think any of those is an environment group. There is a "web-server-environment" environment group, but that isn't listed above (it includes @web-server, not @web-server-environment). There is a comment in comps-f21.xml.in referring to "fedora-server-environment", but AFAICS that doesn't actually exist.

There is a 'server-product-environment' group that is not listed in the kickstart. That's probably what should be included?

for the record, sgallagh indicated on IRC that I'm basically right, and he'll be fixing this, IIRC.

So, here's the issue. The environments are not actual groups that can be specified in the kickstart file. (This is probably worthy of a separate RFE).

What happens is that an environment group "magically" appears in the installer if all of the groups it depends on are present in the composed tree. In the case of server, I recently created a new group "domain-client" as a mandatory part of the Server environment, but I forgot to make the matching change to the kickstart. As a result, the composed image was unable to present the environment and the installer was effectively useless (unless explicitly pointed at the Everything tree).

I've corrected the issue in the Server kickstart, so when TC6 is built it should all work. I've done a manual compose successfully.

Marking this as POST until TC6 is generated.

"What happens is that an environment group "magically" appears in the installer if all of the groups it depends on are present in the composed tree."

that seems...messy, yeah, why isn't it just an environment group in comps which includes all the regular groups?

(In reply to Adam Williamson (Red Hat) from comment #10)
> "What happens is that an environment group "magically" appears in the
> installer if all of the groups it depends on are present in the composed
> tree."
> 
> that seems...messy, yeah, why isn't it just an environment group in comps
> which includes all the regular groups?

Well, this is essentially the magic way that allows any of our install media to automatically see all of the environments when we point it at the Everything tree during live installation. So it's not a bad idea to *also* allow this, but it would make composition easier if we could just specify a whole environment rather than its contents.

(In reply to Stephen Gallagher from comment #11)
> (In reply to Adam Williamson (Red Hat) from comment #10)
> > "What happens is that an environment group "magically" appears in the
> > installer if all of the groups it depends on are present in the composed
> > tree."
> > 
> > that seems...messy, yeah, why isn't it just an environment group in comps
> > which includes all the regular groups?
> 
> Well, this is essentially the magic way that allows any of our install media
> to automatically see all of the environments when we point it at the
> Everything tree during live installation. So it's not a bad idea to *also*
> allow this, but it would make composition easier if we could just specify a
> whole environment rather than its contents.

It turns out this already exists and I was just completely unaware of it. I'm going to go ahead and fix that in comps so we don't ever see a reappearance of this bug.

This is fixed in TC6, closing.