Bug 693356

Summary: Graphical minimal installation not installing minimal package set
Product: Red Hat Enterprise Linux 6 Reporter: Miroslav Vadkerti <mvadkert>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team>
Severity: high Docs Contact:
Priority: high    
Version: 6.1CC: ddumas, dgregor, ebenes, notting, ohudlick, pvrabec, sgrubb
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-04 17:50:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 682670    
Attachments:
Description Flags
/var/log/anaconda.log from installation
none
/root/install.log from installation
none
/var/log/anaconda.yum.log from installation none

Description Miroslav Vadkerti 2011-04-04 12:14:30 UTC
Description of problem:
Graphical minimal installation is not installing the minimal package set.

Graphical installation is installing 265 packages. The correct count seems to be 229 packages as text installation method is installing. 

Version-Release number of selected component (if applicable):
anaconda-13.21.108-1.el6

How reproducible:
100%

Steps to Reproduce:
1. Start installation of RHEL6.1 via graphical installation.
2. Select Minimal package set
3. Do not select any additional repo
4. Proceed with installation with the default settings
  
Actual results:
Graphical minimal installation installs 265 packages

Expected results:
Graphical minimal installation installs 229 packages (same as text installation)

Additional info:
I will post a diff of packages installed via text/graphical method soon

Comment 1 Miroslav Vadkerti 2011-04-04 12:29:52 UTC
These are the packages installed only in graphical installation:

boost-1.41.0-11.el6.x86_64
boost-date-time-1.41.0-11.el6.x86_64
boost-filesystem-1.41.0-11.el6.x86_64
boost-graph-1.41.0-11.el6.x86_64
boost-iostreams-1.41.0-11.el6.x86_64
boost-program-options-1.41.0-11.el6.x86_64
boost-python-1.41.0-11.el6.x86_64
boost-regex-1.41.0-11.el6.x86_64
boost-serialization-1.41.0-11.el6.x86_64
boost-signals-1.41.0-11.el6.x86_64
boost-system-1.41.0-11.el6.x86_64
boost-test-1.41.0-11.el6.x86_64
boost-thread-1.41.0-11.el6.x86_64
boost-wave-1.41.0-11.el6.x86_64
ConsoleKit-0.4.1-3.el6.x86_64
ConsoleKit-libs-0.4.1-3.el6.x86_64
cryptsetup-luks-1.2.0-2.el6.x86_64
cryptsetup-luks-libs-1.2.0-2.el6.x86_64
dbus-1.2.24-4.el6_0.x86_64
eggdbus-0.6-3.el6.x86_64
hal-0.5.14-10.el6.x86_64
hal-info-20090716-3.1.el6.noarch
hal-libs-0.5.14-10.el6.x86_64
hdparm-9.16-3.4.el6.x86_64
libicu-4.2.1-9.el6.x86_64
matahari-0.4.0-1.el6.x86_64
matahari-agent-lib-0.4.0-1.el6.x86_64
matahari-host-0.4.0-1.el6.x86_64
matahari-lib-0.4.0-1.el6.x86_64
matahari-net-0.4.0-1.el6.x86_64
matahari-service-0.4.0-1.el6.x86_64
pm-utils-1.2.5-9.el6.x86_64
polkit-0.96-2.el6.x86_64
qpid-cpp-client-0.10-1.el6.x86_64
qpid-qmf-0.10-5.el6.x86_64
sigar-1.6.5-0.1.git833ca18.el6.x86_64

Comment 2 Chris Lumens 2011-04-04 14:31:07 UTC
Please attach /tmp/anaconda.log and /tmp/yum.log to this bug report.

Comment 3 Miroslav Vadkerti 2011-04-04 16:55:37 UTC
Created attachment 489810 [details]
/var/log/anaconda.log from installation

Comment 4 Miroslav Vadkerti 2011-04-04 16:57:03 UTC
Created attachment 489812 [details]
/root/install.log from installation

Comment 5 Miroslav Vadkerti 2011-04-04 16:58:39 UTC
sorry but the yum.log was empty, I don't know the reason, is the above sufficient?

Comment 6 Miroslav Vadkerti 2011-04-04 17:01:57 UTC
Yikes, I found anaconda.yum.log in /var/log .. attaching now

Comment 7 Miroslav Vadkerti 2011-04-04 17:03:25 UTC
Created attachment 489813 [details]
/var/log/anaconda.yum.log from installation

Comment 8 Dennis Gregorovic 2011-04-04 17:33:03 UTC
I believe this is the same issue as bug 685127

Comment 9 Chris Lumens 2011-04-04 17:50:15 UTC

*** This bug has been marked as a duplicate of bug 685127 ***