Bug 174801

Summary:	no nis possible after minimal install (multiple BOOTPROTO=dhcp due to NM)
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Olaf Hering <ohering>
Component:	Installation	Assignee:	Michal Zugec <mzugec>
Status:	RESOLVED WONTFIX	QA Contact:	Stanislav Visnovsky <visnov>
Severity:	Normal
Priority:	P5 - None	CC:	locilka, suse-beta
Version:	Final
Target Milestone:	---
Hardware:	PowerPC
OS:	Linux
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	bug174801.tar.bz2

Description Olaf Hering 2006-05-11 10:37:57 UTC

doing a minimal install of 10.1 on bramble.suse.de
after install, no NIS is possible, ypdomainname is never set for some reason. likely some package is missing to actually do the right thing. but its not obvious what package that is.

Comment 1 Olaf Hering 2006-05-11 10:40:59 UTC

Created attachment 82985 [details]
bug174801.tar.bz2

Comment 2 Jiří Suchomel 2006-05-11 11:05:53 UTC

What does it mean "no NIS is possible"? NIS configuration does not work? Or is NIS option missing in the selection of authenticaton types?

Comment 3 Olaf Hering 2006-05-11 11:11:21 UTC

ypdomainname is not set during boot.
not necessary a yast bug.

Comment 4 Jiří Suchomel 2006-05-11 12:17:57 UTC

probably not

Comment 5 Peter Poeml 2006-05-11 18:31:40 UTC

In boot.msg, sysconfig says for all interfaces "dhcpcd is still waiting for data", and when ypbind starts, it says "No domainname setskipped".  It seems that no address had been obtained in time.  I think that's how it works currently. We don't have a 'rcypbind reload' in a post-configuration hook script, so far.  Christian, is that a correct view? (sorry about always asking so stupid questions, but I may not be up to speed with current boot/network setup framework)

Comment 6 Christian Zoz 2006-05-12 09:11:18 UTC

Don't configure multiple interfaces with STARTMODE=auto and BOOTPROTO=dhcp. If you want that, then you should set DHCLIENT_PRIMARY_DEVICE. Read the explanation in ifcfg.template.

So this is either invalid or a configuration bug.

Comment 7 Olaf Hering 2006-05-12 09:23:55 UTC

yast did that for me.

Comment 8 Christian Zoz 2006-05-12 09:41:34 UTC

It should not.

Comment 9 Martin Vidner 2006-05-16 16:02:46 UTC

Olaf enabled NM and then disabled it again, triggering the bug. yast2-network-2.13.20, if it enables NetworkManager, will create minimal ifcfgs so that the firewall UI can manipulate with the NICs and assign them to zones. The ifcfgs have STARTMODE=auto and BOOTPROTO=dhcp. 

Lukas, do we still need the feature now that SFw has the "any" feature?

Comment 10 Lukas Ocilka 2006-05-17 06:29:25 UTC

Well, the 'any' feature wasn't tested for functions used in the Firewall proposal, also functions used in yast2-firewall module were not changed. There are completely new functions in the SuSEFirewall module for this feature and they were used only for CWMSuSEFirewallInterfaces.

e.g.: compare SuSEFirewall::GetZonesOfInterfaces() and SuSEFirewall::GetZonesOfInterfacesWithAnyFeatureSupported()

Yes, I could create some special function in the SuSEFirewall module if you tell me what exactly should it do :)

Comment 11 Martin Vidner 2006-08-28 11:52:41 UTC

Reassigning to the new maintainer of yast2-network.

Comment 12 Michal Zugec 2007-05-28 12:54:19 UTC

>>There are completely new functions in the SuSEFirewall module for this >>feature and they were used only for CWMSuSEFirewallInterfaces.

Lukas, could you provide more details that functions you mean?

Comment 13 Lukas Ocilka 2007-05-30 08:09:02 UTC

It seems that neither 10.2 nor 10.3 contain such problem with enabling/disabling NetworkManager, mainly because it creates ifcfg files which can be later handled by NetworkDevices module used by Firewall.

We don't expect doing anything with this for 10.1, so closing as WONTFIX.
Sorry.