On Tue, Jan 29, 2019 at 5:50 PM Ryan Harper <1812...@bugs.launchpad.net>
wrote:
> I'm not 100% sure at which point ceph/charms make use of the dname
> symlinks, but ceph appears to be up much earlier than this.
>
> $ journalctl -o short-monotonic -D fd6c366f929d47a195590b3c6dc9df5a -u
> ceph*
> --
Workaround for the time being until the actual root cause is identified:
juju run --application ceph-osd "sudo udevadm trigger --subsystem-
match=block --action=add"
before unsealing and authorising the vault charm. Charm task marked
incomplete pending diagnosis of what's actually mangling the
** Changed in: charm-ceph-osd
Importance: Critical => High
** Changed in: charm-ceph-osd
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bcache-tools in Ubuntu.
https://bugs.launchpad.net/bugs/181
Re-triggering udev outside of the charm creates the missing by-dname
entries:
sudo udevadm trigger --subsystem-match=block --action=add
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bcache-tools in Ubuntu.
https://bugs.launchpad.net/bugs
Raising a bug task for bcache-tools
** Also affects: bcache-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bcache-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1812925
Title:
An obvious workaround would be to trigger a re-scan before the ceph-osd
charm tries to osdize the bcache devices - I would consider this a
workaround only as the by-dname devices really should be present before
the charm executes.
--
You received this bug notification because you are a member of
@paelzer
"@James - does the UCA for B-to-X hold also a source of ipxe-qemu-256k-
compat-efi-roms?"
Yes
"@James - does the qemu in UCA for B-to-X has [1] and [2]?
https://salsa.debian.org/qemu-team/qemu/commit/7b917f26ac6a224195f68088dcd8e8f99d932675
https://salsa.debian.org
FWIW this issue is blocking migration of any python related updates in
disco development:
http://people.canonical.com/~ubuntu-archive/proposed-
migration/update_excuses_by_team.html#ubuntu-openstack
We have a number of openstack projects with autopkgtests which use
rabbitmq-server which are curre
I think the Elixir warning is unrelated, but problem does need address;
the unit test suite errors are symptomatic of the same underlying issue
effecting RMQ.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to rabbitmq-server in Ubuntu.
https:/
** Description changed:
+ Ubuntu: disco development
+
On a new deployment, erlang will create a cookie with a random secret
value for use; however it must have 0400 permissions otherwise erlang
will refuse to use it.
On s390x the automatic cookie creation code fails with:
-args:
All of the errors are related to file permissions; however I do think
this is something in erlang rather than elixir.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1808984
Title:
Attempting to resolve by making elixir Arch: any
https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3568/+packages
However tests fail on s390x which probably tells us something
interesting.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subsc
Might be related:
Dec 18 14:14:35 rmq-more-tesitng rabbitmq[24111]: warning: Elixir is
running in a system with a different endianness than the one its source
code was compiled in. Please make sure Elixir and all source files were
compiled in a machine with the same endianness as the current one:
Public bug reported:
On a new deployment, erlang will create a cookie with a random secret
value for use; however it must have 0400 permissions otherwise erlang
will refuse to use it.
On s390x the automatic cookie creation code fails with:
args: []
format: "Failed to change mode: einval"
Alternatively we could drop the
BindToDevice=lo
Stanza in the @'less socket unit
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1808766
Title:
fails to start
To manage notific
OR
rabbitmq-server installs without enabling and starting its daemon;
requiring the user to reconfigure epmd (or disable it completely).
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/b
List of potentially impacted packages:
* averell
* ejabberd
* ejabberd-contrib
* ejabberd-mod-cron
* ejabberd-mod-log-chat
* ejabberd-mod-logsession
* ejabberd-mod-logxml
* ejabberd-mod-message-log
* ejabberd-mod-muc-log-http
* ejabberd-mod-post-log
* ejabberd-mod-pottymouth
* ejabberd-mod-rest
*
Proposal to resolve this issue (as I quite like the way RabbitMQ uses
@'ed units).
Ship @'less and @'ed epmd.{socket|service} units in the erlang packages,
all installed by disable by default.
So epmd does not get started by default; only when another erlang
application expresses and interest in
RabbitMQ includes:
After=network.target epmd@0.0.0.0.socket
Wants=network.target epmd@0.0.0.0.socket
in its systemd unit file; however the @ notation on the epmd socket is
not compatible with the erlang packaging in Ubuntu and Debian (which
only ships @'less versions).
** Also affects: erlang (
Raising erlang task as well because we might want to fix things there
rather than rmq.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1808766
Title:
fails to start
To manage not
Other distro references:
https://bugzilla.suse.com/show_bug.cgi?id=1003085
** Bug watch added: bugzilla.suse.com/ #1003085
https://bugzilla.suse.com/show_bug.cgi?id=1003085
** Bug watch added: Red Hat Bugzilla #1104843
https://bugzilla.redhat.com/show_bug.cgi?id=1104843
--
You received t
And
https://bugzilla.redhat.com/show_bug.cgi?id=1104843
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1808766
Title:
fails to start
To manage notifications about this bug go t
I think this is due to the erlang-base package now enabling a shared
epmd daemon by default; rabbitmq-server is unable to connect to it over
the hostname of the server as it only listens on localhost by default.
--
You received this bug notification because you are a member of Ubuntu
Server, whic
** Changed in: spice-html5 (Ubuntu)
Status: Expired => Incomplete
** Changed in: spice-html5 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to websockify in Ubuntu.
https://bugs.launchpad.net/b
@Th - I think you're probably correct in that this is a load issue,
rather than a specific rabbitmq software issue. It looks like the
system is so loaded you're hitting some sort of 90 second timeout at
which point systemd just gives up:
/etc/systemd/system.conf: DefaultTimeoutStartSec=90s
you
Dropped googleapi to Suggests, avoiding the need for this MIR
** Changed in: resource-agents (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to resource-agents in Ubuntu.
https://bugs.launchpad.net/bugs/1
I'm not sure this is coming from cinder - the dependency chain is
python-oauth2client -> python-googleapi -> resource-agents (Recommends).
** Package changed: python-oauth2client (Ubuntu) => resource-agents
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server,
** Changed in: neutron-dynamic-routing (Ubuntu)
Assignee: Ubuntu Server (ubuntu-server) => Ubuntu OpenStack uploaders
(ubuntu-openstack-dev)
--
You received this bug notification because you are a member of Ubuntu
Server, which is a bug assignee.
https://bugs.launchpad.net/bugs/1746759
Tit
** Changed in: neutron (Ubuntu)
Status: New => Invalid
** Changed in: neutron (Ubuntu Xenial)
Status: New => Invalid
** Changed in: neutron (Ubuntu Bionic)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server, which is subsc
** Changed in: openvswitch (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: openvswitch (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1718
Please check that forward/reverse hostname to IP is working OK on the
impacted systems; if it is then set the bug back to New with an
appropriate comment, if not then we can close out this bug report IMHO.
--
You received this bug notification because you are a member of Ubuntu
Server, which is s
rabbitmq is also very sensitive to any hostname <-> IP mismatch as it
uses this to communicate with the RMQ daemon.
'rabbit@hostname' looks suspicious here - I'd suggest that maybe
something is a bit wonky.
If a "sudo su -" results a warning about hostnames this is def the
issue.
** Changed in:
Now that is a useful nugget of information.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1783203
Title:
Upgrade to RabbitMQ 3.6.10 causes beam lockup in clustered deployment
T
Logs from /var/log/rabbitmq might be useful here
** Also affects: rabbitmq-server (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Upgrade to Queens causing crashing
+ Upgrade to RabbitMQ 3.6.10 causes beam lockup in clustered deployment
--
You received this bug notif
** Changed in: charm-ceph-mon
Status: Fix Committed => Fix Released
** Changed in: charm-ceph-mon
Milestone: 18.08 => 18.05
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1773449
** Changed in: charm-ceph-mon
Assignee: (unassigned) => James Page (james-page)
** Changed in: charms.ceph
Assignee: (unassigned) => James Page (james-page)
** Changed in: charm-ceph-mon
Status: Triaged => In Progress
** Changed in: charms.ceph
Status: Tria
OK figured this one out - the cephx keys are missing a permission which
allows them to see blacklisted clients - as a result they can't deal
with a hard crash:
mon 'allow command "osd blacklist"'
This is a charm issue after all.
As a workaround you can manually update the existing client keys
Raising bug tasks for ceph and qemu as I think this is where the issue
lies; nova generates the same libvirt xml disk stanzas for versions that
work and versions that have this issue.
** Also affects: ceph (Ubuntu)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu)
Impo
Note that the UCA for trusty-mitaka does include a later haproxy version
with the same fixes - however nice to get the stock trusty version fixed
up as well!
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to haproxy in Ubuntu.
https://bugs.lau
; High
** Changed in: haproxy (Ubuntu Trusty)
Status: New => In Progress
** Changed in: haproxy (Ubuntu Trusty)
Assignee: (unassigned) => James Page (james-page)
** Description changed:
- While testing upgrades of an Ubuntu 14.04 deployment of OpenStack from
- ~15.04 to 17.11 charm
** Also affects: haproxy (Ubuntu)
Importance: Undecided
Status: New
** Changed in: haproxy (Ubuntu)
Status: New => Triaged
** Changed in: haproxy (Ubuntu)
Importance: Undecided => High
** Changed in: charm-swift-proxy
Status: Triaged => Invalid
** Changed in: charm-no
Tested on my laptop using hostname based endpoint from IPv6 enable
location (was failing previously); packages from PPA resolved my
problem.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to a duplicate bug report (1756032).
https://bugs.launc
I'm also using the network manager plugin for reference.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1756032
Title:
No VPN connectivity when accessing tunnel endpoint over IPv6
To manag
This is bionic top to bottom.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1756040
Title:
bionic: LXD containers don't get fan network IP addresses
To manage notifications about th
Public bug reported:
Juju Version: 2.3.4
Substrate: OpenStack
I'm deploying a bundle which makes use of LXD containers, leveraging fan
networking for communication between containers and hosts; containers
start and have the following config snippet:
devices:
eth0:
hwaddr: 00:16:3e:01:7e:0
Public bug reported:
Our VPN provides both IPv4 and IPv6 addresses for the tunnel endpoint.
With the latest openvpn on Bionic, the VPN starts, but no network
connectivity is actually established if the client is accessing from an
IPv6 enabled location; forcing the tunnel endpoint to IPv4 (using it
** Changed in: nova (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
** Changed in: nova (Ubuntu)
Status: Triaged => In Progress
** Also affects: cloud-archive/pike
Importance: Undecided
Status: New
** Also affects: cloud-archive/queens
Importance
** Project changed: charm-nova-compute => nova (Ubuntu)
** Changed in: nova (Ubuntu)
Status: New => Triaged
** Changed in: nova (Ubuntu)
Importance: Undecided => High
** Changed in: cloud-archive
Status: New => Triaged
** Changed in: cloud-archive
Importance: Undecided => Hi
** Also affects: charm-nova-compute
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1754015
Title:
nova-compute-kvm does not pull ipxe-qemu on
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1754015
Title:
nova-compute-kvm does not pull ipxe-qemu on no
This bug was fixed in the package qemu - 1:2.10+dfsg-0ubuntu3.4~cloud0
---
qemu (1:2.10+dfsg-0ubuntu3.4~cloud0) xenial-pike; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
qemu (1:2.10+dfsg-0ubuntu3.4) artful-security; urgency=medium
.
* SECURITY UPDATE: Add s
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we c
** Also affects: cloud-archive/mitaka
Importance: Undecided
Status: New
** Changed in: cloud-archive/mitaka
Status: New => Triaged
** Changed in: cloud-archive
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Tea
Based on #10 and some testing I did early today, it really feels like
this might be a bug in pacemaker when re-connecting to corosync after a
restart; I think there are two ways forward on this:
a) corosync package updates should always restart pacemaker
b) we should look for a fix in pacemaker to
bug 1739033 was the stable release update that went in around this time.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pacema
** Changed in: nova (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: nova (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
** Changed in: rabbitmq-server (Ubuntu)
Status: New => Triaged
** Changed in: rabbitmq-server (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: rabbitmq-server (Ubuntu)
Milestone: None => ubuntu-18.04
--
You received this bug notification because you are a member of Ubuntu
The two exceptions to my commit where moin and tickcount which I'll
defer to other members of the ubuntu server team to deal with.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-django in Ubuntu.
https://bugs.launchpad.net/bugs/
I've dropped the seeded packages from this list that relate to OpenStack
bits; however they won't push out to universe as they are dependencies
of other seeded packages.
** Changed in: python-posix-ipc (Ubuntu)
Status: New => Fix Released
** Changed in: python-openid (Ubuntu)
Status
This bug was fixed in the package websockify - 0.6.1+dfsg1-1ubuntu1~cloud0
---
websockify (0.6.1+dfsg1-1ubuntu1~cloud0) trusty-mitaka; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
websockify (0.6.1+dfsg1-1ubuntu1) xenial; urgency=medium
.
* Fix hanging nova-
** Changed in: ceph (Ubuntu)
Assignee: Ubuntu Server Team (ubuntu-server) => James Page (james-page)
** Changed in: ceph (Ubuntu)
Status: New => Triaged
** Changed in: ceph (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a
Also validated that the update fixes an existing machine with the 1.2
update on it (with pacemaker services not running).
Pacemaker started after the update.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://
Also tested proposed fix on a three unit gnocchi HA deployment; all
pacemaker updates applied and restarted pacemaker postinst as desired.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/b
Testing from security-proposed PPA:
Broken install (dpkg-reconfigure pacemaker already run, daemons
stopped): Packages updated and pacemaker daemon restarted by postinst:
OK
Running install (pacemaker daemons running prior to pkg upgrade):
Packages update, pacemaker daemon stop prior to unpack a
Updates building in:
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1727063
Title:
Pacemaker package upgrade
** Description changed:
[Impact]
upgrades of the pacemaker package don't restart pacemaker after the package
upgrade, resulting in down HA clusters.
[Test Case]
sudo apt install pacemaker
sudo systemctl start pacemaker
sudo dpkg-reconfigure pacemaker
pacemaker daemons will not
Tested OK (pacemaker was restarted after upgrade)
Uploaded to unapproved queue for SRU Team review - I'd suggest we
fasttrack this ASAP into -updates and -security to catch auto updates
for those systems not already updated.
--
You received this bug notification because you are a member of Ubunt
Doing some testing via:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3010
before upload to xenial-proposed; not that the act of fixing this
problem will in itself cause the pacemaker daemons to be started on
upgrade. However it won't be auto-applied on a default install (unlike
Proposed update for xenial
** Patch added: "pacemaker.debdiff"
https://bugs.launchpad.net/ubuntu/zesty/+source/pacemaker/+bug/1727063/+attachment/4993845/+files/pacemaker.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pace
Actually this only impacts Xenial; Debian carried a patch from:
pacemaker (1.1.15~rc3-1) unstable; urgency=medium
[ Christoph Berg ]
* [23ee108] libcrmservice3.symbols: Exclude systemd symbol on non-linux
* [41dea05] Fix time formatting on x32
* [533c5cc] Fix FTBFS on GNU Hurd
[ Arturo
This issue can be fixed by re-adding the required Start/Stop bits to the
LSB header; however the behaviour of update-rc.d when native systemd
unit files are in use looks odd to me.
Raising an init-system-helpers bug task for foundations team input on
this.
** Also affects: init-system-helpers (Ub
Hmmm - however pacemaker@xenial ships with a native systemd unit; so I'm
baffled as to the behaviour of the package upgrade.
** Description changed:
- We have found on our openstack charm-hacluster implementations that the
- pacemaker .deb packaging along with the upstream pacemaker configuration
See related bug 1727063
** Changed in: pacemaker (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1322899
Title:
pacemaker init script
See related bug 1727063
** Changed in: pacemaker (Ubuntu)
Status: Confirmed => Triaged
** Changed in: pacemaker (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
http
Marking charm bug task as invalid - its doing the right things, however
the package does not declare default start/stop levels so its all
foobar.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpa
Other related bugs - bug 1322899 and bug 1052449
** Changed in: pacemaker (Ubuntu)
Status: Confirmed => Triaged
** Changed in: pacemaker (Ubuntu)
Importance: Undecided => High
** Changed in: pacemaker (Ubuntu)
Importance: High => Critical
** Also affects: pacemaker (Ubuntu Artful)
I think this is a packaging/upstream bug which I appear to have had a go
at before (see #4); however I've not seen this specific symptom before.
** Changed in: charm-hacluster
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, whic
And
https://github.com/ClusterLabs/pacemaker/pull/656
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1727063
Title:
Pacemaker package upgrades stop but fail to start pacemaker re
Hmm
https://github.com/ClusterLabs/pacemaker/commit/fc11a4651b971bd3b9dfc15b8b5c538c7ee9ab75
#diff-06baf804b1f5edee72fb63df4b884b7c
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/17
I appreciate that this is an older bug, but if you could provide details
on which Ubuntu release and which version of the rabbitmq-server package
you see this issue that would be helpful.
Marking 'Incomplete' and 'Low' for now. Please set back to 'New' when
the information requested has been prov
Jorge
Have you seen this issue in Xenial or later releases of the RabbitMQ
server package? Xenial included a 3.5.x series rabbitmq which should
contain the fixes referenced.
Note that we also provide this version of RMQ for trusty uses via the
Icehouse Ubuntu Cloud Archive.
** Changed in: rabbi
Hi
Trusty shipped with RMQ 3.2.4-1ubuntu0.1 - I see you have 3.3.5-1
installed which I can't find in any currently supported Ubuntu release,
or the Ubuntu Cloud Archive pockets for Ubuntu Trusty.
I'm not able to reproduce this issue on either trusty or xenial package
versions.
Please could you c
erlang/rmq is notoriously brittle if the hostname being used
('controller') does not forward and reverse resolve on the host its
running on (and all other hosts that you might want to cluster it with).
Please check this is the case:
sudo nslookup controller
Marking 'Incomplete'; if the hostnam
@paelzer
No we don't - sorry.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1691109
Title:
qemu-kvm not working as nested inside ESX 6.0
To manage notifications about this bug go to
Reassigning to the Linux package as that's where this driver resides
(libiscsi is a pure userspace implementation of the iSCSI client
protocol).
** Package changed: libiscsi (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: libvirt (Ubuntu Vivid)
Status: Confirmed => Won't Fix
** Changed in: nova (Ubuntu Trusty)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net
** Changed in: nova (Ubuntu)
Status: Confirmed => Triaged
** Changed in: nova (Ubuntu)
Importance: High => Medium
** Changed in: nova (Ubuntu)
Milestone: None => ubuntu-18.04
** Changed in: nova (Ubuntu)
Assignee: James Page (james-page) => (unassigned)
--
You r
** Changed in: nova (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1659648
Title:
Instance hung on first start, but works after being killed and
** Changed in: ipset (Ubuntu)
Status: New => Triaged
** Changed in: ipset (Ubuntu)
Importance: Undecided => Medium
** Changed in: ipset (Ubuntu)
Milestone: None => ubuntu-18.04
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribe
** Changed in: rabbitmq-server (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1679386
Title:
Missing dep8 tests
To manage notificatio
** Changed in: rabbitmq-server (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/968722
Title:
/usr/sbin missing some wrappers for plugin
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Also affects: websockify (Ubuntu)
Importance: Undecided
Status: New
** Changed in: charm-nova-cloud-controller
Status: New => Invalid
--
You received this bug notification because you are a member of
@freyes
Yes definitely!
** Changed in: charm-nova-compute
Status: New => Invalid
** Changed in: libvirt (Ubuntu)
Status: New => Triaged
** Changed in: libvirt (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Serve
This bug was fixed in the package libvirt - 2.5.0-3ubuntu5.5~cloud0
---
libvirt (2.5.0-3ubuntu5.5~cloud0) xenial-ocata; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
libvirt (2.5.0-3ubuntu5.5) zesty; urgency=medium
.
* d/p/bug-1708305-qemu-Fix-memory-locking-
This bug was fixed in the package libvirt - 1.3.1-1ubuntu10.14~cloud0
---
libvirt (1.3.1-1ubuntu10.14~cloud0) trusty-mitaka; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
libvirt (1.3.1-1ubuntu10.14) xenial; urgency=medium
.
* d/p/bug-1708305-qemu-Fix-memory-
Qemu bug report - bug 1701449
** Also affects: ceph (Ubuntu)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu i
Marking this as 'Medium' for now - we may want to bump that to 'High';
right now we have a reproducer in the context of qemu/librbd but not
directory with librbd which indicates this is a qemu specific issue.
** Summary changed:
- memory overhead of qemu-kvm and ram-allocation-ratio=0.9 leads to
Raising bug tasks for distro packages alongside the charm bug.
** Changed in: charm-nova-cloud-controller
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/167
Marking charm bug as invalid as this is an issue with librbd or qemu,
not the charm itself.
** Changed in: ceph (Ubuntu)
Importance: Undecided => Medium
** Changed in: qemu (Ubuntu)
Importance: Undecided => Medium
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
** Changed in
Marking charm task as invalid as this is a application issue.
** Changed in: charm-percona-cluster
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1713778
T
1 - 100 of 6263 matches
Mail list logo