Public bug reported:
Similar to the EC2 instance ID issue in Bug #1061166, the
snapshot_id_mappings and volume_id_mappings tables were both introduced
in Folsom but are not populated entirely during creation, with the
deleted column ending up NULL for all rows copied during the initial
migration.
** Tags added: openstack-ubuntu-upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access existing volumes.
To manage notifications a
** Tags added: openstack-ubuntu-upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065320
Title:
/var/lib/nova/volumes is owned by root after Folsom upgrade
To manage notifications about this b
I've been unable to reproduce this using a simple test:
# apt-get install openvswitch-switch quantum-l3-agent
# service quantum-l3-agent status
quantum-l3-agent stop/waiting # <- this is expected, currently.
# ovs-vsctl add-br br-int
# ovs-vsctl add-br br-ex
# ip addr
3: br-int: mtu 1500 qdisc n
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1035172
Title:
DHCP broken for Openstack Nova instances since kernel v3.3
To manage notifications about this bug go to:
Public bug reported:
In the last upload to Ubuntu, debian/novnc.init was strangely dropped
from the package with no indication in changelog as to why. It exists
in Debian, and users are apparently still expecting it be there.
** Affects: novnc (Ubuntu)
Importance: Undecided
Status
Quantum server should be loading plugin specific config, as configured
in /etc/default/quantum-server (OVS plugin by default). I'm a bit
confused what the bug is here. How do I reproduce?
ubuntu@juju-james-instance-0:~$ ls /var/lib/quantum/
ovs.sqlite
ubuntu@juju-james-instance-0:~$ sudo rm -rf
Public bug reported:
The quantum-server upstart job attempts to add an additional '--config-
file=' argument to quantum-server if a plugin config is present
(specified in /etc/default/quantum-server, defaults to openvswitch
plugin).
When instaling quamtum-server and quantum-plugin-openvswitch tog
WRT Ubuntu update, this needs to be fixed upstream before it can be
applied as a match to the Ubuntu package in Quantal and Cloud Archive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064835
Title:
Hi Justin, thanks for the bug. It looks like the dependency between
keystone and python-keystone is explicit in that it requires the same
version, so those should be upgraded together. The python-
keystoneclient dependency is loosely defined, for sure. Can you confirm
that this is the case?
Al
Finished bisecting over the weekend. It concluded that
7c7c7f01cc5e3e423120a4848a73dd5e4586f2f9 is the first bad commit. The
following is a summary of the bisect against linux-stable:
git bisect start
git bisect good v3.2
git bisect bad v3.3-rc1
2ac9d7aaccbd598b5bd19ac40761b723bb675442 - good
a
It looks like this is related to the discussion of vhost_net, packet
checksumming and DHCP @ http://www.spinics.net/lists/kvm/msg37660.html
and recent changes to libvirt that enable 'vhost=on' by default for KVM
processes (vhost=on does not get set by default on precise)
Using iptables on the host
Tagging this as affecting nova, as it manages its own out-of-band bridge
and iptables rules for its libvirt guests. These rules should probably
be setup by nova-network (and potentially quantum?)
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notifica
*** This bug is a duplicate of bug 1029430 ***
https://bugs.launchpad.net/bugs/1029430
** This bug has been marked a duplicate of bug 1029430
KVM guests networking issues with no virbr0 and with vhost_net kernel
modules loaded
--
You received this bug notification because you are a membe
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nova (Ubuntu)
Status: New => Confirmed
** Changed in: nova (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Tags added: folsom-rc-potential
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029430
Title:
KVM guests networking issues with no virbr0 and with vhost_net kernel
modules loaded
To manage noti
** Branch linked: lp:~gandelman-a/ubuntu/quantal/openvswitch/1.4.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057098
Title:
[FFe] Please update to 1.4.3
To manage notifications about this bug g
Public bug reported:
Installing nova-novncproxy 2012.2-0ubuntu2:
$ sudo apt-get install nova-novncproxy
$ service nova-novncproxy status
nova-novncproxy: unrecognized service
$ which nova-novncproxy
In addition to this affecting Nova, the novnc package's init scripts
requires the presence of /us
Public bug reported:
The websockify's only purpose ATM is to serve as a dependency of nova's
VNC services, specifically nova-novncproxy, however, it does not
currently install any python module and the nova service fails to start
because of an ImportError.
# apt-get -y install websockify ; python
Looks like the upstream source tree's use of setuptools is broken?
Neither websockify.py (which is a symlink to websockify binary in the
source tree) or websocket.py end up in /usr/share/ after running
setup.py.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
arget
2012-10-02 15:23:07 TRACE nova raise exception.NotFound()
2012-10-02 15:23:07 TRACE nova NotFound: Resource could not be found.
2012-10-02 15:23:07 TRACE nova
** Affects: nova (Ubuntu)
Importance: Undecided
Assignee: Adam Gandelman (gandelman-a)
Status: In Pro
Public bug reported:
After upgrading a running cluster from Essex to Folsom
(2012.2-0ubuntu2~cloud0), the EC2 API can no longer find instances by
EC2 ID, ie:
ubuntu@ip-10-252-38-15:~$ euca-describe-instances
RESERVATION r-90qer9xs 7b58c0e219a948ef942071c871d05b8bdefault
INSTANCE
The theme has been re-enabled in our packaging, but the actual CSS and
media needs to be refreshed and updated to apply correctly over the
current version of the django app.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
After taking another look at this, EC2 instance IDs appear to change
during an upgrade.
Did an upgrade with two running instances, i-0003 and i-0004.
After upgrade, they show change to i-0003 and i-0004,
respecively. Any EC2 action (terminate, get-console-output, etc) on
these n
Oops: should have read that instances i-0003 and i-0004 changed
post-upgrade to i-0005 and i-0006
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1061166
Title:
ec2 instance IDs are
>From what I can gather the 107 migration only copies the instance's ID
and UUID to the new mapping table, but leaves the other columns NULL,
specifically 'deleted'.
In Folsom, an ec2 describe instances call will check that the
instances.id <-> uuid mapping exists in the instances_id_mapping table
t, referer:
http://ec2-50-112-7-145.us-
west-2.compute.amazonaws.com/dashboard/auth/login/
** Affects: horizon (Ubuntu)
Importance: Undecided
Assignee: Adam Gandelman (gandelman-a)
Status: In Progress
** Tags: openstack-ubuntu-upgrade
** Tags added: openstack-ubuntu-upgrade
**
Public bug reported:
Developers from OpenVswitch have requested we update to the current
stable release, 1.4.3. This version is a bug-fix only release for the
1.4 branch that contains the following changes:
8249ccc Declare the version as "1.4.3".
02978b5 datapath: Fix FLOW_BUFSIZE definition.
6
Public bug reported:
089_add_volume_id_mappings.py
107_add_instance_id_mappings.py
These two migrations create tables that easily map volume and instance
IDs to UUIDs. Each have 6 columns: id, uuid, created_at, updated_at,
deleted_at, deleted. Only the 'id' and 'uuid' column get populated with
Jon-
Unfortunately if you've hit this bug, your instance_id_mappings table is
already polluted with duplicate entries and the mapping between EC2 IDs
and UUIDs is skewed.Someone may know a better work around, but in
the meantime I'd take a look at the instance_id_mappings table and clean
it of
Public bug reported:
The panel of the Settings dashboard that allows geneartion of a Juju
environments config is missing from the Current horizon package. The
patch is still included in the packaging, but has not been refreshed and
re-enabled against the Folsom release of Openstack.
There have b
Public bug reported:
The SysV init script shipped with the novnc script attempts to start
nova-novncproxy (provided as part of the nova source package), but there
is no dependency on nova-novncproxy.
Attempting to start the service with 'set -x' shows:
ubuntu@server-650:~$ sudo service novnc sta
Public bug reported:
Using the latest quantal mini.iso, ethdetect fails during preseeded net
installs. Kernel log shows:
bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw"
Since kernel 3.3, bnx2 driver apparently requires a new firmware file
which was committed to linux-firmware at
Martijn-
This is the expected behavior of the ec2 fact that ships with facter.
If it can connect to a webserver at http://169.254.169.254:80 (the
expected location of the meta-data server on Amazon EC2), it will
attempt to traverse the directory structure and populate facts with bits
of meta-data
*** This bug is a duplicate of bug 990759 ***
https://bugs.launchpad.net/bugs/990759
** This bug has been marked a duplicate of bug 990759
package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
--
You received
Unpacking replacement postfix ...
Preparing to replace libsasl2-modules 2.1.23.dfsg1-5ubuntu1 (using
.../libsasl2-modules_2.1.25.dfsg1-3_amd64.deb) ...
Unpacking replacement libsasl2-modules ...
Preparing to replace libsasl2-2 2.1.23.dfsg1-5ubuntu1 (using
.../libsasl2-2_2.1.25.dfsg1-3_amd64.deb)
Unpacking replacement postfix ...
Preparing to replace libsasl2-modules 2.1.23.dfsg1-5ubuntu1 (using
.../libsasl2-modules_2.1.25.dfsg1-3_amd64.deb) ...
Unpacking replacement libsasl2-modules ...
Preparing to replace libsasl2-2 2.1.23.dfsg1-5ubuntu1 (using
.../libsasl2-2_2.1.25.dfsg1-3_amd64.deb)
Hi Chris-
Thanks for reporting this and helping make Ubuntu better. Can you
confirm whether or not this report is from the same system as that
described in Bug #990751 ? That is, was this generated from a
subsequent attempt at repairing or working around the other previously
reported bug? Thank
Installing new version of config file /etc/ldap/schema/README ...
Installing new version of config file /etc/ldap/schema/openldap.ldif ...
Installing new version of config file /etc/ldap/schema/cosine.ldif ...
Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.4.25-1.1ubuntu4.1...
done.
Movi
*** This bug is a duplicate of bug 990742 ***
https://bugs.launchpad.net/bugs/990742
** This bug has been marked a duplicate of bug 990742
does not depend on libsasl2-2 (>= 2.1.24)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
*** This bug is a duplicate of bug 990742 ***
https://bugs.launchpad.net/bugs/990742
** This bug has been marked a duplicate of bug 990742
does not depend on libsasl2-2 (>= 2.1.24)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Changed in: openldap (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/990742
Title:
does not depend on libsasl2-2 (>= 2.1.24)
To manage notifications about
*** This bug is a duplicate of bug 990742 ***
https://bugs.launchpad.net/bugs/990742
Unpacking replacement libsasl2-2 ...
Preparing to replace ldap-utils 2.4.21-0ubuntu5.7 (using
.../ldap-utils_2.4.28-1.1ubuntu3_amd64.deb) ...
Unpacking replacement ldap-utils ...
Preparing to replace slapd 2.
Note, the fix for this in Debian came by setting 'Breaks: slapd <
2.4.25-4' on libsasl2-2 in the cyrus-sasl package.
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=163;filename=cyrus-
sasl2_2.1.25.dfsg1-3.1.debdiff;att=1;bug=628237
--
You received this bug notification because you are a membe
** Summary changed:
- does not depend on libsasl2-2 (>= 2.1.24)
+ slapd fails to upgrade: requires libsasl2-2 (>= 2.1.24) installed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/990742
Title:
slapd
** Also affects: cyrus-sasl2 (Ubuntu)
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/990742
Title:
slapd fails to upgrade: requires libsasl2-2 (>= 2.1.24)
This has been fixed in Debian and Quantal in the most recent sync of
cyrus-sasl2 (2.1.25.dfsg1-4)
** Changed in: openldap (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Changed in: keystone (Ubuntu)
Status: Triaged => In Progress
** Changed in: keystone (Ubuntu)
Assignee: (unassigned) => Adam Gandelman (gandelman-a)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Committed to our CI packaging branch, will be fixed in Ubuntu on the
next keystone upload.
** Changed in: keystone (Ubuntu)
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.launc
I'm happy to re-test the new package in proposed, but I've been watching
http://archive.ubuntu.com/ubuntu/dists/precise-
proposed/main/binary-i386/Packages.gz since it was accepted and the
latest kernel I find is 3.2.0.29.31, not 3.2.0-29.46. Am I looking in
the wrong place? Do proposed kernel up
I can confirm that the package in -proposed fixes my issue. I can
saturate my connection for prolonged periods, and the only msg related
to the asix driver that hits my kernel log is from the module's
initialization.
** Tags removed: verification-needed-precise
** Tags added: verification-done-pre
Attached is a new debdiff with the full change history applied. Built
successfully on ARM and PPC, as well as built and tested on amd64.
Please accept into -proposed. Thanks.
** Patch added: "lp973741-2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/s3cmd/+bug/973741/+attachment/3246392/+
Please find the attached test log from the Ubuntu Server Team's CI
infrastructure. As part of the verification process for this bug, the
OpenStack components have been deployed and configured across multiple
nodes using precise-proposed as an installation source. After successful
bring-up and confi
** Attachment added: "1041120_verification.log"
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1041120/+attachment/3286614/+files/1041120_verification.log
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member
That kernel is good and not affected by the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1035172
Title:
DHCP broken for Openstack Nova instances since kernel v3.3
To manage notifications ab
Having trouble reproducing using the following steps with stable/essex
on Ubuntu 12.04 (via 2012.1.3+stable-20120827-4d2a4afe-0ubuntu1
package):
nova floating-ip-create
nova add-floating-ip b8e0295d-e515-4838-b91a-eb3c4b1beebe 192.168.25.237
nova delete b8e0295d-e515-4838-b91a-eb3c4b1beebe
nova fl
Marking 'Fix Released' . The uploads of python-glanceclient
(1:0.4.1-0ubuntu1) and glance (2012.2~f3-0ubuntu1) included changes that
describe the conflicting relationship between glance-client and python-
glanceclient. Only one client package may be installed.
** Changed in: python-glanceclient
** Summary changed:
- django_compressor is required for access to the dashboard
+ node.js is required for access to the dashboard
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024326
Title:
node.j
This one is good, too. Thanks Joseph.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1035172
Title:
DHCP broken for Openstack Nova instances since kernel v3.3
To manage notifications about this bug
Hey Sam-
Thanks for the patch. I've merged the change into our -proposed
packaging branches, where the change will be incorporated into our CI
builds (available in ppa:openstack-ubuntu-testing/folsom-trunk-testing)
and be merged to ~ubuntu-server-dev branch (and Ubuntu archive) with the
next uplo
Andrew-
Can't seem to reproduce this locally. Its a long shot, but I wonder if
this might be related to the same problems reported in Bug #1006898. Are
there multiple instances of dnsmasq running? I know you're not
configured for VLANing, but I'm interested to know if the proposed fix
there solv
Hey Eugene-
I'm not sure where you and the other guy got a more up-to-date version
of lockfile. python-lockfile has remained at 0.8 in Ubuntu since the
package was introduced in Lucid. That said, AFACIS I'm not sure any of
this is lockfile related as nova.utils.GreenLockFile overrides
lockfile
Public bug reported:
When configured to use FlatDHCPManager in multi-host, Openstack Nova
(Folsom version) instances no longer get their IP address via DHCP from
the server running local on the compute node.
For those who are not familiar with Openstack configurations, the
compute nodes' VMs com
Joseph- I'm unable to get my host in working order for testing using
that kernel as the initrd does not contain the required firmware for my
NIC (bnx2) Is that expected to exist like it has for the other upstream
kernels I've tested, or is there something I must do after installing
the debs to rep
Joseph- Yes, I've installed both. I was warned of possible missing
firmware at package installation and sure enough at boot:
bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw"
I've run into similar issues with quantal kernels in the past, see bug
#1008749
--
You received this bug no
Thanks, Byron. I've stuffed a newer version of python-prettytable into
the Precise pocket of the PPA as well as updated the packaging
dependencies to reflect the upstream version requirement.
** Changed in: python-novaclient (Ubuntu)
Status: New => Fix Committed
--
You received this bug
Thanks Byron, I've included glance-api.conf in the sql_conn.patch to
also set the path there. New packages building in PPA, should be fixed
in Quantal with the next upload.
** Changed in: glance (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a
** Changed in: nova (Ubuntu)
Status: New => In Progress
** Changed in: nova (Ubuntu)
Assignee: (unassigned) => Adam Gandelman (gandelman-a)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
FYI-
According to flags.py, the metadata endpoint is enabled by default:
cfg.ListOpt('enabled_apis',
default=['ec2', 'osapi_compute', 'osapi_volume', 'metadata'],
help='a list of APIs to enable by default'),
So, on the packaging side we need to ship the filter
** Changed in: ubuntu
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1018586
Title:
cleanup_file_locks does not remove stale sentinel files
To manage notifications a
** Tags added: essex-backport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1018586
Title:
cleanup_file_locks does not remove stale sentinel files
To manage notifications about this bug go to:
http
Attached is a debdiff against openssl 1.0.1-4ubuntu5.3 with the
upstream fix applied.
** Patch added: "lp973741.debdiff"
https://bugs.launchpad.net/ubuntu/+source/s3cmd/+bug/973741/+attachment/3236667/+files/lp973741.debdiff
** Summary changed:
- s3cmd: segmentation fault for all https ope
** Description changed:
+ [IMPACT]
+
+ https operations that make use of openssl/libcrypto on specific legacy
+ Intel CPUs results in SIGSEGV. This includes everything from utilities
+ like wget and curl, to mail servers and everything in between.
+
+ [TESTCASE]
+
+ curl or wget a URL via the
@Aaron,
I believe there is a PPC build failure that is blocking it. Do the failures
in the build log look like anything obvious to you?
https://launchpadlibrarian.net/75199/buildlog_ubuntu-precise-
powerpc.openvswitch_1.4.0-1ubuntu1.1_FAILEDTOBUILD.txt.gz
--
You received this bug notifi
** Changed in: sqlalchemy (Ubuntu Quantal)
Status: In Progress => Fix Released
** Changed in: sqlalchemy (Ubuntu Precise)
Importance: Undecided => High
** Changed in: sqlalchemy (Ubuntu Precise)
Status: Fix Released => In Progress
--
You received this bug notification because y
Aaron, the package posted earlier was built on a PPA, which only targets
i386 and amd64. I've just tested Ben's patch against PPC and proposed a
new upload to precise-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Public bug reported:
On 12.04, python-greenlet-dbg apparently does not include the debug
symbols:
ubuntu@server-4821~$ sudo apt-get -y install python2.7-dbg python-greenlet
python-greenlet-dbg
ubuntu@server-481:~$ python2.7 -c 'import greenlet'
ubuntu@server-481:~$ python2.7-dbg -c 'import green
Having a tough time reproducing this.. I've tried on multiple version
releases of 12.10, multiple architectures and tried with using the main
archive (instead of PPA) to resolve dependencies with older library
versions. In all cases, both servers stay up as expected. Any chance
you can debug futh
Kurt-
Thanks for the report. From the looks of it, nova is having problems import
the webob.exc module in the postinst. This is strange, as python-webob is a
dependency of python-nova, both of which are installed according the logs. I'm
curious--apport is reporting this is a fresh installati
Public bug reported:
root@server-570:/etc/quantum# apt-get remove --purge quantum-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
quantum-server*
0 upgraded, 0 newly installed, 1 to remove and 154 not
Sorry clint, the bug actually affects the Openstack Ubuntu Testing PPA.
I wish there was a better way to target packages in that PPA and not the
Ubuntu package, tho those packages are where the Ubuntu packages are
derived.
Anyway, the issue is the use of update-rc.d in the postrm's is bad, and
do
** Description changed:
Note: OVS from before 1.5, which includes the default versions shipped
with 12.04 and Fedora 17, has a bug that causes it not to work correctly
with floating IPs when the person contacting the floating IP is on the
same box as quantum-l3-agent.
While not very l
** Changed in: openvswitch (Ubuntu Precise)
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/1044318
Title:
[SRU] pre-1.5 OVS has trouble with floating ips when pinging
Reopening as last upload does not fix these issues.
** Changed in: quantum (Ubuntu Quantal)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1045064
Title:
Imp
** Changed in: quantum
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/1048668
Title:
OVS Agent Packaging Issue
To manage notifications about this bug go to:
https://bug
As discussed with Emilien on IRC, seems to be an issue connecting to the
OVS socket when executing via quantum-rootwrap:
http://paste.openstack.org/show/nxrauk9Pje5zTYhZGcNu/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Branch unlinked: lp:~gandelman-a/ubuntu/quantal/horizon/1024326
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024326
Title:
node.js is required for access to the dashboard
To manage notificatio
Public bug reported:
ubuntu@server-509:~$ sudo apt-get install python-compressor
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using
on (Ubuntu)
Status: New => Confirmed
** Changed in: horizon (Ubuntu)
Assignee: (unassigned) => Adam Gandelman (gandelman-a)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036571
Title:
Still trying to figure out how best to handle the lessc dependency. But
in the meantime, I've updated the package in the PPA to include the new
dependency and the relevant symlinking that you've described. There
should be packages in the PPA soon that reflect these changes. However,
I'm still ge
Public bug reported:
Moving the root of the WSGI app from / to /horizon with a simple
mod_wsgi config: http://paste.ubuntu.com/1149774/
The dashboard generally works okay, but the authentication actions
(login and logout) end up redirecting to pages relevant to /, not
/horizon.
Ie, logging in vi
On 08/20/2012 11:49 PM, Aimon Bustardo wrote:
> What is the timeframe for getting this released to main ubuntu repo? or
> at least in a stable ppa?
>
The stable PPA should contain the fix, its built directly from
stable/essex branch. Dont use those for production tho, its a testing PPA.
We're p
** Changed in: openvswitch (Ubuntu Precise)
Milestone: ubuntu-12.04.1 => precise-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021530
Title:
[SRU] update to include stable fixes for OVS
Is there an ETA on when this will hit precise-proposed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025544
Title:
[SRU] schema changes using sqlalchemy's sqlite dialect can fail when
using refl
Public bug reported:
This is a meta-bug used for tracking progress of new updates to Nova,
Horizon, Keystone, and Glance.
glance 2012.1.3+stable~20120821-120fcf-0ubuntu1
- Glance add uploads a double image if using ssl and images is smaller
than 4k. (LP: #1007093)
- If response.envi
Opening again. The fix for bug #1020313 changes the default config and
moves the applications root to /horizon (instead of /). The rest of the
config needs updating so that redirects function properly with the new
change.
** Changed in: horizon (Ubuntu)
Status: Invalid => Confirmed
--
Y
Public bug reported:
root@server-534:/home/ubuntu# apt-get install python-quantumclient
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily
unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another
process using it?
root@server-534:/home/ubunt
Joseph, thanks and sorry I've been slow to respond. I'd be happy to
assist with a bisect, in fact I already attempted to do this myself but
I seemed to have hit some problems along the way when selecting proper
starting and endpoints for the bisect, or using the wrong tree. I've
even got a decent
Now tracking nova - 2012.1.3+stable-20120827-4d2a4afe-0ubuntu1, which
supersedes the original upload into precise-proposed and should fix the
FTBFS.
** Description changed:
This is a meta-bug used for tracking progress of new updates to Nova,
Horizon, Keystone, and Glance.
glance 2012.1.
These were fixed upstream (or removed) and fixed in Ubuntu as of the F3
upload.
** Changed in: quantum (Ubuntu)
Status: Triaged => 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/102
301 - 400 of 1180 matches
Mail list logo
