RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 612184 - Cannot create and run on vmware workstation 7.1.0 build-261024
Summary: Cannot create and run on vmware workstation 7.1.0 build-261024
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-07 13:55 UTC by John Gorman
Modified: 2010-08-06 13:26 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-05 19:07:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description John Gorman 2010-07-07 13:55:31 UTC
Description of problem:

RHEL6 beta 2, both server and workstation versions:
Using vmware workstation 7.1.0 build-261024 to create
a vm gives this error:

"You have specified that the group 'X Windows' should
be installed. This group does not exist. Would you
like to continue or abort this installation."

Then at boot time I do not get a console prompt.
I cannot log in to find the IP, and therefor I
cannot ssh in. Completely unusable.

RHEL6 beta 1 works fine.

Version-Release number of selected component (if applicable):


How reproducible: Every time.

Steps to Reproduce:
1. Under vmware worstation create a new vm.
2. Wait for the console login prompt.
3. Never happens.
  
Actual results: Unusable VM.

Expected results: A console prompt.

Additional info:

Works:

RHEL6.0-20100414.0-AP-i386-DVD1.iso

Does not work:

RHEL6.0-20100622.1-Server-i386-DVD1.iso
RHEL6.0-20100622.1-Workstation-i386-DVD1.iso

Comment 2 Bill Nottingham 2010-07-08 01:35:59 UTC
This sounds like your kickstart file is incorrect. Can you attach it?

Comment 3 John Gorman 2010-07-08 13:06:49 UTC
Hi Bill

There is no kickstart file. VMware workstation just
asks for the location of the iso on my file system
and installs it.

Beta 1 works fine with VMware workstation.

Beta 2, both the server and the workstation versions
are unusable. The console freezes at the end of
the boot process and does not give a login prompt
or a login screen.

This is kind of important because VMware is the
easiest way to test a new OS. Plus people will
be evaluating this for VMware servers.

I have no idea whether this problem shows up on
VMware server. I am in programming and I don't
have direct access to the VMware server that runs
all of our production servers.

You can download VMware workstation yourself and
try it. I am sure that it is some tiny detail
that makes the difference.

- john

Comment 6 Chris Lumens 2010-07-14 19:40:28 UTC
This message:

"You have specified that the group 'X Windows' should
be installed. This group does not exist. Would you
like to continue or abort this installation."

only exists in the package selection code for kickstart:

clumens@exeter:~/src/anaconda$ git checkout rhel6-branch
Switched to branch 'rhel6-branch'
clumens@exeter:~/src/anaconda$ grep -r "You have specified" *
kickstart.py:                                _("You have specified that the "
kickstart.py:                                        _("You have specified that the "

What kind of installation are you doing?  Can you attach /tmp/anaconda.log from when you hit this error to this bug report if at all possible?

Comment 7 RHEL Program Management 2010-07-15 19:37:36 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 8 Joshua Kwan 2010-08-06 00:29:36 UTC
Hi guys, I maintain the Easy Install (Kickstart autogeneration) framework for VMware Workstation.
As you may have guessed, yes, there is a Kickstart file involved. The bug was that the "X Windows" comp name disappeared between RHEL6 Beta1 and Beta2 and we released Workstation 7.1.0 only with knowledge of Beta1. The bug has now been fixed and full RHEL6 support will be provided for 7.1.2. At this time I cannot provide an official ETA.

Thanks, and please let me know if any other issues of this sort (VMware + Kickstart) are encountered.

Comment 9 Chris Lumens 2010-08-06 13:26:29 UTC
Great, thanks for the status update.  Glad to hear it's been corrected.


Note You need to log in before you can comment on or make changes to this bug.