Comment 8 for bug 993666

My bad.
I totally forgot about this patch.
I won't have time for fixing and resubmitting it today, so if you want to
go ahead feel free to do that!

Dean had some fairly easy comments. Also the patch definitely needs a
rebase.

Salvatore

On 20 July 2012 10:35, Paul Maunders <email address hidden> wrote:

> I have also encountered this problem today with a fresh install of
> Ubuntu Precise, and following the devstack quick start instructions. The
> script failed while it was trying to download Cirrus UEC images.
>
> --2012-07-20 18:16:34--
> http://launchpad.net/cirros/trunk/0.3.0/+download/cirros-0.3.0-x86_64-uec.tar.gz
> Resolving launchpad.net (launchpad.net)... failed: Name or service not
> known.
> wget: unable to resolve host address `launchpad.net'
>
> I could see that all my nameservers had been removed from resolv.conf
>
> $ cat /etc/resolv.conf
> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by
> resolvconf(8)
> # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
> nameserver 127.0.0.1
>
> Did the patch ever get merged into the master branch?
>
> Can anyone suggest a work around?
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/993666
>
> Title:
> DNS stops during install
>
> Status in devstack - openstack dev environments:
> In Progress
>
> Bug description:
> Today, I was trying to get the latest devstack running on a VM (Ubuntu
> 12.04, updated today, running on Mac OS X 10.6.8 using VirtualBox
> 4.1.14 r77440).
>
> When devstack got to the point indicated in the full-res image linked
> below (somewhere between 'add_nova_opt vncserver_listen=127.0.0.1' and
> 'nova-manage db sync'), I lost DNS.
>
> As a result, later parts of the install fail (e.g., downloading the
> image file).
>
> This happens regardless of my VM network running in either bridged or
> NATed mode,
>
> In order to narrow things down, I was running a ping to Google, and as
> soon as I saw that the hostname stopped resolving, I hit ^c. I wasn't
> able to tell exactly which point DNS failed, due to the low time
> resolution and the undetermined reflex response time of my fingers :-)
>
> Full resolution screenshot:
>
> http://www.flickr.com/photos/oubiwann/7137334925/sizes/o/in/photostream/
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/devstack/+bug/993666/+subscriptions
>