Wrong project, meant to use puppet-neutron.
** Changed in: neutron (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560714
Title:
linuxbridge agent
Public bug reported:
When trying to setup linuxbridge with puppet-neutron, we see the following
error:
Error: Could not set 'present' on ensure: No such file or directory -
/etc/neutron/plugins/linuxbridge/linuxbridge_conf.ini at
Public bug reported:
When trying to setup linuxbridge with puppet-neutron, we see the following
error:
Error: Could not set 'present' on ensure: No such file or directory -
/etc/neutron/plugins/linuxbridge/linuxbridge_conf.ini at
Wrong project, meant to use puppet-neutron.
** Changed in: neutron (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1560714
Title:
linuxbridge
@Bobby
My workaround is applied to the image the instance is spawned with. You
must modify the image, upload that modified image and you will be able
to successfully boot VMs without this issue.
If you do not have access to do that, the only other way I would see
would be to spawn a VM using the
@Bobby
My workaround is applied to the image the instance is spawned with. You
must modify the image, upload that modified image and you will be able
to successfully boot VMs without this issue.
If you do not have access to do that, the only other way I would see
would be to spawn a VM using the
Lots of people asking for workarounds, I figured I would post mine - it
involves deleting the eth0 file from /etc/network/interfaces.d prior to
using the image. So it goes a bit like this:
# Install qemu-utils
apt-get install qemu-utils
# Mount the Ubuntu cloud image
modprobe nbd max_part=63
Lots of people asking for workarounds, I figured I would post mine - it
involves deleting the eth0 file from /etc/network/interfaces.d prior to
using the image. So it goes a bit like this:
# Install qemu-utils
apt-get install qemu-utils
# Mount the Ubuntu cloud image
modprobe nbd max_part=63
** Description changed:
In Ubuntu 12.04 with:
# dpkg -l |egrep pacemaker|corosync
ii corosync 1.4.2-2ubuntu0.2
Standards-based cluster framework (daemon and modules)
ii pacemaker1.1.6-2ubuntu3.3 HA
** Description changed:
In Ubuntu 12.04 with:
# dpkg -l |egrep pacemaker|corosync
ii corosync 1.4.2-2ubuntu0.2
Standards-based cluster framework (daemon and modules)
ii pacemaker1.1.6-2ubuntu3.3 HA
Public bug reported:
In Ubuntu 12.04 with:
# dpkg -l |egrep pacemaker|corosync
ii corosync 1.4.2-2ubuntu0.2
Standards-based cluster framework (daemon and modules)
ii pacemaker1.1.6-2ubuntu3.3 HA
cluster resource
Public bug reported:
In Ubuntu 12.04 with:
# dpkg -l |egrep pacemaker|corosync
ii corosync 1.4.2-2ubuntu0.2
Standards-based cluster framework (daemon and modules)
ii pacemaker1.1.6-2ubuntu3.3 HA
cluster resource
Public bug reported:
This bug was fixed upstream by Debian: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=651903
Essentially, service iptables-persistent save will always attempt to save
both ipv4 and ipv6 rules.
If ipv6 is disabled, aka:
- net.ipv6.conf.all.disable_ipv6 = 1
-
Public bug reported:
Lots of reference reading:
- http://serverfault.com/questions/625027/nagios-check-ntp-time-offset-unknown
- http://serverfault.com/questions/269701/nagios-ntp-discarding-peer
- http://sourceforge.net/p/nagiosplug/mailman/message/24582375/
Using this check on more than a
Public bug reported:
Lots of reference reading:
- http://serverfault.com/questions/625027/nagios-check-ntp-time-offset-unknown
- http://serverfault.com/questions/269701/nagios-ntp-discarding-peer
- http://sourceforge.net/p/nagiosplug/mailman/message/24582375/
Using this check on more than a
Public bug reported:
Using package versions:
ii python-swift1.13.1-0ubuntu1~cloud0
distributed virtual object store - Python libraries
ii python-swiftclient 1:2.0.3-0ubuntu1~cloud0 Client
library for Openstack Swift API.
ii swift
Scott / James:
What is the general process for the cloud archive ? Are the fixes
backported/cherry-picked from the current stable branch (trusty) once
they make it out of proposed ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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 swift in Ubuntu.
https://bugs.launchpad.net/bugs/1317147
Title:
Swift-proxy needs python-pecan =0.4.5, but
This is linked to another dependency problem in bug
https://bugs.launchpad.net/ubuntu/+source/swift/+bug/1317147.
** 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
See: https://ask.openstack.org/en/question/27951/pecan-version-for-
ceilometer-in-icehouse-swift-proxy/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1317147
Title:
Swift-proxy needs python-pecan
I'm also affected, using the cloud-archive repository for Icehouse on
Ubuntu precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1317147
Title:
Swift-proxy needs python-pecan =0.4.5, but 0.3.0
** 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/1317147
Title:
Swift-proxy needs python-pecan =0.4.5, but 0.3.0 is present
Once the pecan dependency is manually fixed, it also complains about
another incorrect version:
pkg_resources.VersionConflict: (happybase 0.7 (/usr/lib/python2.7/dist-
packages), Requirement.parse('happybase=0.5,!=0.7'))
This would need to be fixed as well.
--
You received this bug
This is linked to another dependency problem in bug
https://bugs.launchpad.net/ubuntu/+source/swift/+bug/1317147.
** 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
Oh, sorry for the spam. The happybase bug is reported in another bug:
https://bugs.launchpad.net/ubuntu/+source/swift/+bug/1317381
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1317147
Title:
Hi Scott,
You're correct, we use config drive in our implementation
(using_config_drive=True for nova-compute).
The template used by nova is located here:
https://github.com/openstack/nova/blob/master/nova/virt/interfaces.template
I also see your point that Nova could also implement a fix for
Adding the openstack nova bug for cross reference:
https://bugs.launchpad.net/nova/+bug/1319117
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1315501
Title:
cloud-init does not
Hi Scott,
You're correct, we use config drive in our implementation
(using_config_drive=True for nova-compute).
The template used by nova is located here:
https://github.com/openstack/nova/blob/master/nova/virt/interfaces.template
I also see your point that Nova could also implement a fix for
Adding the openstack nova bug for cross reference:
https://bugs.launchpad.net/nova/+bug/1319117
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315501
Title:
cloud-init does not use interfaces.d in
29 matches
Mail list logo
