NetworkManager update breaks DNS config [SOLVED?]

[Patrick O'Callaghan]

On Fri, 2013-02-22 at 13:34 +0800, Ed Greshko wrote:
> On 02/22/13 13:24, Patrick O'Callaghan wrote:
> > On Fri, 2013-02-22 at 11:35 +0800, Ed Greshko wrote:
> >> [egreshko at localhost ~]$ cat /etc/resolv.conf
> >> # Generated by NetworkManager
> >> nameserver 192.168.0.1
> >>
> >> You've downgraded NetworkManager to confirm it fixes the issue?
> > Downgrading threw up some dependency issues which I couldn't be bothered
> > tracking down, however reinstalling NM (in fact erasing, installing
> > again and rebooting) seems to have fixed it (i.e. /etc/resolv.conf is
> > now correct and shows a mod time consistent with the reboot rather than
> > the earlier manual correction. Go figure.
> 
> Good to hear....   I wonder how your system got to F18.  On one "real" system here F18 was installed during the beta test phase due to a premature disk failure.  After the release, and a distro-sync, and a few updates I had some weird errors with (I wish I could remember) one package.  I too had to erase and install that package to get things back in order. 

Updated via fedup from F17. It took two tries IIRC. I did wonder about
package consistency. In a separate thread I mentioned that "yum
check-update" was giving errors while "yum --assumeno update" worked,
which doesn't seem consistent.

poc