I, too, can confirm that I have the same problem:
$ sudo apt-get -u install libglib2.0-dev
Reading package lists... Done
Building dependency tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
I have a Merlin U630 and get the same sort of thing about shared
interrupts on Gutsy (2.6.22)
To get the card to work on my Laptop (HP dv1448ea) (915 chipset) I have
to exclude the serial port ranges that the PCMCIA modem wants to use:
/etc/pcmcia/config.opts:
exclude port 0x2f8-0x2ff
exclude
Hi,
Sorry, had forgotten about this bug. The problem does not existing in
7.10 - i.e. it seems to be fixed.
Best regards
Alex.
--
qemu crashes Xorg 7.2 in Feisty when switching to full screen mode (Ctl-Alt-F)
https://bugs.launchpad.net/bugs/113429
You received this bug notification because
I tried to hibernate/suspend from the dgm login screen and it makes no
difference. It still fails to hibernate with the same HAL error. It
hibernated and suspended perfectly in Edgy.
--
HAL failed to hibernate
https://bugs.launchpad.net/bugs/68258
You received this bug notification because you
Further investigation leads me to believe that it is a caching/data
problem in evolution-data-server with saved searches/virtual folders.
If I exit evolution and then kill evolution-data-server, and then
restart evolution everything is fine. If I then start browsing back and
forth between saved
I've upgrade to Feisty and I'm having the same problem. It hangs on
Send Receive after it has been running for a while - i.e. it uses 100%
for increasing amounts of time each time you do Send Receive. It is
definitely evolution and not evolution-data-server. I think it may have
something to
Public bug reported:
Binary package hint: xorg
When running Qemu (any guest OS) switching to full screen mode crashes
Xorg in Feisty. This didn't happen with Edgy. This happens with Qemu
0.8.2 from the repositories and building 0.9.0 from source.
It also happens with both the i810 and intel
Yep, I've got this too, but mine is en_GB. Very strange, and I can't
seem to fix it.
--
Bold, Italics, and Bold Italics not in English on Fonts menu
https://bugs.launchpad.net/bugs/105900
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Summary changed:
- [Intrepid] lifrea 1.4.18-0ubuntu2 seg faults with xulrunner
1.9.0.5+nobinonly-0ubuntu0.8.10.1
+ [Intrepid] liferea 1.4.18-0ubuntu2 seg faults with xulrunner
1.9.0.5+nobinonly-0ubuntu0.8.10.1
--
[Intrepid] liferea 1.4.18-0ubuntu2 seg faults with xulrunner
intrepid-proposed to see if this is fixed? If
you don't know how to use intrepid-proposal,
https://wiki.ubuntu.com/Testing/EnableProposed have instructions.
Thanks!
--
Alex Kavanagh
Home: http://alex.kavanagh.name
Work: http://www.tinwood.com
--
Liferea doesn't start with Aborted error
://wiki.ubuntu.com/Testing/EnableProposed have instructions.
Thanks!
--
Alex Kavanagh
Home: http://alex.kavanagh.name
Work: http://www.tinwood.com
--
Liferea doesn't start with Aborted error.
https://bugs.launchpad.net/bugs/295490
You received this bug notification because you are a member
Emilio Pozuelo Monfort wrote, On 20/01/09 16:41:
Alex Kavanagh wrote:
$ liferea
Segmentation fault
Did you try running /usr/bin/liferea directly? Perhaps you installed another
liferea version in /usr/local/bin.
Yes, did run running liferea directly, and no there is no other
On Thu, 2007-02-01 at 15:08 +, Daniel Holbach wrote:
Thanks for your bug report. Does this also happen with a new user
account? Does evolution print anything, if you start it from the
terminal?
I tried the new account and it is exactly the same.
However, in my testing I have discovered
Public bug reported:
Binary package hint: evolution-data-server
It worked in Dapper, but has stopped working in Edgy.
I have a webcal subscription:
webcal://username:[EMAIL PROTECTED]/webcal/publish.php/shared.ics
which no longer updates (30 minutes set). If I stop evolution, kill
Public bug reported:
Binary package hint: liferea
liferea is now seg faulting after a recent aptitude safe-upgrade brought
in a new version of Firefox: 3.0.5+nobinonly-0ubuntu0.8.10.1
liferea --debug-all gives:
...
...
PLUGINS: - XulRunner Rendering Plugin (liblihtmlx.so, type=0)
PLUGINS:
** Attachment added: liferea --debug-all run.
http://launchpadlibrarian.net/20571648/run.txt
--
[Intrepid] lifrea 1.4.18-0ubuntu2 seg faults with xulrunner
1.9.0.5+nobinonly-0ubuntu0.8.10.1
https://bugs.launchpad.net/bugs/309640
You received this bug notification because you are a member of
Emilio Pozuelo Monfort wrote, On 02/01/09 08:42:
Alex Kavanagh wrote:
Public bug reported:
Binary package hint: liferea
liferea is now seg faulting after a recent aptitude safe-upgrade brought
in a new version of Firefox: 3.0.5+nobinonly-0ubuntu0.8.10.1
liferea --debug-all gives
I'm guessing that on The Dark Knight is so that it can be tested. It
also fails on Criminal Minds Season 4 (UK region) as well. Happy to
test any updated software.
--
libdvdread libdvdread: CHECK_VALUE failed in ifo_read.c:1913 on The Dark
Knight
https://bugs.launchpad.net/bugs/377414
You
Public bug reported:
The landscape web interface is constantly asking for a reboot of the
machine, but even when it has a scheduled reboot, it does not clear the
instruction. The landscape system is in contact with the machine and
can install/upgrade software.
A scheduled reboot does reboot the
Here are the log files as requested.
** Attachment added: "/var/log/landscape/*"
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1663542/+attachment/4816486/+files/landscape.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Re: comment #21 and gating; if this is fully async, then gating is only
going to tighten the race, but not eliminate it. i.e. code like:
if is_leader():
leader_set(...)
can still error as the leadership could be lost between the two calls.
The only safe way of doing leadership code
It sounds like this is probably fixed. Just need to schedule a test to
check if it has been.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659604
Title:
root disk flavor constraints not applied
@Corey, yes, you're correct; xenial doesn't use it; It first appeared in
2.2.5, and xenial is on the 2.0.x series. So artful got 2.2.x series,
which means artful has the issue, whereas xenial as 2.0.7 which means it
doesn't have this feature (as we didn't backport it).
--
You received this bug
@sil2100, that is a good catch, and sadly, Corey, there isn't an easy
solution. What requests.toolbelt is used for is to allow Multipart
uploads to lxd (from pylxd) so that data can be streamed from disk,
rather than pulled into memory.
nova-lxd DOES use this feature, in that it grabs the image
Newton is now eol; however, it still needs a fix for mitaka.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675386
Title:
all network devices aren't added to instance profile
To manage
Updated stable/mitaka patch which includes changelog update.
** Patch added: "Updated patch for stable/mitaka"
https://bugs.launchpad.net/nova-lxd/+bug/1675386/+attachment/5147055/+files/01_bug-1675386-ensure-all-net-devices-added.patch
--
You received this bug notification because you are
@corey.bryant -- I probably didn't have 2.2.6 ready at the time; sorry.
I'll test it as soon as it becomes available in proposed. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754657
Title:
** Also affects: nova-lxd
Importance: Undecided
Status: New
** Changed in: nova-lxd
Status: New => Triaged
** Changed in: nova-lxd (Ubuntu)
Status: New => In Progress
** Changed in: nova-lxd
Status: Triaged => In Progress
** Changed in: nova-lxd
Importance:
** Changed in: nova-lxd (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.launchpad.net/bugs/1771928
Title:
Disk usage leak on image import
To manage notifications
So tested this manually on xenial (pylxd/lxd) and it's all working
perfectly.
Also checked with lxd charm/nova-compute (mitaka) to verify that the
nova-compute/nova-lxd/pylxd combo works; did this by running up an
openstack bundle (openstack-bundles/development/openstack-lxd-xenial-
mitaka) and
stable/mitaka patch as a diff file that fixes the bug.
Note this is only a debian patch diff file; the stable/mitaka source has
not been altered.
** Description changed:
RELEASE: nova-compute-lxd 13.3.0-0ubuntu1
DESCRIPTION:
In config.py the network_devices object should be returned
I can't check artful as pylxd 2.2.6 doesn't appear in artful-proposed
yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754657
Title:
[SRU] python-pylxd 2.0.7 (xenial), python-pylxd 2.2.6
Moving to low as it's most likely been fixed; still need to test it.
** Changed in: nova-lxd
Importance: High => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659604
Title:
root disk
** Changed in: nova-lxd (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/1583524
Title:
nova-lxd doesn't create the VLAN interface with LinuxBridge and
Closing as newton is end-of-life now, and fix was done to master.
** Changed in: nova-lxd (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636706
Title:
** Description changed:
[Impact]
This is a new point release of nova-lxd for stable/queens. This has fixes to
work with LXD 3.0 which removed some zfs storage keys from the default config.
This has been fixed in master, and backported to stable/queens:
Public bug reported:
This is a new release for stable/queens. This has fixes to work with
LXD 3.0 which removed some zfs storage keys from the default config.
This has been fixed in master, and backported to stable/queens:
https://review.openstack.org/#/c/584900/
** Affects: nova-lxd (Ubuntu)
Verified on bionic with queens proposed using https://github.com
/openstack-charmers/openstack-bundles/tree/master/development/openstack-
lxd-bionic-queens bundle (for MaaS)
Verified that a server instance can be booted and that no errors occur.
** Tags removed: verification-needed
** Changed in: cloud-archive/queens
Assignee: (unassigned) => Alex Kavanagh (ajkavanagh)
** Changed in: nova-lxd (Ubuntu Bionic)
Assignee: (unassigned) => Alex Kavanagh (ajkavanagh)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Hi Łukasz
Sorry, I should have been more specific. The openstack-lxd-bionic-
queens bundle tests the distro installed version of OpenStack on bionic,
which is the OpenStack queens release. I then used the queens-proposed
archive to verify that the 17.0.1 release of nova-lxd was being
installed
** Tags removed: verification-pike-needed
** Tags added: verification-pike-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754657
Title:
[SRU] python-pylxd 2.0.7 (xenial), python-pylxd 2.2.6
@coreycb pike-proposed on xenial is giving python 2.2.6, which is fine
as it will work. 2.0.7 is in xenial standard:
sudo add-apt-repository cloud-archive:pike-proposed
sudo apt update
sudo apt install python-pylxd
apt policy python-pylxd
python-pylxd:
Installed: 2.2.6-0ubuntu0.17.10.1~cloud0
Ryan, my bad -- I should have updated the bug; I've provided Colin with
a serverstack bastion and some scripts to do testing, and Colin has been
doing that. Apologies that the bug didn't reflect this new information.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I've confirmed that this function with mitaka/xenial using the amulet
test associated with lxd.
** Tags removed: verification-mitaka-needed verification-needed
verification-needed-xenial
** Tags added: verification-done verification-mitaka-done
verification-xenial-done
--
You received this
Thanks Colin for tracking this done; very pleased it's not a kernel bug.
I'll now take this up with the snappy team. Thank again for doing the
detective work; much appreciated!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: charm-lxd
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801349
Title:
zpool create -f lxd /dev/vdb fails on cosmic (18.10)
Thanks Brian for the help with this; apologies for getting the tags
wrong! I'll fix them now.
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Colin, sorry, no; it's the bug that 'found' the issue; it's basically
saying that we aren't enabling a particular gate test (i.e. it's staying
dev-) due to this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yeah, this is a pain. cosmic-rocky is going to be a 'thing' though for
our OpenStack releases, so this is going to be awkward to fix if
upstream glance won't take the backport to rocky.
Is it possible to change the package to use py3compile with the -V
option: (from the help):
-V VRANGE
Note that the LXD charm change is a workaround to the nova-lxd bug. The
nova-lxd bug still needs to be fixed so that the LXD pool name can be
different to the ZFS pool name.
** Changed in: charm-lxd
Status: In Progress => Fix Committed
--
You received this bug notification because you
I suspect the reason is that 'async' is now a reserved word, and thus
glance can't use it for a module or submodule name.
In fact, we have a bug filed for this:
https://bugs.launchpad.net/glance/+bug/1781617
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
The following is the stack track from install:
2018-09-27 11:28:44 DEBUG install Setting up python3-glance (2:17.0.0-0ubuntu3)
...
2018-09-27 11:28:45 DEBUG install File
"/usr/lib/python3/dist-packages/glance/async/flows/api_image_import.py", line 26
2018-09-27 11:28:45
Narinder: So now the charm and gss should support ssl (at least in my
tests!) Please could you test them and comment back here the results.
Thanks, Alex.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So this is what I tested and verified works with python-nova-lxd 17.0.1:
Package: python-nova-lxd
Version: 17.0.1-0ubuntu1
Priority: extra
Section: python
Source: nova-lxd
Origin: Ubuntu
Maintainer: Chuck Short
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 308 kB
Depends:
** Changed in: nova-lxd
Assignee: (unassigned) => Alex Kavanagh (ajkavanagh)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790956
Title:
syntax error in manager.py ping_ip_address
To man
Okay, for the avoidance of doubt, I will re-do my tests and post the
actual package versions here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789427
Title:
[SRU] Release tagged version 17.0.1
>From the perspective of nova-lxd, there isn't a problem with the snap
version (as pylxd already works with a snap version of lxd). However,
the lxd charm will need to be altered to ensure that it installs /
otherwise manages the fact that lxd is supplied in snap form.
We do have some utilities
Tested this on xenial, with the cloud archive, and the following package
details:
root@xenial-test:~# apt show python-pylxd
Package: python-pylxd
Version: 2.2.6-0ubuntu1.1~cloud0
Priority: optional
Section: python
Maintainer: Chuck Short
Installed-Size: 304 kB
Depends: python-babel (>= 1.3),
In bionic: these packages also test/install fine:
root@bionic-test:~# apt show python-pylxd
Package: python-pylxd
Version: 2.2.6-0ubuntu1
Priority: extra
Section: python
Origin: Ubuntu
Maintainer: Chuck Short
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 304 kB
Depends:
Marking the simplestreams bug as fix released as keystone v3 was added
to it in 2017-09-14 with this commit:
https://git.launchpad.net/simplestreams/commit/?id=1dab951f16541ee29d72a80296e4b4f413761067
** Changed in: simplestreams
Status: Confirmed => Fix Released
** Changed in:
** Changed in: nova-lxd/rocky
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/1815325
Title:
nova-lxd fails to boot with TypeError: 'filter' object is not
** Also affects: nova-lxd (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/1815325
Title:
nova-lxd fails to boot with TypeError: 'filter' object is
** Changed in: nova-lxd/rocky
Assignee: (unassigned) => Alex Kavanagh (ajkavanagh)
** Changed in: nova-lxd/trunk
Assignee: (unassigned) => Alex Kavanagh (ajkavanagh)
** Changed in: nova-lxd/rocky
Assignee: Alex Kavanagh (ajkavanagh) => Michael Johnson (johnsom)
*
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Changed in: charm-nova-compute
Status: New => Triaged
** Changed in: charm-nova-compute
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Release tagged 18.0.1 in the nova-lxd git repository contains updates
for the stable/rocky which is the distro release for cosmic.
** Affects: nova-lxd (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- [SRU} Release 18.0.1 (rocky update) for
** Changed in: charm-ceph-radosgw
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838109
Title:
civetweb does not allow tuning of maximum socket connections
To manage
** Changed in: charm-lxd
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788040
Title:
Replace LXD deb by snap in Ubuntu 18.10
To manage notifications about this
** Tags added: series-upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828293
Title:
[Queens -> Rocky Upgrade] python3-neutron-fwaas-dashboard
installation: trying to overwrite
This doesn't seem to be a charm bug; if it is related to the charm, then
please re-open.
** Also affects: ceph (Ubuntu)
Importance: Undecided
Status: New
** Changed in: charm-ceph-osd
Status: New => Invalid
--
You received this bug notification because you are a member of
** Changed in: charm-cinder
Status: New => Triaged
** Changed in: charm-nova-compute
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842751
Title:
[disco]
Not sure if this is still an issue? Is this on new deployments or
upgrades?
** Changed in: charm-glance
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/1782644
Title:
> Hello - Does the recent switch from New -> Triaged for charm-cinder
and charm-nova-compute mean that someone was able to determine that the
charms are to blame and perhaps not the kernel?
Sadly not; I'm just knocking them off new; the alternative is incomplete
which means they'll time out after
TRIAGE: Confirmed, but not sure whether to fix in packages or "make the
problem go away" in the charm; more discussion needed.
** Also affects: ceph (Ubuntu)
Importance: Undecided
Status: New
** Changed in: charm-ceph-mon
Status: New => Triaged
--
You received this bug
Marking the openstack-dashboard bug as invalid, as it was a packaging
bug. There is a separate bug (lp:1837457) about handling upgrade
failures in charms as they were not reported.
** Changed in: charm-openstack-dashboard
Status: Triaged => Invalid
** Changed in:
This appears to be a packaging bug rather than a charm bug; or it's
basically an issue with the openstack-dashboard in that the themes have
to be placed where packages put files, rather than in config. Either
way, it's invalid for the charm; changing it to the package.
** Changed in:
I upgraded from 18.04 to focal and had the same problem. Purging
timidity got audio back for me as well.
** Tags added: champagne focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
Title:
Public bug reported:
glance-common: 2:20.0.0~b3~git2020032414.30ece7aa-0ubuntu2~cloud0 failed
to install on focal:
Expected it to install:
Actually failed to install, producing this trace:
2020-04-09 15:10:25 DEBUG install Setting up glance-common
Hi Mateusz
> Can we get this fix backported to Bionic ?
Not sure, as it is a new feature rather than a bug fix. However, it is
'bug' like in that one would expect it to work; I can ask, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Manual testing of mojo specs of the change in keystone is successful!:
# stable_to_next
$ ./go-mojo.sh bionic specs/full_stack/stable_to_next/queens
2020-03-13 12:19:57 [INFO] Using pre-existing container class containerless
2020-03-13 12:19:57 [INFO] Rsyncing
Note I've pushed this review as a fix for this:
https://review.opendev.org/#/c/730376/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865754
Title:
tripleo-ci-centos-8-scenario001-standalone
** Tags added: charm-upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838552
Title:
charm upgrade restarted neutron-ovs-agent even though config was
unchanged
To manage notifications about
Some additional information regarding how the bug was found:
During the upgrade the ovs runs, deleting the ports. They don't come
back, even after restarting the services, which suggests an issue within
the neutron openvswitch agent in terms of re-creating ports that have
been deleted.
from the
Additional details from a compute unit:
on nova/compute/1 -- before stopping the unit, but after upgrading from
train->ussuri on bionic. Note that the disk, console.log are owned
nova.nova.
root@juju-ed722c-mojo-17:/var/lib/nova/instances/499b7f90-4e5e-4eb9-b29b-2befe835cbe7#
ll
total 184692
** Changed in: nova-lxd
Assignee: Alex Kavanagh (ajkavanagh) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790956
Title:
syntax error in manager.py ping_ip_address
To man
** Changed in: nova-lxd/rocky
Assignee: Alex Kavanagh (ajkavanagh) => (unassigned)
** Changed in: nova-lxd/trunk
Assignee: Alex Kavanagh (ajkavanagh) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: charm-ceph-rbd-mirror
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/1865754
Title:
tripleo-ci-centos-8-scenario001-standalone
** Changed in: charm-designate
Status: Fix Committed => 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/1828534
Title:
[19.04][Queens -> Rocky] Upgrading to Rocky resulted in
** Changed in: charm-glance
Status: Fix Committed => 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/1881140
Title:
Add tempest functional test coverage to OpenStack charms
To
** Changed in: charm-glance
Milestone: None => 20.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881140
Title:
Add tempest functional test coverage to OpenStack charms
To manage
** Changed in: charm-designate
Milestone: None => 20.10
** Changed in: charm-designate
Status: Fix Committed => 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/1899064
Title:
** Changed in: charm-ceph-mon
Status: Fix Committed => 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/1852441
Title:
In bionic, one of the ceph packages installed causes chrony
Hi Christian,
I've tested the patch in your [2] ([2] below) and it worked perfectly.
I got a colleague to rebuild it for me against the current focal libvirt
[1] as I couldn't find your PPA mentioned. I'm upgrading an OpenStack
system from bionic-ussuri -> focal-ussuri, and confirmed that the
** Changed in: charm-barbican
Status: Fix Committed => 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/1827690
Title:
[19.04][stein] barbican-worker is down: Requested revision
** Changed in: charm-neutron-openvswitch
Status: New => Triaged
** Changed in: charm-neutron-openvswitch
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: charm-nova-cloud-controller
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/1259760
Title:
Spice console isn't working when ssl_only=True is set
To
Not a charm bug now.
** Changed in: charm-hacluster
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/1118815
Title:
Remove python-oauth from the archive
To manage
Triaged to medium; there should be a fix for the openstack-dashboard
charm to setup horizon to do this, but it can be done from the CLI as a
workaround.
** Changed in: charm-openstack-dashboard
Status: New => Confirmed
** Changed in: charm-openstack-dashboard
Importance: Undecided =>
** Changed in: charm-ovn-chassis
Milestone: None => 21.10
** Changed in: charm-ovn-dedicated-chassis
Milestone: None => 21.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940043
Title:
** Changed in: charm-ceph-radosgw
Milestone: None => 21.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921453
Title:
multi-zone replication doesn't work
To manage notifications about this
https://review.opendev.org/c/openstack/charm-neutron-gateway/+/810411
<-- this makes this fix committed. \o/
** Changed in: charm-neutron-gateway
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
1 - 100 of 122 matches
Mail list logo
