|
Bugzilla – Full Text Bug Listing |
| Summary: | resolv.conf missing when NetworkManager tabooed | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.2 | Reporter: | Felix Miata <mrmazda> |
| Component: | Installation | Assignee: | Michal Filka <mfilka> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | jengelh, jreidinger, rmilasan |
| Version: | Milestone 3 | ||
| Target Milestone: | --- | ||
| Hardware: | 32bit | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
y2logs
y2logs from 12.2B2+ factory install to host gx62b y2logs |
||
Created attachment 497290 [details]
y2logs from 12.2B2+ factory install to host gx62b
This is apparently mostly fixed. Shortly before installation completed, I went to tty2 to examine /etc/resolv.conf and /mnt/etc/resolv.conf. The former contained the DNS# from cmdline, while the latter was empty. On first boot, the first thing to happen on the blue screen was unable to refresh popup. I chose to skip, after which text yast finished auto configuration, configuring resolv.conf with the DNS# from installation cmdline, resulting in working network.
Some openSUSE bugs for the new maintainer of yast2-network. I think, it is same problem as in bnc#758539 *** This bug has been marked as a duplicate of bug 758539 *** That bug was filed against 12.1, so isn't fixable unless changed to 12.2, which would get this one lost. Still happened on first boot in 12.2RC2.5 so that repos could not auto-refresh, but after yast was finished a working resolv.conf appeared. Created attachment 504319 [details] y2logs On host st40a it happened again with whatever's currently in http://download.opensuse.org/distribution/12.2/. YaST didn't bother to open automatically on first boot as it normally does to clean up the installation. This is my first ever installation of any openSUSE without Grub Legacy as default. On host kt880 it happened again with 12.3M1. YaST didn't bother to open automatically on first boot as it normally does to clean up the installation. y2logs @ bug 789900 I could reproduce the issue with 12.3 (Final). DNS settings from cmdline / bootparams are not written to target's /etc/resolv.conf. Please open new bug for issue described in Comment#6 and Comment#7 as it has nothing to do with yast2-network. Thanks. *** Bug 771298 has been marked as a duplicate of this bug. *** lets keep only one bug for same issue *** This bug has been marked as a duplicate of bug 771298 *** (In reply to Josef Reidinger from comment #11) > lets keep only one bug for same issue > > *** This bug has been marked as a duplicate of bug 771298 *** Yes, let's, and let's make the one that actually meets the duplicate the duplicate. The later bug duplicates the first. One cannot duplicate that which does not exist. *** Bug 771298 has been marked as a duplicate of this bug. *** 12.2 is out of support. Please reproduce on current release and open a new issue if it is still happening. |
Created attachment 492699 [details] y2logs I would have used something newer than M3 to confirm if I could find something that would install at all, but factory-snapshot was all I could make install. To reproduce: 1-start minimal server HTTP install 2-deselect firewall 3-taboo SuSEfirewall2, ModemManager, NetworkManager, wireless-tools and various other wired network packages not essential behind a firewall 4-finish installation 5-reboot Actual behavior: 1-YaST can't refresh repos 2-networking non-functional 3-/etc/resolv.conf does not exist Expected behavior: 1-YaST finishes up normally 2-networking works 3-dns from installation cmdline is present in resolv.conf