There are no details here.  Exactly what problem are you seeing?  Please attach complete logs, the traceback if you are getting it, and the details of what kind of install you are trying to perform.

This issue has been proposed when we are only considering blocker
issues in 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. **

See http://fedoraproject.org/wiki/How_to_debug_installation_problems for how to report anaconda problems, specifically the 'Writing the Report" section.

Created attachment 438630 [details]
Anaconda screen

I'm not sure how to get logs from remote machine during installation process. 

If you can describe me how to switch to console with messages on remote computer I will post you those messages.

Thanks 

Kamil

First, double check that the kickstart file it's prompting you for in the box actually exists.  Second, please make sure that the network is active for this install - there should be some sort of command line parameter being passed that tells anaconda how to bring up the network.

Assuming both of those are fine, I believe you should just be able to hit ctrl-z to drop to a shell, then scp /tmp/anaconda.log and /tmp/syslog to another machine, then attach those to this bug report.

Given the date this bug was opened, my guess is that it's a dupe of bug #623937.  Closing it now for lack of sufficient debugging information.

Hi,

I have this error message in anaconda.

Unable to retrieve                    
http://download.englab.brq.redhat.com/pub/rhel/rel-eng/RHEL6.0-20100811.2/6/Server/x86_64/os/images/install.img.  

I can't download log files so please try you to install RHEL6 on ibm-x3650m3-01.lab.eng.brq.redhat.com and check what problem is.

Network is up on this machine I can download manually image and kick start too.

But there is no scp, ls so I can't send you log files.



Thanks


Kamil

We discuss this bug with Ben Levenson and we think that should be considered as a blocker.

Please retest using a recent tree.  The  RHEL6-20100811.2 tree is right around the time we dealt with a NetworkManager issue that affected network-based installations.  Please use a current nightly tree, or at least a tree from 15-Aug or later.

