http://defect.opensolaris.org/bz/show_bug.cgi?id=9947
John Leser <John.Leser at sun.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P4 |P3
Severity|minor |normal
--- Comment #7 from John Leser <John.Leser at sun.com> 2009-10-22 23:59:51 UTC
---
Right now, on my test machine, I'm consistently seeing BFU hang before reaching
the BFU prompt, because datalink-management has been disabled and nwam tore
down all the network interfaces:
[1]+ Stopped
/net/trigati.east/export/build/am223141/nwam1-build/usr/src/tools/scripts/bfu
/net/trigati.east/export/build/am223141/nwam1-build/archives/i386/nwam1-build-RC4
bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
index 1
inet 127.0.0.1 netmask ff000000
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252
index 1
inet6 ::1/128
bash-3.2# svcs -a | grep datalink
disabled 19:38:05 svc:/network/datalink-management:default
bash-3.2# nwamadm list
TYPE PROFILE STATE
ncp Automatic online
ncu:ip e1000g3 offline
ncu:phys e1000g3 uninitialized
ncu:ip e1000g2 offline
ncu:phys e1000g2 uninitialized
ncu:ip e1000g1 offline
ncu:phys e1000g1 uninitialized
ncu:ip e1000g0 uninitialized
ncu:phys e1000g0 uninitialized
ncp User disabled
loc myloc1 disabled
loc NoNet online
loc Automatic offline
enm myenm1 disabled
bash-3.2# pgrep bfu
356489
bash-3.2# ptree 356489
100004 /lib/svc/bin/svc.startd
100823 bash
356489 /bin/ksh /tmp/bfu.356489
/net/trigati.east/export/build/am223141/nwam
365182 gzip -d -c
/net/trigati.east/export/build/am223141/nwam1-build/arch
365183 cpio -it
365184 egrep -s ^var/svc/profile/platform_i86pc.xml
Given that this is happening fairly often, I'm upping the priority of this bug.
This will definitely be a usability problem for internal developers using BFU.
I also wonder if can possibly handle the sudden disappearance of the datalink
management daemon more gracefully?
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
