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 622558 - kickstart vnc install fails
Summary: kickstart vnc install fails
Keywords:
Status: CLOSED DUPLICATE of bug 610769
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.1
Hardware: x86_64
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-08-09 18:14 UTC by gregrwm
Modified: 2010-08-09 23:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-09 18:24:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
from anaconda via scp (150.12 KB, text/xml)
2010-08-09 18:14 UTC, gregrwm 		no flags Details
another from anaconda via scp, this one without kickstart (155.75 KB, text/xml)
2010-08-09 19:15 UTC, gregrwm 		no flags Details
View All

Description gregrwm 2010-08-09 18:14:44 UTC 
Created attachment 437671 [details]
from anaconda via scp

Description of problem:  upon opening vnc window, anaconda was displaying it had a problem

Version-Release number of selected component (if applicable):  RHEL6.0-20100715.2-Server-x86_64-DVD1.iso

Steps to Reproduce:
1.  extract install.img, vmlinux, initrd.img, put on nfs server with kickstart file

2.  kickstart file content:
install
nfs --server=192.168.1.242 --dir=/var/spool/up2date/r6
vnc --password=foo
key foo
lang en_US.UTF-8
keyboard us
network --device 00:16:36:7E:CA:7A --bootproto static --ip 209.999.82.2     --gateway 209.999.82.14 --netmask 255.255.255.240 --hostname bleep.999.net
network --device 00:16:36:7E:CA:7B --bootproto static --ip 192.168.2.43 --nameserver 192.168.2.42 --netmask 255.255.255.0
rootpw --iscrypted $1$qtu.AIJq$YToV.foo
authconfig --enableshadow --enablemd5
selinux --disabled
timezone --utc America/Chicago
firstboot --disable
%packages
@base
@core
@basic-desktop
@network-file-system-client
@x11
%end

3.  boot parameters:  quiet panic=30 ksdevice=00:16:36:7E:CA:7B netmask=255.255.255.0 ip=192.168.2.43 gateway=192.168.2.42 dns=192.168.2.42 ks=nfs:192.168.2.42:/path/r6/bleep.ks
  
Actual results:  open vnc connection, find problem report, save via scp

Expected results:  continue install
Comment 1 Chris Lumens 2010-08-09 18:24:49 UTC 

*** This bug has been marked as a duplicate of bug 610769 ***
Comment 2 gregrwm 2010-08-09 19:11:47 UTC 
tried again without kickstart, boot parameters:  quiet panic=30 ksdevice=00:16:36:7E:CA:7B netmask=255.255.255.0 ip=192.168.2.43 gateway=192.168.2.42 dns=192.168.2.42 hostname=pecan vnc vncpassword=foo lang=en_US keymap=us repo=nfs:192.168.2.42:/path/r6

maybe same bug or maybe not, anaconda signature follows.  these disks have a bad raid superblock, that may be what's tripping up anaconda, i was hoping/expecting the installer would offer to start fresh.
Comment 3 gregrwm 2010-08-09 19:15:08 UTC 
Created attachment 437684 [details]
another from anaconda via scp, this one without kickstart
Comment 4 gregrwm 2010-08-09 19:54:38 UTC 
i don't know about the first anaconda attachment but the second signature attachment is probably related to bad raid superblocks on disk, when i removed those partitions anaconda was able to continue.
Comment 5 gregrwm 2010-08-09 19:56:36 UTC 
in other words, probably not a duplicate of the ethernet device bug.
Comment 6 Chris Lumens 2010-08-09 20:03:35 UTC 
Please don't use a single bug report as a dumping ground for every issue you run across.  The initial bug you reported is identical to 610769.  Both used kickstart, both displayed the same traceback.  Obviously when you switched to not using kickstart but instead specified everything on the command line, the traceback went away because kicsktart.py was no longer involved.
Comment 7 gregrwm 2010-08-09 23:40:50 UTC 
sorry, my submission of comment#2 was a "mid air collision", so i resubmitted it anyway, the only choice offered by bugzilla other than to lose it.  might be nicer for bugzilla to output the comment text i'd submitted, so i could then paste it into a new bug.  now of course you'll say i should submit a bug against bugzilla.  anyway now you know why i submitted the second attachment here anyway.  maybe tomorrow i'll get time to resubmit it as a separate bug, gotta go now..
Note You need to log in before you can comment on or make changes to this bug.