Bug 1179362

Summary: Environment group selection broken with DNF payload (always installs same package set, whatever group you pick)
Product: [Fedora] Fedora Reporter: satellitgo
Component: anacondaAssignee: David Shea <dshea>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: anaconda-maint-list, awilliam, g.kaviyarasu, jonathan, pschindl, robatino, satellitgo, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: AcceptedBlocker
Fixed In Version: anaconda-22.16-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-26 16:52:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1043121    
Attachments:
Description Flags
boot iso anaconda log
none
boot iso anaconda log2
none
boot iso anaconda log3
none
boot iso anaconda log4
none
boot iso anaconda log5
none
program.log from a recreation of the bug
none
anaconda.log
none
dnf.rpm.log
none
dnf.log
none
packaging.log none

Description satellitgo 2015-01-06 15:36:44 UTC
Description of problem:
boot.iso installs result in console login
gnome selected

Version-Release number of selected component (if applicable):
http://kojipkgs.fedoraproject.org/mash/rawhide-20150101/rawhide/x86_64/os/images/boot.iso

http://kojipkgs.fedoraproject.org/mash/

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
logs in to console login which works

Expected results:
login to graphical desktop

Additional info:

Comment 1 David Shea 2015-01-06 15:54:15 UTC
Please attach the logs from /var/log/anaconda

Comment 2 satellitgo 2015-01-06 17:15:32 UTC
Created attachment 976868 [details]
boot iso anaconda log

Comment 3 satellitgo 2015-01-06 17:16:14 UTC
Created attachment 976869 [details]
boot iso anaconda log2

Comment 4 satellitgo 2015-01-06 17:16:44 UTC
Created attachment 976870 [details]
boot iso anaconda log3

Comment 5 satellitgo 2015-01-06 17:17:12 UTC
Created attachment 976871 [details]
boot iso anaconda log4

Comment 6 satellitgo 2015-01-06 17:17:40 UTC
Created attachment 976872 [details]
boot iso anaconda log5

Comment 7 Fedora Blocker Bugs Application 2015-01-06 17:32:21 UTC
Proposed as a Freeze Exception for 22-alpha by Fedora user satellit using the blocker tracking app because:

 dnf fails on boot.iso install? workstation installs 297 rpms  anaconda 22.13-1

Comment 8 David Shea 2015-01-06 18:05:46 UTC
Could you attach the actual files, please? As text? In particular, the packaging.log.

Comment 9 satellitgo 2015-01-06 18:08:49 UTC
I am not sure how to do this on a minimal install; that is why the screen photos(In reply to David Shea from comment #8)
> Could you attach the actual files, please? As text? In particular, the
> packaging.log.

I am not sure how to do this on a minimal install; that is why the screen photos

Will try...

Comment 10 Adam Williamson 2015-01-06 19:21:17 UTC
You can mount a USB stick manually, or ssh them across to another system, or even fpaste out ones that are small enough.

Comment 11 Adam Williamson 2015-01-06 20:52:25 UTC
Created attachment 976939 [details]
program.log from a recreation of the bug

Comment 12 Adam Williamson 2015-01-06 20:53:07 UTC
Created attachment 976941 [details]
anaconda.log

Comment 13 Adam Williamson 2015-01-06 21:10:37 UTC
Created attachment 976956 [details]
dnf.rpm.log

Comment 14 Adam Williamson 2015-01-06 21:11:13 UTC
Created attachment 976957 [details]
dnf.log

Comment 15 Adam Williamson 2015-01-06 21:11:52 UTC
Created attachment 976958 [details]
packaging.log

Comment 16 DO NOT USE account not monitored (old adamwill) 2015-01-06 21:49:22 UTC
To reproduce:

1. Boot 2015-01-05 Rawhide boot.iso
2. Pick any sane partition layout
3. Go to Software Selection and choose 'Fedora Workstation'
4. Return to hub, verify that 'Software Selection' is still picked
5. Begin install, note only 297 packages are installed
6. Boot installed system; it boots to a console, no GNOME-ish packages installed

This appears to be DNF only. Booting with inst.nodnf and doing the same thing results in a package set problem (sssd-common), indicating that yum is properly selecting the Workstation environment (because that package is a part of it).

I believe the bug actually affects the default environment group also. Currently the default is 'Fedora Cloud Server' due to https://bugzilla.redhat.com/show_bug.cgi?id=1177002 , but if you examine the dnf.rpm.log file, packages from that environment - 'cloud-init', for instance - are not installed. I'm not sure exactly what package set is actually getting installed - it doesn't seem to be just @core - but it's not even the default environment group.

Comment 17 DO NOT USE account not monitored (old adamwill) 2015-01-06 21:51:10 UTC
It's *possible* this could somehow boil down to DNF hiding dependency issues: perhaps it's somehow throwing out a bunch of packages to avoid the sssd-common dep issue. But I don't *think* that should be it, because sssd-common isn't required by that much stuff. Trying to remove it from my desktop only results in sssd and freeipa-client being removed. So I don't think that, even if DNF is silently dropping stuff to avoid this dep issue, it should result in *so* many packages being dropped.

Comment 18 Adam Williamson 2015-01-06 22:00:55 UTC
I'm proposing this as a blocker (instead of FE) as it violates https://fedoraproject.org/wiki/Fedora_22_Alpha_Release_Criteria#Package_sets as currently written: "When doing a graphical install using the dedicated installer images, the installer must be able to install each of the release blocking desktops, as well as the minimal package set."

I do have a proposal in to change that criterion, but I still think it ought to cover this case, though you could argue possibly not for Alpha.

Comment 19 Petr Schindler 2015-01-07 16:45:43 UTC
Discussed at today's blocker review meeting [1]. Accepted as a blocker. This bug is a clear violation of the Alpha Package Sets criterion: When doing a graphical install using the dedicated installer images, the installer must be able to install each of the release blocking desktops, as well as the minimal package set.

[1] http://meetbot.fedoraproject.org/fedora-blocker-review/2015-01-07/

Comment 20 satellitgo 2015-01-26 15:45:51 UTC
boot.iso x86_64 20150124 installs KDE correctly to bare metal

https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150124_Installation

detects workstation check failure.

looks fixed

Comment 21 Adam Williamson 2015-01-26 16:52:28 UTC
yeah, seems like this is fixed now. thanks.