(In reply to comment #8)
> Given the date this bug was opened, my guess is that it's a dupe of bug
> #623937.  Closing it now for lack of sufficient debugging information.

Failing also with nightly from 20100807 where the 623937 was not present.

I obtained logs from console in stage1 somehow:

Ctrl-Z
bash-4.1# echo $(</tmp/anaconda.log)
bash-4.1# while read L; do echo "$L"; read < /dev/tty ; done < /tmp/syslog

I will attach them.

Created attachment 439121 [details]
anaconda.log

I wonder if we really want usb0 device here (detected as ksdevice=link), we have also eth0 and eth1, see fragments of syslog in next comment.

Created attachment 439122 [details]
NM parts of syslog

Hi,

It helps to add ksdevice=E4:1F:13:65:94:74 parameter to beaker before provisioning system.

Now I'm able to install RHEL6 system.

It is probably eng-ops issue.



Thanks

Kamil

Hi,

I have removed RHEL 6.0 blocker.

While using ksdevice=E4:1F:13:65:94:74 instead of ksdevice=link will work-around the issue I still believe that it should be fixed. 

Why is anaconda trying to use ksdevice=usb0 ???

I would expect ksdevice=link to get translated into eth*, not usb*.

Thanks
Jirka

Anaconda is using usb0 because it is the first interface with link up (is it up, right?) as documented for option ksdevice. So it seems like a problem with the device (hw/network setup?), not with anaconda.
What kind of device is the usb0? Could you please provide /var/log/anaconda.log, /var/log/anaconda.syslog from successfuly installed system (using another device as in comment #16) or /tmp/anaconda.log /tmp/syslog from install environment?

How does the usb0 behave after install? Can it be configured with NM and used without problems?

Please provide the information requested in comment #17 so we can determine if this is a software problem or not.

Hi all,

we have been able to install RHEL 6 once today in the morning using ksdevice=E4:1F:13:65:94:74.

The we have opened a ticket with eng-ops to make this default Since then we are not able to install RHEL 6 anymore. Kamil owns the box, he will try to do provison in the Beaker tomorrow in the morning again. We will post the results here.

Current status:
==========================================================
Unable to download the kickstart file.  Please modify the  
kickstart parameter below or press Cancel to proceed as an 
interactive installation. 
============================================================

I can download the ks file. I will attach it.

bash-4.1# while read L; do echo "$L"; read < /dev/tty ; done < /tmp/syslog

<5>Kernel command line: initrd=/images/RHEL6.0-20100811.2_nfs-Server-x86_64/initrd.img ksdevice=E4:1F:13:65:94:74 kssendmac console=ttyS0,115200 ks=http://10.34.32.211/cblr/svc/op/ks/system/ibm-x3650m3-01.lab.eng.brq.redhat.com BOOT_IMAGE=/images/RHEL6.0-20100811.2_nfs-Server-x86_64/vmlinuz BOOTIF=01-e4-1f-13-65-94-74


Here is ifconfig output:bash-4.1# ifconfig 
eth0      Link encap:Ethernet  HWaddr E4:1F:13:65:94:74  
          inet addr:10.34.35.88  Bcast:10.34.35.255  Mask:255.255.252.0
          inet6 addr: 2620:52:0:2223:e61f:13ff:fe65:9474/64 Scope:Global
          inet6 addr: fe80::e61f:13ff:fe65:9474/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7705 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:645866 (630.7 KiB)  TX bytes:1134 (1.1 KiB)
          Interrupt:28 Memory:92000000-92012800 

eth1      Link encap:Ethernet  HWaddr E4:1F:13:65:94:76  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:40 Memory:94000000-94012800 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

usb0      Link encap:Ethernet  HWaddr E6:1F:13:57:94:77  
          inet addr:169.254.95.120  Bcast:169.254.95.255  Mask:255.255.255.0
          inet6 addr: fe80::e41f:13ff:fe57:9477/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2486 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1262 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:168354 (164.4 KiB)  TX bytes:61040 (59.6 KiB)


As you can see it should get kickstart via eth0. I don't know what usb0 is:
bash-4.1# ethtool eth0
Settings for eth0:
	Supported ports: [ TP ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supports auto-negotiation: Yes
	Advertised link modes:  10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Advertised pause frame use: No
	Advertised auto-negotiation: Yes
	Speed: 1000Mb/s
	Duplex: Full
	Port: Twisted Pair
	PHYAD: 1
	Transceiver: internal
	Auto-negotiation: on
	MDI-X: Unknown
	Supports Wake-on: g
	Wake-on: g
	Link detected: yes
bash-4.1# ethtool usb0
Settings for usb0:
	Current message level: 0x00000007 (7)
	Link detected: yes

I have tried to bring usb0. wget is still working just fine:

$ifconfig usb0 down
$wget http://10.34.32.211/cblr/svc/op/ks/system/ibm-x3650m3-01.lab.eng.brq.redhat.com


When I try to turn-off eth0 (eth1 is off by default) and I will leave only usb0 up then I cannot download ks:

bash-4.1# ip link show up
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether e4:1f:13:65:94:76 brd ff:ff:ff:ff:ff:ff
4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether e6:1f:13:57:94:77 brd ff:ff:ff:ff:ff:ff


bash-4.1# wget http://10.34.32.211/cblr/svc/op/ks/system/ibm-x3650m3-01.lab.eng.brq.redhat.com
--2010-08-18 11:27:57--  http://10.34.32.211/cblr/svc/op/ks/system/ibm-x3650m3-01.lab.eng.brq.redhat.com
Connecting to 10.34.32.211:80... failed: Network is unreachable.


Based on this I'm wondering if anaconda is really taking ksdevice=E4:1F:13:65:94:74 into the account. My impression is that it's still using usb0.

BTW, what is usb0? Why it gets IPv4 address? Should I try to turn it off in BIOS?

Feel free to check the system. Command is:
console ibm-x3650m3-01.lab.eng.brq.redhat.com

Thanks
Jirka

Created attachment 439412 [details]
ks file. http://10.34.32.211/cblr/svc/op/ks/system/ibm-x3650m3-01.lab.eng.brq.redhat.com

Hi all,

there is one BIG difference to the status tomorrow with ksdevice=link.

When I click on OK on the error message the installation will proceed. I should be able to provide the requested information soon.

When I have tried this yesterday I got the same error message over and over.

Thanks
Jirka

Hi,

I was able to install RHEL6.0 using
ksdevice=E4:1F:13:65:94:74

and clicking OK an anaconda error message 
==========================================================
Unable to download the kickstart file.  Please modify the  
kickstart parameter below or press Cancel to proceed as an 
interactive installation. 
============================================================

However, system has started without network - only loopback interface was up. I had to use serial console to bring up the network.

=======================================================================
[root@ibm-x3650m3-01 ~]# ip a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether e4:1f:13:65:94:74 brd ff:ff:ff:ff:ff:ff
    inet 10.34.35.88/22 brd 10.34.35.255 scope global eth0
    inet6 2620:52:0:2223:e61f:13ff:fe65:9474/64 scope global dynamic 
       valid_lft 2591951sec preferred_lft 604751sec
    inet6 fe80::e61f:13ff:fe65:9474/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether e4:1f:13:65:94:76 brd ff:ff:ff:ff:ff:ff
4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether e6:1f:13:57:94:77 brd ff:ff:ff:ff:ff:ff
    inet 169.254.95.120/24 brd 169.254.95.255 scope global usb0
    inet6 fe80::e41f:13ff:fe57:9477/64 scope link 
       valid_lft forever preferred_lft forever
5: sit0: <NOARP> mtu 1480 qdisc noop state DOWN 
    link/sit 0.0.0.0 brd 0.0.0.0
==========================================================================

I still don't know what usb0 is but it will get ONLY PRIVATE ADDRESS (169.254.95.120/24)

Feel free to log on the system. 
ssh ibm-x3650m3-01.lab.eng.brq.redhat.com
root:redhat

I'm going to provide anaconda logs:
$scp root.eng.brq.redhat.com:/var/log/anaconda* .
$cd ..
$tar jcvf ibm-x3650m3-01.lab.eng.brq.redhat.com-Anaconda_logs.tar.bz2 ibm-x3650m3-01.lab.eng.brq.redhat.com-Anaconda_logs

Thanks a lot!
Jirka

Created attachment 439435 [details]
Anaconda log files

Hi all,

following section shows manual intervention:

11:36:09,453 ERROR   : Error downloading http://10.34.32.211/cblr/svc/op/ks/system/ibm-x3650m3-01.lab.eng.brq.redhat.com: Coul
dn't connect to server
11:36:09,453 ERROR   : failed to retrieve http://10.34.32.211/cblr/svc/op/ks/system/ibm-x3650m3-01.lab.eng.brq.redhat.com
11:45:09,425 INFO    : file location: http://10.34.32.211/cblr/svc/op/ks/system/ibm-x3650m3-01.lab.eng.brq.redhat.com
11:45:09,425 INFO    : transferring http://10.34.32.211/cblr/svc/op/ks/system/ibm-x3650m3-01.lab.eng.brq.redhat.com
11:45:09,586 INFO    : setting up kickstart

Anaconda has failed to get ks first. After 10 minutes when I have clicked OK it has worked.

Thanks
Jirka

Just my thought: could it be that usb0 was already up and eth0 still down by first Anaconda's attempt to get ks file?

Jirka

Hi all,

I had just confirmed assumption made above:

$grep DHCPOFFER anaconda.syslog
<30>Aug 18 11:36:08 dhclient: DHCPOFFER from 169.254.95.118
<30>Aug 18 11:36:17 dhclient: DHCPOFFER from 10.34.32.1


11:36:09,453 ERROR   : Error downloading
http://10.34.32.211/cblr/svc/op/ks/system/ibm-x3650m3-01.lab.eng.brq.redhat.com:
Coul
dn't connect to server
11:36:09,453 ERROR   : failed to retrieve


At 11:36:09,453 only usb0 was up. Download has failed. eth0 was up at 11:36:17.

Conclusion: there is a race condition getting IP address for usb0 and eth0. usb0 gets only private address while eth0 will get global IPv4 address.

It seems like 
ksdevice=E4:1F:13:65:94:74
is being ignored. Anaconda is not waiting for eth0 (E4:1F:13:65:94:74) to have IP address.

Thanks
Jirka

I would propose this as a blocker for RHEL 6.0

Whatever usb0 is, it's conflicting with the installation.  Disable it.  An address assignment of 169.254.*.* from dhclient indicates DHCP failure.  Use ksdevice=eth0 or ksdevice=E4:1F:13:65:94:74 as you have been.  ksdevice=link does not guarantee a particular device, only the first one found that has an active link (note, that means a cable plugged in to it with the link light on), which may or may not constitute a _working_ link.  Users with multiple network devices should not be relying on ksdevice=link unless only a single interface will be connected at install time.

Hi David,

the problem is is that anaconda is failing with
ksdevice=E4:1F:13:65:94:74

Work-around is to click on "OK" in anaconda under this error message:
==========================================================
Unable to download the kickstart file.  Please modify the  
kickstart parameter below or press Cancel to proceed as an 
interactive installation. 
============================================================

At the current state anaconda seems to ignore
ksdevice=E4:1F:13:65:94:74

It's not waiting for eth0 (E4:1F:13:65:94:74) to have IP address. It will try to retrieve ks file as soon as either usb0 or eth0 is up. Please check the attached logs and comment #26.

Thanks
Jirka

(In reply to comment #29)
> 
> At the current state anaconda seems to ignore
> ksdevice=E4:1F:13:65:94:74
> 
> It's not waiting for eth0 (E4:1F:13:65:94:74) to have IP address. It will try
> to retrieve ks file as soon as either usb0 or eth0 is up. Please check the
> attached logs and comment #26.

You might be hitting bug #623937, can you try with Snap #12?

Hi Radek,

thanks fir the hint! I have tried RHEL6.0-20100818.0_ftp-Server-x86_64 and it works as expected:-) 

This BZ can be closed.

Jirka