https://bugzilla.novell.com/show_bug.cgi?id=758539
https://bugzilla.novell.com/show_bug.cgi?id=758539#c17
--- Comment #17 from C. Holm
I've reproduced the bug in 13.1 M4: - /etc/resolv.conf is empty at the end of first stage / begining of second stage
/etc/resolv.conf has proper/expected content when second stage is over.
Ah, interesting. I was never able to test that because our stage 2 fails for various reasons when DNS is unavailable. (And I haven't tested 13.1m4 yet; the following comments have been tested up to 12.3.)
I think, there is nothing what yast2-network can fix. It seems to me as requirement for another order of modules' proposals.
I don't think I understand what you're saying. It worked in the past (but see below), why is this serious change of behaviour considered to be ok?
(Note: according comment#1, requirement was to make dns configuration available earlier for use in addons)
I think you misunderstood me. I'm not talking about some rarely used addons, "<add-on>" is the AutoYAST feature that allows you to install from network repos, a pretty basic feature of AutoYAST. And I don't know and don't really care about *when* the relevant module writes the DNS configuration. I would like it to work the way it worked before. DNS basically *is* "network" to the general population. My stage2 depends on the network and DNS (is this such a crazy idea?), *plus* I'm using "keep_install_network", and, according to http://doc.opensuse.org/projects/autoyast/configuration.html#CreateProfile.N...,
YaST will keep network settings created during installation (via Linuxrc) and/or merge it with network settings from the AutoYaST profile (if defined). AutoYaST settings have higher priority than already present configuration files. […] If there is an empty or no dns and routing section, YaST will keep already present values. Otherwise settings from the profile will be applied.
However, with this bug, this is untrue. Stage2 will have no DNS, and hence if one tries to use it, the install will never be able to complete. (Ironically, in the case of scripts fetched from the network, AutoYAST doesn't recognize they're empty files because the network was down and reports them as having completed successfully. But I should maybe put this into a separate bug report.) Sorry if I sound rude, I don't mean to offend anybody. I just don't have insight into the AutoYAST development process and don't I'm pretty sure I misunderstood some of your comments. It sounds to me like you're saying "it has always been this way (which is untrue) and WONTFIX". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.