** Changed in: cloud-archive
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to
** Changed in: cloud-archive
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to '/var/run/libvirt/libvirt-sock',
This bug was fixed in the package nova - 1:2013.2.2-0ubuntu1.1
---
nova (1:2013.2.2-0ubuntu1.1) saucy-proposed; urgency=low
[ Jian Wen ]
* d/nova-compute.upstart: If libvirt-bin is installed, then wait
for it to reach running state before starting nova-compute
(LP:
This bug was fixed in the package nova - 1:2013.2.2-0ubuntu1.1
---
nova (1:2013.2.2-0ubuntu1.1) saucy-proposed; urgency=low
[ Jian Wen ]
* d/nova-compute.upstart: If libvirt-bin is installed, then wait
for it to reach running state before starting nova-compute
(LP:
Tested with proposed; starting nova-compute always ensures that libvirt
is started first.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Tested with proposed; starting nova-compute always ensures that libvirt
is started first.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Paul, or anyone else affected,
Accepted nova into saucy-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/nova/1:2013.2.2-0ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Paul, or anyone else affected,
Accepted nova into saucy-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/nova/1:2013.2.2-0ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:~ubuntu-server-dev/nova/grizzly
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to
** Changed in: nova (Ubuntu Raring)
Status: In Progress = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to
** Branch linked: lp:~ubuntu-server-dev/nova/havana
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd
** Changed in: cloud-archive
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to '/var/run/libvirt/libvirt-sock',
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to '/var/run/libvirt/libvirt-sock',
** Branch linked: lp:~ubuntu-server-dev/nova/grizzly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd
may need to
** Branch linked: lp:~ubuntu-server-dev/nova/havana
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd
may need to
** Changed in: nova (Ubuntu Raring)
Status: In Progress = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to '/var/run/libvirt/libvirt-sock',
** Changed in: cloud-archive
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd
may
This bug was fixed in the package nova - 1:2014.1~b2-0ubuntu3
---
nova (1:2014.1~b2-0ubuntu3) trusty; urgency=medium
* debian/tests/nova-compute-daemons: Drop nova-compute-uml.
-- Chuck Short zul...@ubuntu.com Fri, 31 Jan 2014 14:40:23 -0500
** Changed in: nova (Ubuntu Trusty)
This bug was fixed in the package nova - 1:2014.1~b2-0ubuntu3
---
nova (1:2014.1~b2-0ubuntu3) trusty; urgency=medium
* debian/tests/nova-compute-daemons: Drop nova-compute-uml.
-- Chuck Short zul...@ubuntu.com Fri, 31 Jan 2014 14:40:23 -0500
** Changed in: nova (Ubuntu Trusty)
I have linked branches for an SRU for grizzly and horizon. Please review
when you get a chance. Thanks!
** Branch linked: lp:~arges/nova/fix-lp907152-grizzly
** Branch linked: lp:~arges/nova/fix-lp907152-havana
** Changed in: nova (Ubuntu Raring)
Status: Confirmed = In Progress
**
I have linked branches for an SRU for grizzly and horizon. Please review
when you get a chance. Thanks!
** Branch linked: lp:~arges/nova/fix-lp907152-grizzly
** Branch linked: lp:~arges/nova/fix-lp907152-havana
** Changed in: nova (Ubuntu Raring)
Status: Confirmed = In Progress
**
** Also affects: nova (Ubuntu Raring)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu Trusty)
Importance: Medium
Assignee: James Page (james-page)
Status: In Progress
--
** Changed in: nova (Ubuntu Trusty)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu Raring)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu Saucy)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Also affects: nova (Ubuntu Raring)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu Trusty)
Importance: Medium
Assignee: James Page (james-page)
Status: In Progress
--
** Changed in: nova (Ubuntu Trusty)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu Raring)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu Saucy)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
** Branch linked: lp:~ubuntu-server-dev/nova/icehouse
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to '/var/run/libvirt/libvirt-sock',
** Branch linked: lp:~ubuntu-server-dev/nova/icehouse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd
may need to
I have a way todo this now; I'll push in with the next set of icehouse
updates I do.
** Changed in: nova (Ubuntu)
Status: Triaged = In Progress
** Changed in: nova (Ubuntu)
Assignee: (unassigned) = James Page (james-page)
--
You received this bug notification because you are a
** Branch linked: lp:~james-page/nova/compute-plus-others
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to '/var/run/libvirt/libvirt-sock',
I have a way todo this now; I'll push in with the next set of icehouse
updates I do.
** Changed in: nova (Ubuntu)
Status: Triaged = In Progress
** Changed in: nova (Ubuntu)
Assignee: (unassigned) = James Page (james-page)
--
You received this bug notification because you are a
** Branch linked: lp:~james-page/nova/compute-plus-others
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd
may
** Tags added: canonistack
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd
may need to be started:
** Tags added: canonistack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd
may need to be started: No such file
I've been bitten by this bug too.
Please re-subscribe this team when you feel that you have a suitable
patch
Any hint about what would be the proper way of fixing it?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
I've been bitten by this bug too.
Please re-subscribe this team when you feel that you have a suitable
patch
Any hint about what would be the proper way of fixing it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Paul
Thanks for you work on this bug.
I understand what this bug is trying to resolve but the proposed patch
to the upstart configuration will break the nova-compute-xcp package
which provides nova-compute-hypervisor but does not depend on libvirt-
bin.
In this type of deployment a
Hi Paul
Thanks for you work on this bug.
I understand what this bug is trying to resolve but the proposed patch
to the upstart configuration will break the nova-compute-xcp package
which provides nova-compute-hypervisor but does not depend on libvirt-
bin.
In this type of deployment a
No, I believe we need to keep it. Since nova is not explicitly
dependent on libvirt.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to
Debdiff attached
** Patch added: nova_2012.1~e4.diff
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/907152/+attachment/2830495/+files/nova_2012.1%7Ee4.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
v2: Based on SpamapS comments from #ubuntu-server
** Patch added: nova_2012.1~e4.v2.diff
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/907152/+attachment/2830587/+files/nova_2012.1%7Ee4.v2.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
No, I believe we need to keep it. Since nova is not explicitly
dependent on libvirt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to
Debdiff attached
** Patch added: nova_2012.1~e4.diff
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/907152/+attachment/2830495/+files/nova_2012.1%7Ee4.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
v2: Based on SpamapS comments from #ubuntu-server
** Patch added: nova_2012.1~e4.v2.diff
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/907152/+attachment/2830587/+files/nova_2012.1%7Ee4.v2.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
(setting to confirmed as the race certainly is possible based on the
'start on's)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to
If the upstart job is going to wait on libvirt-bin to start anyway, can
the other two conditions not be dropped as they are implied by libvirt-
bin (which itself waits on runlevel 2)?
** Changed in: nova (Ubuntu)
Status: New = Triaged
** Changed in: nova (Ubuntu)
Importance: Undecided
(setting to confirmed as the race certainly is possible based on the
'start on's)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable to connect to
If the upstart job is going to wait on libvirt-bin to start anyway, can
the other two conditions not be dropped as they are implied by libvirt-
bin (which itself waits on runlevel 2)?
** Changed in: nova (Ubuntu)
Status: New = Triaged
** Changed in: nova (Ubuntu)
Importance: Undecided
This is actually an Ubuntu packaging issue.
** Project changed: nova = ubuntu
** Package changed: ubuntu = nova (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
The attachment nova-compute.upstart.diff of this bug report has been
identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the tag
This is actually an Ubuntu packaging issue.
** Project changed: nova = ubuntu
** Package changed: ubuntu = nova (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907152
Title:
Error: unable
The attachment nova-compute.upstart.diff of this bug report has been
identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the tag
56 matches
Mail list logo
