** Changed in: libvirt (Ubuntu)
Status: Incomplete = Fix Released
** Changed in: libvirt (Ubuntu Maverick)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
(Assigned to Dave to get his response)
** Changed in: libvirt (Ubuntu)
Assignee: Serge Hallyn (serge-hallyn) = Dave Walker (davewalker)
** Changed in: libvirt (Ubuntu Maverick)
Assignee: Serge Hallyn (serge-hallyn) = (unassigned)
--
You received this bug notification because you are
@Mark
please give a more complete scenario so we can reason through it. For
whom is one of hte guests the DNS server? If the *host* is a guest of
the DNS server on one of its kvm guests, then I think the answer is that
libvirt doesn't support that.
---
Ubuntu Bug Squad volunteer triager
@DaveWalker,
regarding comment #20, could you give a little more detail? which
proposed stanza should be reconsidered? I'll add it to the oneiric
package (for starters) but don't know which you mean :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
@Serge correct - for security (and portability) reasons, we've decided
to run ssh only and nothing else on the hosts - all other services run
on guests - so the host is using one of it's own guests as it's DNS
server. It's backup nameservers are on different hosts which are
usually up, so we
But what if your DNS servers, are also your guests?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/599342
Title:
Temporary failure in name resolution
To manage notifications about
I am sorry for the delay.
It looks like the grep from comment #13 will do the trick on standalone
systems.
Unfortunately we have moved away from KVM on our systems, so that I am
not able to test it right now.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Might stand to rephrase:
What if your DNS servers, are your guests?
And btw? Thanks for all you do.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/599342
Title:
Temporary
** Changed in: libvirt (Ubuntu Maverick)
Milestone: None = maverick-updates
** Tags removed: server-mrs
--
Temporary failure in name resolution
https://bugs.launchpad.net/bugs/599342
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Having discussed this issue with cjwatson, he suggested the proposed
stanza be reconsidered and done slightly differently - and postponed for
an SRU into Maverick.
Thanks
--
Temporary failure in name resolution
https://bugs.launchpad.net/bugs/599342
You received this bug notification because
Robert, Serge - was this ever confirmed? Do we have chance of getting
it in for 10.10 or is it likely to be a candidate for update?
--
Temporary failure in name resolution
https://bugs.launchpad.net/bugs/599342
You received this bug notification because you are a member of Ubuntu
Server Team,
Quoting Kate Stewart (599...@bugs.launchpad.net):
Robert, Serge - was this ever confirmed? Do we have chance of getting
it in for 10.10 or is it likely to be a candidate for update?
I'd like confirmation from Robert that the patch suffices for him.
The resulting package works on my system,
** Tags added: server-mrs
--
Temporary failure in name resolution
https://bugs.launchpad.net/bugs/599342
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
** Changed in: libvirt (Ubuntu Maverick)
Milestone: ubuntu-10.10-beta = None
--
Temporary failure in name resolution
https://bugs.launchpad.net/bugs/599342
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Robert,
can you confirm whether this fix works for you? We'll need confirmation of
that before the fix can be pushed to the package.
--
Temporary failure in name resolution
https://bugs.launchpad.net/bugs/599342
You received this bug notification because you are a member of Ubuntu
Server Team,
** Tags added: maverick
--
Temporary failure in name resolution
https://bugs.launchpad.net/bugs/599342
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
Note - it started fine in my own VMs. Waiting for confirmation from Robert
that this
works for him.
--
Temporary failure in name resolution
https://bugs.launchpad.net/bugs/599342
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt
Thanks, Scott.
Robert, what do you think about shortcutting your additional upstart
script if
grep '\$hostname\' /etc/hosts
returns 0? That should be save for both of us.
--
Temporary failure in name resolution
https://bugs.launchpad.net/bugs/599342
You received this bug notification
Debdiff of proposed package fix.
** Patch added: libvirt-host-upstart.debdiff
https://bugs.edge.launchpad.net/ubuntu/+source/libvirt/+bug/599342/+attachment/1500364/+files/libvirt-host-upstart.debdiff
--
Temporary failure in name resolution
https://bugs.launchpad.net/bugs/599342
You
I've posted this for testing to ppa:serge-hallyn/libvirt-host-upstart-fix.
Once it is
built Ill test it on my own vms. Assuming it works for both Robert and I, I'll
propose it for merge into maverick. IIUC it'll need to be fixed in maverick
before
we do an equivalent fix to SRU for lucid.
--
** Tags added: patch
--
Temporary failure in name resolution
https://bugs.launchpad.net/bugs/599342
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
We have removed the local hostname from /etc/hosts pointing to 127.0.1.1
or any other address in 127.0.0.0/8, we only keep 127.0.0.1 for
localhost in there. Every other name is resolved by our internal DNS.
The loop above just waits until the DNS answers and the hostname can be
resolved.
Robert:
Naturally you can use the recipe in comment #2 on your own systems. It's
just not safe to put in the package.
Jamie, since you've been packaging libvirt-bin (and since I'm looking for
a sanity check), do you see any problems with changing the upstart script
to the one I put in comment
Serge, I am not an upstart expert and highly recommend you get Scott to
check this. While it seems sane I think we'd need to test 'airplane
mode' for people trying to do work on their laptops and the network
isn't up (though I would think the 'network-manager' bit should cover
it).
--
Temporary
Hi Scott, would you mind taking a look at the proposed tweak
to /etc/init/libvirt-bin.conf? There is probably a better way...
Thanks!
--
Temporary failure in name resolution
https://bugs.launchpad.net/bugs/599342
You received this bug notification because you are a member of Ubuntu
Server
Reassigning to Scott, as you're asking for his input.
Scott, once you're done with this, please assign it back to Serge.
Thanks!
** Changed in: libvirt (Ubuntu Maverick)
Assignee: Serge Hallyn (serge-hallyn) = Scott James Remnant (scott)
--
Temporary failure in name resolution
I'm pretty sure mixing and/or like that will have disastrous
consequences (bug #447654) - please don't
** Changed in: libvirt (Ubuntu Maverick)
Assignee: Scott James Remnant (scott) = Serge Hallyn (serge-hallyn)
--
Temporary failure in name resolution
https://bugs.launchpad.net/bugs/599342
Is this actually happening because of dnsmasq or is there another issue
going on here? If its because of dnsmasq it might have to be converted
as well.
chuck
--
Temporary failure in name resolution
https://bugs.launchpad.net/bugs/599342
You received this bug notification because you are a
Nominated for maverick -- tentatively assigned to Serge, feel free to
reassign to Canonical Server team if needed.
** Changed in: libvirt (Ubuntu)
Importance: High = Medium
** Changed in: libvirt (Ubuntu)
Milestone: None = ubuntu-10.10-beta
** Changed in: libvirt (Ubuntu)
Assignee:
This scares me because on my laptop, where I do still have
127.0.1.1 vostro2
in my /etc/hosts, 'host vostro2' returns 1. So most stock ubuntu
installations would apparently wait forever to start libvirt-bin.
Does the following /etc/init/libvirt-bin.conf work for you?
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/51031539/Dependencies.txt
--
Temporary failure in name resolution
https://bugs.launchpad.net/bugs/599342
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in
After reading bug #595388 I have added the lines:
hostname=$(hostname)
until host $hostname
do
sleep 2s
done
to the pre-start section of libvirt-bin's upstart script. It works for
me.
--
Temporary failure in name resolution
** Changed in: libvirt (Ubuntu)
Importance: Undecided = High
** Changed in: libvirt (Ubuntu)
Status: New = Triaged
--
Temporary failure in name resolution
https://bugs.launchpad.net/bugs/599342
You received this bug notification because you are a member of Ubuntu
Server Team, which is
33 matches
Mail list logo
