[1.9.1] Failure to get DHCP address during curtin install of IBM S822LC 8335-GTA
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Expired
|
Undecided
|
Unassigned | ||
curtin |
Incomplete
|
Medium
|
Unassigned |
Bug Description
While installing system I ran into:
[ 278.524290] tg3 0004:01:00.0 eth0: Link is down
[ 282.748081] tg3 0004:01:00.0 eth0: Link is up at 1000 Mbps, full duplex
[ 282.748275] tg3 0004:01:00.0 eth0: Flow control is off for TX and off for RX
[ 282.748345] tg3 0004:01:00.0 eth0: EEE is disabled
IP-Config: eth0 hardware address 98:be:94:01:0f:4c mtu 1500 DHCP RARP
hostname entei hostname entei hostname entei hostname entei hostname entei hostname entei hostname entei IP-Config: no response after 100 secs - giving up
/scripts/
done.
Begin: Loading essential drivers ... done.
Begin: Running /scripts/
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... IP-Config: eth0 hardware address 98:be:94:01:0f:4c mtu 1500 DHCP RARP
IP-Config: no response after 2 secs - giving up
IP-Config: eth0 hardware address 98:be:94:01:0f:4c mtu 1500 DHCP RARP
hostname entei IP-Config: no response after 3 secs - giving up
IP-Config: eth0 hardware address 98:be:94:01:0f:4c mtu 1500 DHCP RARP
hostname entei hostname entei hostname entei IP-Config: no response after 4 secs - giving up
IP-Config: eth0 hardware address 98:be:94:01:0f:4c mtu 1500 DHCP RARP
hostname entei hostname entei hostname entei IP-Config: no response after 6 secs - giving up
IP-Config: eth0 hardware address 98:be:94:01:0f:4c mtu 1500 DHCP RARP
hostname entei hostname entei hostname entei IP-Config: no response after 9 secs - giving up
IP-Config: eth0 hardware address 98:be:94:01:0f:4c mtu 1500 DHCP RARP
hostname entei hostname entei hostname entei hostname entei IP-Config: no response after 16 secs - giving up
IP-Config: eth0 hardware address 98:be:94:01:0f:4c mtu 1500 DHCP RARP
hostname entei hostname entei hostname entei hostname entei hostname entei IP-Config: no response after 25 secs - giving up
IP-Config: eth0 hardware address 98:be:94:01:0f:4c mtu 1500 DHCP RARP
hostname entei hostname entei hostname entei hostname entei hostname entei IP-Config: no response after 36 secs - giving up
IP-Config: eth0 hardware address 98:be:94:01:0f:4c mtu 1500 DHCP RARP
hostname entei hostname entei hostname entei hostname entei hostname entei hostname entei IP-Config: no response after 64 secs - giving up
IP-Config: eth0 hardware address 98:be:94:01:0f:4c mtu 1500 DHCP RARP
hostname entei hostname entei hostname entei hostname entei hostname entei hostname entei hostname entei IP-Config: no response after 100 secs - giving up
/scripts/
done.
mdadm: CREATE user root not found
mdadm: CREATE group disk not found
dpkg -l '*maas*'|cat
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 1.9.1+bzr4543-
ii maas-cli 1.9.1+bzr4543-
ii maas-cluster-
ii maas-common 1.9.1+bzr4543-
ii maas-dhcp 1.9.1+bzr4543-
ii maas-dns 1.9.1+bzr4543-
ii maas-proxy 1.9.1+bzr4543-
ii maas-region-
ii maas-region-
ii python-django-maas 1.9.1+bzr4543-
ii python-maas-client 1.9.1+bzr4543-
ii python-
Please refer to logs for bug 1558747 for maas logs for this.
Changed in maas: | |
status: | New → Incomplete |
Hi Larry,
Can you attach the curtin configuration from maas?
maas <maasuser> node get-curtin-config <system id>