xenial/ocata/proposed
Confirmed able to boot instances using the patched packages - console
and serial XML snippets LGTM:
$ apt-cache policy nova-compute
nova-compute:
Installed: 2:15.0.6-0ubuntu1~cloud0
Candidate: 2:15.0.6-0ubunt
Public bug reported:
Detected during testing of libvirt 3.6.0 and qemu 2.10~rc4 for Pike
Staging on Xenial; however Christian was able to reproduce this problem
using uvtool on Artful with the same libvirt/qemu versions.
See attached stacktrace for details.
** Affects: libvirt (Ubuntu)
Impo
** Changed in: nova-lxd
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxd in Ubuntu.
https://bugs.launchpad.net/bugs/1573681
Title:
conflict when managing LXD storage with Juju 2.0
To m
** Changed in: charm-nova-compute
Status: Fix Committed => Fix Released
--
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/1673467
Title:
[ocata] unsupported configuration: CPU mode
** Changed in: charm-nova-compute
Milestone: 17.08 => None
--
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/1657305
Title:
percona cluster getting wrong private ip
To manage notific
** Changed in: charm-lxd
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxd in Ubuntu.
https://bugs.launchpad.net/bugs/1573681
Title:
conflict when managing LXD storage with Juju 2.0
To
** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1718133
Title:
Live block migration in Pike fails due to qemu-
Pike UCA is in sync with Artful versions; I'm working to reproduce so we
can debug further.
--
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/1718133
Title:
Live block migration in Pike f
Marking qemu task as invalid - this is really a new feature that nova
needs to deal with.
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/pike
Importance: Undecided
Status: New
** Changed in: nova (Ubuntu)
Importance: Undecid
Nova/devstack bug 1718295
--
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/1718133
Title:
Live block migration in Pike fails due to qemu-img
To manage notifications about this bug go to
I've uploaded test packages to:
https://launchpad.net/~james-page/+archive/ubuntu/pike
The patch this includes will only work with qemu 2.10 as found in artful
and the Pike UCA; will need todo a larger patch for submission to Nova
to deal with multiple versions.
--
You received thi
** Changed in: nova (Ubuntu Artful)
Status: Triaged => In Progress
** Changed in: nova (Ubuntu Artful)
Assignee: (unassigned) => James Page (james-page)
** Changed in: cloud-archive/pike
Status: Triaged => In Progress
** Changed in: cloud-archive/pike
Distro patch to unblock Ubuntu Pike UCA and Artful (needs conditional
check for general consumption).
** Patch added: "qemu-2.10-compat.patch"
https://bugs.launchpad.net/nova/+bug/1718295/+attachment/4953632/+files/qemu-2.10-compat.patch
** Changed in: nova
Status: Invalid => New
--
Setting Nova bug task back to 'New' as I think we do need to accommodate
this behavioural change in qemu.
--
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/1718295
Title:
Live migration f
** Patch added: "qemu-2.10-compat.patch"
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1718133/+attachment/4953631/+files/qemu-2.10-compat.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.laun
Fix promoted to pike-proposed.
** Changed in: cloud-archive/pike
Status: In Progress => Fix Committed
--
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/1718133
Title:
Live block m
This bug was fixed in the package nova - 2:16.0.0-0ubuntu2~cloud0
---
nova (2:16.0.0-0ubuntu2~cloud0) xenial-pike; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
nova (2:16.0.0-0ubuntu2) artful; urgency=medium
.
* d/p/qemu-2.10-compat.patch: Compatibility patc
Verified nova update for pike using tempest live migration tests and
some manual exercising of live-migration including block-migration with
attached storage volumes from cinder (yikes!).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
The verification of the Stable Release Update for nova 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
Not a charm specific issue, so raising a bug task for the RMQ packages -
and marking the charm task as invalid.
** Changed in: charm-rabbitmq-server
Status: New => Invalid
** Changed in: rabbitmq-server (Ubuntu)
Status: New => Confirmed
** Changed in: rabbitmq-server (Ubuntu)
Im
Wedged erlang processes are a nightmare for this - we actually had a
script called the rabbit hammer that did what you describe above to
resolve a wedged, clustered rmq deployment.
** Also affects: rabbitmq-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug noti
I've seen this behaviour to confirming the bug and triaging as 'Medium'
** Changed in: rabbitmq-server (Ubuntu)
Status: Confirmed => 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
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
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 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
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
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-
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-
@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
** 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
** 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
** 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: 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: 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: 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: 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
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
@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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
** 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
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
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
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
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://
** 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
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-
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
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/
** 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
** 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.
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
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
** 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
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: 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
** 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
** 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
** 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
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
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
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
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
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
** 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
; 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
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
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
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
** 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
** 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
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
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
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:
** 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
** 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: 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
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,
@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
** 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
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
901 - 1000 of 5689 matches
Mail list logo