Bug 1014306

Summary:	Different installation using graphic or text mode
Product:	Red Hat Gluster Storage	Reporter:	Scott Haines <shaines>
Component:	distribution	Assignee:	Anthony Towns <atowns>
Status:	CLOSED NOTABUG	QA Contact:	Rejy M Cyriac <rcyriac>
Severity:	high	Docs Contact:
Priority:	high
Version:	2.1	CC:	ahatfiel, flanagan, grajaiya, rhs-bugs, sdharane
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-22 13:57:15 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:

Description Scott Haines 2013-10-01 17:12:25 UTC

Installed RHS 2.1 nodes on laptop (4GB, using VMs of 512MB) w/ graphic installation disabled; used text installation. After default install and at first reboot, machine does not have the Gluster tools. Discovered difference between pakages installed:

**Text mode installation**
...
%packages --nobase
@core
%end

**Graphic mode installation**
...
%packages
@core
@glusterfs-all
@glusterfs-swift
@rhs-tools
@scalable-file-systems
abrt-gui
%end

Comment 1 Anthony Towns 2013-10-09 05:04:20 UTC

The documentation for anaconda says the 'text' boot option should behave this way:

text
    Force text mode install. This will install only base packages for a minimal system and implies that the installed system will boot up in runlevel 3 instead of to the graphical login screen.

https://fedoraproject.org/wiki/Anaconda_Boot_Options?rd=Anaconda/Options

I'm not sure that's entirely logical (and I couldn't see it documented in the RHEL guides), but it would be something that would need to be changed in RHEL and anaconda upstream, rather than being something specific to RHS. Given it's only an issue if the user specifies the 'text' boot option explicitly or has less than 640MiB of memory, I'm not sure this is worth escalating.

Comment 3 Anthony Towns 2013-10-22 13:57:15 UTC

(In reply to Anthony Towns from comment #1)
> The documentation for anaconda says the 'text' boot option should behave
> this way:
> 
> text
>     Force text mode install. This will install only base packages for a
> minimal system and implies that the installed system will boot up in
> runlevel 3 instead of to the graphical login screen.
> 
> https://fedoraproject.org/wiki/Anaconda_Boot_Options?rd=Anaconda/Options
> 
> I'm not sure that's entirely logical (and I couldn't see it documented in
> the RHEL guides), but it would be something that would need to be changed in
> RHEL and anaconda upstream, rather than being something specific to RHS.
> Given it's only an issue if the user specifies the 'text' boot option
> explicitly or has less than 640MiB of memory, I'm not sure this is worth
> escalating.

Per the above, closing this as NOTABUG.