Public bug reported:
Hi, I am the author of pngtools. After prompting from Arch Linux, I've
recovered the source code for pngtools from a backup and placed it on
github at https://github.com/mikalstill/pngtools.
I'd be happy enough to accept patches and bug reports there, and will do
my best to
Public bug reported:
Hi, my Dell XPS 7390 worked just fine with Ubuntu 19.10, but after
clean-install upgrading to 20.04 I don't have working bluetooth any
more. The machine has an Intel AX200 installed. I'm not sure what
details are helpful to provide, so here are some random things, happy to
Your fix looks reasonable to me, but we'd need a test as well I think.
I've tagged this as being of possible backport interest to mitaka as
well.
** Changed in: nova (Ubuntu)
Status: New => Confirmed
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
I am experiencing this problem as well. Any news on your testing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1209092
Title:
network : gnome-control-center crashed with SIGABRT in
** Tags added: 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/1026621
Title:
nova-network gets release_fixed_ip events from someplace, but the
database still keeps them
Hi! There seem to be two issues here in the one bug -- DHCP refreshes
are causing problems, and pain with windows instances because of how
they handle timezones and that causing extra DHCP refreshes. I'll
talk about each of those separately.
Windows timezones
=
I'm sorry to hear
The bug for the windows timezone issues is 1231254.
--
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/1026621
Title:
nova-network gets release_fixed_ip events from someplace, but the
** Tags added: libvirt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026621
Title:
nova-network gets release_fixed_ip events from someplace, but the
database still keeps them associated with
The bug for the windows timezone issues is 1231254.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026621
Title:
nova-network gets release_fixed_ip events from someplace, but the
database still
Hi! There seem to be two issues here in the one bug -- DHCP refreshes
are causing problems, and pain with windows instances because of how
they handle timezones and that causing extra DHCP refreshes. I'll
talk about each of those separately.
Windows timezones
=
I'm sorry to hear
** Changed in: nova
Status: In Progress = Triaged
** Changed in: nova
Assignee: Michael Still (mikalstill) = (unassigned)
--
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
** Changed in: nova
Assignee: Michael Still (mikalstill) = (unassigned)
** Changed in: nova
Status: In Progress = Triaged
--
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
** Changed in: nova
Status: In Progress = Triaged
** Changed in: nova
Assignee: Michael Still (mikalstill) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832507
Title
** Changed in: nova
Assignee: Michael Still (mikalstill) = (unassigned)
** Changed in: nova
Status: In Progress = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832507
Title
Does the console log file exist at all?
** Summary changed:
- empty console log output with grizzley on centOS distribution
+ empty console log output with grizzly on centOS distribution
** Changed in: nova
Status: New = Incomplete
--
You received this bug notification because you are
Does the console log file exist at all?
** Summary changed:
- empty console log output with grizzley on centOS distribution
+ empty console log output with grizzly on centOS distribution
** Changed in: nova
Status: New = Incomplete
--
You received this bug notification because you are
** Changed in: nova
Assignee: (unassigned) = Michael Still (mikalstill)
--
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/832507
Title:
console.log grows indefinitely
To manage
** Changed in: nova
Assignee: (unassigned) = Michael Still (mikalstill)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832507
Title:
console.log grows indefinitely
To manage notifications
** Changed in: nova
Status: New = Confirmed
** Changed in: nova
Importance: Undecided = Critical
--
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/1182624
Title:
Uncached
** Changed in: nova
Status: New = Confirmed
** Changed in: nova
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182624
Title:
Uncached instance builds
@Matthew -- are you still working on this one?
--
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/1155458
Title:
500 response when trying to create a server from a deleted image
To
@Matthew -- are you still working on this one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1155458
Title:
500 response when trying to create a server from a deleted image
To manage notifications
@Adam -- can we therefore remove the upstream tasks from this bug?
--
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/1158563
Title:
After grizzly upgrade, EC2 API requests fail:Could not
@Adam -- can we therefore remove the upstream tasks from this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1158563
Title:
After grizzly upgrade, EC2 API requests fail:Could not find:
** Tags added: ec2
--
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/1158563
Title:
After grizzly upgrade, EC2 API requests fail:Could not find:
credential
To manage notifications
** Tags added: ec2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1158563
Title:
After grizzly upgrade, EC2 API requests fail:Could not find:
credential
To manage notifications about this bug go
** Changed in: nova
Assignee: (unassigned) = Matthew Sherborne (msherborne+openstack)
** Changed in: nova
Status: New = Triaged
** Changed in: nova
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: nova
Assignee: (unassigned) = Matthew Sherborne (msherborne+openstack)
** Changed in: nova
Status: New = Triaged
** Changed in: nova
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
nova-volumes is gone now, so this is just a cinder bug.
** No longer affects: nova
--
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/1028718
Title:
nova volumes are inappropriately
Closing from lack of activity.
** Changed in: nova
Status: Confirmed = Won't Fix
** Changed in: nova
Importance: Low = Undecided
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
nova-volumes is gone now, so this is just a cinder bug.
** No longer affects: nova
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1028718
Title:
nova volumes are inappropriately clingy for ceph and
Closing from lack of activity.
** Changed in: nova
Status: Confirmed = Won't Fix
** Changed in: nova
Importance: Low = Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/833519
Yes, if there are more device files than that they will now be used as
well.
--
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/861504
Title:
nova-compute-lxc limited by available nbd
Yes, if there are more device files than that they will now be used as
well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/861504
Title:
nova-compute-lxc limited by available nbd devices to 16
It certainly seems like we should only send the last N lines of the
console to the user (although that might be computationally expensive to
generate on such a large file). That's a separate bug though I suspect.
I've filed bug 1081436 for that.
--
You received this bug notification because you
It certainly seems like we should only send the last N lines of the
console to the user (although that might be computationally expensive to
generate on such a large file). That's a separate bug though I suspect.
I've filed bug 1081436 for that.
--
You received this bug notification because you
What release was this canonistack region running at the time the problem
was seen?
** Changed in: nova
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
What release was this canonistack region running at the time the problem
was seen?
** Changed in: nova
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000710
Title:
** Changed in: python-keystoneclient
Importance: Undecided = Critical
** Changed in: python-keystoneclient (Ubuntu)
Importance: Undecided = Critical
** Changed in: python-keystoneclient (Ubuntu Quantal)
Importance: Undecided = Critical
--
You received this bug notification because you
** Project changed: nova = open-iscsi (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1072597
Title:
open-iscsi has a bug with ubuntu
To manage notifications about this bug go to:
** Changed in: nova
Importance: Undecided = High
** Changed in: nova/essex
Importance: Undecided = High
** Changed in: nova/essex
Importance: High = Medium
** Changed in: nova/folsom
Importance: Undecided = High
--
You received this bug notification because you are a member of
** Changed in: nova
Importance: Undecided = High
** Changed in: nova/essex
Importance: Undecided = High
** Changed in: nova/essex
Importance: High = Medium
** Changed in: nova/folsom
Importance: Undecided = High
--
You received this bug notification because you are a member of
Upstream has chosen not to backport this fix to essex. Can we please
consider carrying this patch ourselves?
--
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/1062314
Title:
Upstream has chosen not to backport this fix to essex. Can we please
consider carrying this patch ourselves?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1062314
Title:
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Assignee: (unassigned) = Michael Still (mikalstill)
--
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
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Assignee: (unassigned) = Michael Still (mikalstill)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1062314
Public bug reported:
This is a bug against stable essex. I have made no attempt to determine
if this is still a problem in Folsom at this stage.
During a sprint this week we took a nova region which was previously
relatively idle and started turning up large numbers of instances using
juju. We
I think the issue here is that nova.virt.firewall.py
IptablesFirewallDriver.instance_rules() is calling
get_instance_nw_info() which is causing rpcs to be fired off
_while_still_holding_the_iptables_lock. I suspect that the rpcs need to
happen outside the lock.
From yet more instrumented code:
A
Public bug reported:
This is a bug against stable essex. I have made no attempt to determine
if this is still a problem in Folsom at this stage.
During a sprint this week we took a nova region which was previously
relatively idle and started turning up large numbers of instances using
juju. We
I think the issue here is that nova.virt.firewall.py
IptablesFirewallDriver.instance_rules() is calling
get_instance_nw_info() which is causing rpcs to be fired off
_while_still_holding_the_iptables_lock. I suspect that the rpcs need to
happen outside the lock.
From yet more instrumented code:
A
** Tags added: ops
--
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/1059899
Title:
nova fails to configure dnsmasq, resulting in DNS timeouts in
instances
To manage notifications
** Tags added: ops
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059899
Title:
nova fails to configure dnsmasq, resulting in DNS timeouts in
instances
To manage notifications about this bug go
Another option would be to create a vhost for the dashboard.
** Tags added: canonistack
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1020313
Title:
openstack-dashboard hijacks
Public bug reported:
I have to regions configured in /etc/openstack-
dashboard/local_settings.py. If I switch between them in the drop down
at the top right of the screen, a login dialog appears at the bottom of
the page which is quite confusing. Some thoughts:
- credentials from the previous
** Attachment added: login-bug.png
https://bugs.launchpad.net/bugs/1036918/+attachment/3261487/+files/login-bug.png
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1036918
Title:
Public bug reported:
Hi. We have two regions configured in /etc/openstack-
dashboard/local_settings.py.
A user changed regions with the drop down, logged into the new region,
and started an instance. The instance started in the _previous_ region.
I'm not sure what debugging information to
Another option would be to create a vhost for the dashboard.
** 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/1020313
Title:
openstack-dashboard hijacks the web root
To
Public bug reported:
I have to regions configured in /etc/openstack-
dashboard/local_settings.py. If I switch between them in the drop down
at the top right of the screen, a login dialog appears at the bottom of
the page which is quite confusing. Some thoughts:
- credentials from the previous
** Attachment added: login-bug.png
https://bugs.launchpad.net/bugs/1036918/+attachment/3261487/+files/login-bug.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1036918
Title:
Switching
Public bug reported:
Hi. We have two regions configured in /etc/openstack-
dashboard/local_settings.py.
A user changed regions with the drop down, logged into the new region,
and started an instance. The instance started in the _previous_ region.
I'm not sure what debugging information to
Bolke -- that's not currently the case. If you want this functionality
you should file a separate bug for it. However, with a shared instances
directory you're best off disabling the cache manager entirely at the
moment.
--
You received this bug notification because you are a member of Ubuntu
Looking at the ec2 api code, this is pretty consistent for all these
calls -- you'll get the uuid (with keystone) or the project id (without
keystone) in all cases. This is consistent with the ec2 api
specification, which says this field should be:
ownerId The ID of the AWS account that owns the
Bolke -- that's not currently the case. If you want this functionality
you should file a separate bug for it. However, with a shared instances
directory you're best off disabling the cache manager entirely at the
moment.
--
You received this bug notification because you are a member of Ubuntu
Looking at the ec2 api code, this is pretty consistent for all these
calls -- you'll get the uuid (with keystone) or the project id (without
keystone) in all cases. This is consistent with the ec2 api
specification, which says this field should be:
ownerId The ID of the AWS account that owns the
** Tags added: canonistack ops
--
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:
** 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/1006671
Title:
swift command has unhelpful manpage
To manage notifications about this bug go to:
We have now observed this error on two testing clusters, so I don't
think this is because we're running precise-proposed in one any more.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
We have now observed this error on two testing clusters, so I don't
think this is because we're running precise-proposed in one any more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1019913
Title:
Public bug reported:
Running proposed on one of our clusters, I see the following with
instances started via juju. I have been unable to re-create the problem
with raw ec2 commands.
[instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] Ensuring static filters
[instance:
Public bug reported:
Running proposed on one of our clusters, I see the following with
instances started via juju. I have been unable to re-create the problem
with raw ec2 commands.
[instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] Ensuring static filters
[instance:
Public bug reported:
Before we turned on keystone, euca-describe-instances used to include
the names of user's projects in its output. It now lists the uuid of the
tenant instead, which isn't super helpful when trying to work out who
owns what. Can we please translate this back to a human
Public bug reported:
Before we turned on keystone, euca-describe-instances used to include
the names of user's projects in its output. It now lists the uuid of the
tenant instead, which isn't super helpful when trying to work out who
owns what. Can we please translate this back to a human
Public bug reported:
I went to run the glance command line client on one of my machines, but
it wasn't installed. I got:
$ glance index
'The program 'glance' is currently not installed. You can install it by typing:
apt-get install glance-common
However, glance-common was installed. It turns
The process of trying both univere and virtualbox.org versions involved
uninstalling the package, which removed the kernel module virtualbox
needs to work. Now I am having trouble getting the kernel module for
oneiric's kernel back.
--
You received this bug notification because you are a member
I've been using virtualbox for a while under oneiric and it hasn't had
problems, so I do suspect this is a precise kernel issue. I ran stress
for 40 minutes, and the machine was clearly working hard... The fans
were going full. sensors at the end said:
$ sensors
k10temp-pci-00c3
Adapter: PCI
** Package changed: ubuntu = virtualbox (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/926526
Title:
Virtualbox reboots system after precise upgrade
To manage notifications about this bug
And here's the syslog from that period. The inverter entries are from
my solar panels, you can ignore them.
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/926526/+attachment/2715499/+files/syslog
--
You received this bug notification because you are a
$ sudo apt-get install lm-sensors
[sudo] password for mikal:
Reading package lists... Done
Building dependency tree
Reading state information... Done
lm-sensors is already the newest version.
The following packages were automatically installed and are no longer required:
python-mox
Public bug reported:
I upgraded my workstation (an AMD64 machine with virtualization
extensions) to precise. Now when I run virtualbox virtual machines, the
workstation reboots within about a minute of starting the virtual
machine. This happens with both the virtualbox from universe, as well as
Public bug reported:
Nova now requires a policy.json file in /etc/nova/.
Update the packages to install this file which is in the source tree.
(This is an attempt to move https://bugs.launchpad.net/nova/+bug/915614
to the right place).
** Affects: nova (Ubuntu)
Importance: Undecided
Public bug reported:
The latest nova-compute adds a new command which needs sudo privs:
2012-01-13 22:24:27,385 DEBUG nova.utils [-] Running cmd (subprocess):
sudo guestmount --rw -a /var/lib/nova/instances/instance-000c/disk
-m /dev/sda1 /tmp/tmpXrLkev from (pid=2743) execute /data/backups-
Public bug reported:
Nova now requires a policy.json file in /etc/nova/.
Update the packages to install this file which is in the source tree.
(This is an attempt to move https://bugs.launchpad.net/nova/+bug/915614
to the right place).
** Affects: nova (Ubuntu)
Importance: Undecided
Public bug reported:
The latest nova-compute adds a new command which needs sudo privs:
2012-01-13 22:24:27,385 DEBUG nova.utils [-] Running cmd (subprocess):
sudo guestmount --rw -a /var/lib/nova/instances/instance-000c/disk
-m /dev/sda1 /tmp/tmpXrLkev from (pid=2743) execute /data/backups-
I have just send a patch for review which implements the _base cleanup
aspects of the blueprint. Its integrated into the nova compute manager,
as opposed to being a separate script.
https://review.openstack.org/#change,2902
--
You received this bug notification because you are a member of
I have just send a patch for review which implements the _base cleanup
aspects of the blueprint. Its integrated into the nova compute manager,
as opposed to being a separate script.
https://review.openstack.org/#change,2902
--
You received this bug notification because you are a member of
Public bug reported:
Hi.
I've just noticed that URLs are not logged for IRC sessions correctly
(they are skipped entirely). They also don't appear in gnome
notifications.
This problem appears to be fixed in upstream, with commit
370f2550ba89ba01ad396e0fd7967a4fd0414a49. This commit is nearly a
Public bug reported:
The nova base instance directory $instances_path/_base is never cleaned
up. This caused one of my compute nodes to run out of disk recently,
even though a bunch of the images there were no longer in use. There
appear to be homebrew cleanup scripts online, such as
87 matches
Mail list logo
