215341 – Network inst srcs used after reboot, although network not yet started

Bug 215341 - Network inst srcs used after reboot, although network not yet started

Summary: Network inst srcs used after reboot, although network not yet started

Status:	RESOLVED DUPLICATE of bug 218705

Alias:	None

Product:	openSUSE 10.2
Classification:	openSUSE
Component:	Update Problems (show other bugs)
Version:	Beta 1
Hardware:	Other Other

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	Ladislav Slezák
QA Contact:	Jiri Srain

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2006-10-26 16:08 UTC by Will Stephenson
Modified:	2006-11-07 15:18 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	Other
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
y2logs (641.24 KB, application/x-tgz) 2006-10-26 16:09 UTC, Will Stephenson	Details
/var/log/messages showing initial network start, and subsequent restart to get an ethernet connection (88.84 KB, application/x-gzip) 2006-10-26 16:12 UTC, Will Stephenson	Details
View All Add an attachment (proposed patch, testcase, etc.)

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

Description Will Stephenson 2006-10-26 16:08:57 UTC

I updated alpha5 to beta1 and after the initial reboot, i got some install source errors because some network instsrcs I had configured were still enabled, although the network system had not been started.  This included both ftp and nfs install sources, so it's not _just_ networking that is a problem here.

Comment 1 Will Stephenson 2006-10-26 16:09:37 UTC

Created attachment 102733 [details]
y2logs

Comment 2 Will Stephenson 2006-10-26 16:12:50 UTC

Created attachment 102734 [details]
/var/log/messages showing initial network start, and subsequent restart to get an ethernet connection

I restarted the network by hand to get the instsrcs up, as you can see at the end of the log

Comment 3 Ladislav Slezák 2006-11-07 15:18:59 UTC


*** This bug has been marked as a duplicate of bug 218705 ***