** Changed in: charm-ceph-osd
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/2064717
Title:
ceph-volume needs "packaging" module
To manage notifications
** Changed in: charm-ceph-osd/reef
Assignee: (unassigned) => Felipe Reyes (freyes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064717
Title:
ceph-volume needs "packaging" modu
** Also affects: charm-ceph-osd
Importance: Undecided
Status: New
** Also affects: charm-ceph-osd/reef
Importance: Undecided
Status: New
** Changed in: charm-ceph-osd
Status: New => Fix Committed
** Changed in: charm-ceph-osd
Assignee: (unassigned) => Peter
** Changed in: cloud-archive/victoria
Status: New => Won't Fix
** Changed in: cloud-archive/wallaby
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064190
mportance: Undecided
Status: New
** Affects: cloud-archive/victoria
Importance: Undecided
Status: New
** Affects: cloud-archive/wallaby
Importance: Undecided
Status: New
** Affects: magnum (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects:
** Also affects: charm-nova-compute/zed
Importance: Undecided
Status: New
** Also affects: charm-nova-compute/2023.2
Importance: Undecided
Status: New
** Also affects: charm-nova-compute/yoga
Importance: Undecided
Status: New
** Also affects:
Marking magnum-ui (upstream) as invalid since this is an issue found in
the ubuntu focal archive.
** Changed in: magnum-ui
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: magnum-ui (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/205
Title:
Cluster Resize is failing in UI
To manage notifications
On Horizon I was able to launch an instance with a floating ip and
navigate across the different panels with no problem.
ubuntu@freyes-bastion:~$ juju ssh openstack-dashboard/0 apt policy
openstack-dashboard
openstack-dashboard:
Installed: 4:20.1.2-0ubuntu1~cloud0
Candidate:
I was able to run successfully charmed-openstack-tester (tox -e func-
target -- focal-xena) for the Xena UCA, here it's the list of packages
used by the testing bed.
ubuntu@freyes-bastion:~$ juju ssh neutron-api/0 apt policy neutron-common
neutron-common:
Installed: 2:19.2.0-0ubuntu1~cloud0
On Wed, 2022-05-11 at 19:13 +, Lucas Kanashiro wrote:
> Thanks for working with upstream to fix this. Would you be willing to
> backport this fix to Jammy? Or do you prefer me to do it?
I can propose the SRU (via debdiff) if you can sponsor it :-)
>
> For Kinetic we will be moving to the
ppa with the fix proposed at
https://github.com/ClusterLabs/crmsh/pull/972 for testing purposes
available at https://launchpad.net/~freyes/+archive/ubuntu/lp1972730
** Changed in: charm-hacluster
Status: New => Invalid
--
You received this bug notification because you are a member of
The way this error is exposed in the hacluster is when running the
`stop` hook:
unit-hacluster-1: 16:53:41 DEBUG juju.worker.uniter.runner starting jujuc
server {unix @/var/lib/juju/agents/unit-hacluster-1/agent.socket }
unit-hacluster-1: 16:53:41 INFO unit.hacluster/1.juju-log Setting node
Public bug reported:
Pacemaker changed the output string of "crmadmin -S " in 2.1.0
with the commit
https://github.com/ClusterLabs/pacemaker/commit/c26c9951d863e83126f811ee5b91a174fe0cc991
, this is different from the ouput that wait4dc() expects
** Description changed:
[Impact]
This release comes with bug fixes that we would like to make available
to our users.
The following packages come in this set of point releases:
* neutron 19.2.0
* nova 24.1.0
+ * cinder 19.1.0
[Test Case]
The following SRU process was
** Merge proposal linked:
https://code.launchpad.net/~freyes/ubuntu/+source/neutron/+git/neutron/+merge/421764
** Merge proposal linked:
https://code.launchpad.net/~freyes/ubuntu/+source/neutron/+git/neutron/+merge/421763
--
You received this bug notification because you are a member of
Public bug reported:
[Impact]
This release comes with bug fixes that we would like to make available
to our users.
The following packages come in this set of point releases:
* neutron 19.2.0
* nova 24.1.0
[Test Case]
The following SRU process was followed:
** Changed in: charm-mysql-router
Milestone: None => 22.04
** Changed in: charm-mysql-router
Assignee: (unassigned) => Felipe Reyes (freyes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
From a charm's perspective, I believe we should be setting
[DEFAULT].unknown_config_option to "warning", so (possible) future
changes in this area won't break a running cluster.
From the docs
worth to mention that the [DEFAULT].name key is set by "mysqlrouter
--bootstrap" and not by the charm, more details at
https://bugs.launchpad.net/charm-mysql-router/+bug/1907250/comments/10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm seeing this error:
2022-05-03 22:04:39 io INFO [7f91c2e53e00] starting 8 io-threads, using backend
'linux_epoll'
2022-05-03 22:04:39 main ERROR [7f91c2e53e00] Error: option 'DEFAULT.name' is
not supported
The error can be reproduced using this bundle
http://paste.ubuntu.com/p/mdY9dJhktH/ +
hello all,
I was able to validate successfully the packages available in the
-proposed pocket, specifically the following versions were installed in
the cloud deployed:
~/sources/ubuntu/lp1962582 $ grep ceilometer-common *.dpkg
machine-23.dpkg:ii ceilometer-common
in: nova (Ubuntu)
Assignee: Felipe Reyes (freyes) => (unassigned)
** Changed in: nova (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904580
** Changed in: charm-nova-compute
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/1904580
Title:
Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open
To manage
** Changed in: nova (Ubuntu)
Assignee: (unassigned) => Felipe Reyes (freyes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904580
Title:
Permissions 0644 for '/var/lib/nova/.ssh/id_
*** This bug is a duplicate of bug 1904580 ***
https://bugs.launchpad.net/bugs/1904580
hello everyone, thanks for reporting this bug, I'm going to mark this
bug as duplicate of https://bugs.launchpad.net/charm-nova-
compute/+bug/1904580 since it tracked the analysis and workarounds.
** This
** Patch added: "lp1966512_jammy.patch"
https://bugs.launchpad.net/ubuntu/+source/python-magnumclient/+bug/1966512/+attachment/5573002/+files/lp1966512_jammy.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
n
is 60 minutes.\n' does not match /.*?^Optional arguments:/
** Affects: python-magnumclient (Ubuntu)
Importance: Undecided
Assignee: Felipe Reyes (freyes)
Status: New
** Changed in: python-magnumclient (Ubuntu)
Assignee: (unassigned) => Felipe Reye
** Patch added: "lp1966442_jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-os-win/+bug/1966442/+attachment/5572999/+files/lp1966442_jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: python-os-win (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-os-win (Ubuntu)
Assignee: (unassigned) => Felipe Reyes (freyes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Public bug reported:
[Impact]
Users will get the latest stable bug fixes for this release of
OpenStack. Point releases included in this SRU:
ceilometer 17.0.1,
heat 17.0.1
horizon 20.1.1
[Test Case]
Testing of point releases for OpenStack packages is covered by:
** Changed in: charm-ironic-conductor
Milestone: None => 22.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943765
Title:
ipmitool "timing" flags are not working as expected causing failure
Hi Frode,
I went through the captures I have and effectively, if we filter out the
packets where the srcport != 53 or dstport != 6081 , we end up only with
valid dns traffic.
I believe this explains what we are seeing, and the other findings you
did regards the missing flows, we can say with
I have a capture using `tshark -i bond0 port 53` and I have a couple of
streams that exhibit this issue, I would like to highlight this one in
particular:
$ tshark -x -r dns-port-machine-10.pcap "udp.stream eq 9" | pastebinit
https://paste.ubuntu.com/p/yS74KCG2bY/
$ tshark -Tfields -e udp.port -e
An older capture:
[...]
.?.V...#[...
8.0.27-0ubuntu0.20.04.1...%..D/D).1[.[g=WEU(.K_.caching_sha2_password..@eX...$..>M'...>.t...E.@.@.KG...f..t
.?.V...#[...
Something I saw in a new data capture was when I made wireshark to
display the conversation of the stream that was showing "Unknown
operation (12)" packets, it displayed this:
[...]
..O...p<...a_.q.U.
...@..J.[...
here is an example on how to reuse config.rendered flag
https://github.com/openstack/charm-manila/blob/b75e6ed3ce6b2c061105ac8226a778e1ec3685d4/src/reactive/manila_handlers.py#L178
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We discussed this issue with the team and the agreement is that the
charm should disable/mask the service until the configuration has been
rendered, this is a pattern already used in other charms. For the
reactive charms there is a handler for this -
https://github.com/openstack/charm-layer-
** Bug watch added: github.com/systemd/systemd/issues #12841
https://github.com/systemd/systemd/issues/12841
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959847
Title:
Unknown operation (12)
On Tue, 2022-02-08 at 15:11 +, Frode Nordahl wrote:
> Thank you for your bug report, I wonder if this proposed fix [0] could
> be related?
I don't believe so, IIUC this would affect how the replies are
assembled and passed to the guest. I was looking at a similar issue (RR
counters) on the
Checking designate/2.
~/Downloads/f1badd08-a9a6-405a-b0be-d7f49ece023c/designate_2 $ tail
var/log/designate/designate-mdns.log -n 2
2021-04-19 16:04:24.389 64928 ERROR designate
oslo_db.exception.CantStartEngineError: No sql_connection parameter is
established
2021-04-19 16:04:24.389 64928 ERROR
syslog from a VM where some dns queries failed with ETIMEDOUT, e.g.
Feb 2 15:56:08 juju-6c8a68-zaza-1e093df25cbd-7 systemd-resolved[1352]:
Transaction 55701 for on scope dns on ens3/*
now complete with from none (unsigned).
** Attachment added: "syslog"
Public bug reported:
There have been DNS issues while running CI jobs for the openstack
charms, when I captured the dns traffic in one of the nova-compute
units[0][1], it can be seen how certain queries are malformed:
~ $ tshark -r dns-port-53.pcap | grep -i malformed | tail -n 2
15403
The fix for this bug will be available in neutron-19.1.0 which at the
moment is available in the -proposed pockets for Impish and Xena, more
details on the progress of the point release can be found at
https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1956991
--
You received this bug
Marking jammy as fix committed since package
neutron_19.0.0+git2022010514.7aba1bddab-0ubuntu1[0] contains the fix
that was merged in upstream[1]
[0]
https://launchpad.net/ubuntu/+source/neutron/2:19.0.0+git2022010514.7aba1bddab-0ubuntu1
[1]
** Patch added: "lp1951841_impish.debdiff"
https://bugs.launchpad.net/charm-ovn-chassis/+bug/1951841/+attachment/5552146/+files/lp1951841_impish.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+
+ When the ovn-controller daemon elects a new leader is expected that
+ clients reconnect to that new instance, for the case of Xena the
+ reconnect attempt will also call register_metadata_agent()[0] and this
+ method enforces that OVS system-id is formatted
** Changed in: neutron (Ubuntu Impish)
Assignee: (unassigned) => Felipe Reyes (freyes)
** Changed in: neutron (Ubuntu Impish)
Status: New => Triaged
** Summary changed:
- ovn metadata agent randomly timing out
+ [SRU] ovn metadata agent randomly timing out
--
You received th
- Marking charm-ovn-chassis as invalid since the issue is in neutron itself and
not the charm or how it drives the workload.
- Adding tasks for Ubuntu/Impish and cloud-archive/xena.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This change[0] was merged in stable/xena, this relaxes the check that
ovs system-id must be a uuid formatted string, now when it can't parse
it as a uuid it will (re)generate a uuid using uuid.uuid5(), which will
use as input a hardcoded UUID (as namespace) and the chassis name
string.
[0]
Public bug reported:
According to this bug[0] and these patches[1][2][3] the support to emit
a ICMP "need to fragment" packet was added in ovn-21.09, Wallaby UCA
carries ovn-20.12
This limitation becomes a problem when the overlay network is configured
to use jumbo frames and the external
** Changed in: charm-neutron-gateway
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/1944424
Title:
AppArmor causing HA routers to be in backup state on wallaby-focal
To
** Also affects: ironic (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/1943765
Title:
ipmitool "timing" flags are not working as expected causing
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874719
Title:
Focal/Groovy deploy creates a 'node1' node
To manage notifications about this bug go to:
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219
Title:
context deadline exceeded: unknown in containerd with latest runc
version
To manage notifications about this bug
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783184
Title:
neutron-ovs-cleanup can have unintended side effects
To manage notifications about this bug go to:
** Changed in: maas
Assignee: Felipe Reyes (freyes) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880495
Title:
Upgrade from 1.95 to 2.35 failure because col
Hi,
This is a workaround you can use temporarily:
$ wget -O- http://ddebs.ubuntu.com/dbgsym-release-key.asc | sudo apt-
key add -
$ sudo apt update
The key was extended temporarily.
Best,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
The public key used by the debugging symbols repository
/usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu-
dbgsym-keyring expired.
$ apt policy ubuntu-dbgsym-keyring
ubuntu-dbgsym-keyring:
Installed: 2020.02.11.2
Candidate: 2020.02.11.2
Version
To test this I deployed a Focal based CDK environment, then launched a
machine running groovy and scp'ed /root from kubernetes-master/0 to that
new machine and executed sosreport, the verification executed correctly.
Here it's the evidence.
Before the patch:
root@juju-321ff4-k8s-11:~# cat
Flannel doesn't like to be installed in groovy, I will need to give some
extra cycles to this verification.
unit-flannel-2: 15:59:56 INFO unit.flannel/2.juju-log Invoking reactive
handler: reactive/flannel.py:228:set_flannel_version
unit-flannel-2: 15:59:56 ERROR unit.flannel/2.juju-log Hook
I tested the package available in focal-proposed, and it could capture
correctly information that before the patch couldn't, for example:
Before the patch:
root@juju-867473-k8s-4:~# cat
On Sat, 2021-02-06 at 16:01 +, Eric Desrochers wrote:
> @freyes,
>
> Can you please fill the SRU template ? And I'll proceed with the
> sponsoring along with all the other patches waiting for SRU.
done ;-)
** Description changed:
+ [Impact]
+
+ Running sosreport in a CDK deployed
Adding a task for libvirt at Ubuntu/focal since this patch[0] might need
to be backported.
[0]
https://github.com/libvirt/libvirt/commit/ae9e6c2a2b75d958995c661f7bb64ed4353a6404
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Focal)
Just some history, in the past we attempted to disable unattended-
upgrades (as a config option) in the hacluster charm, but it was decided
that it wasn't the right place to get this addressed.
Bug https://bugs.launchpad.net/charm-hacluster/+bug/1826898
** Tags added: sts
--
You received this
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899455
Title:
[SRU] openvswitch 2.12.1
To manage notifications about this bug go to:
Public bug reported:
Extend the rabbitmq plugin to include the output of:
sudo rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().'
This information is useful to get insights of the state of the erlang
virtual machine.
** Affects: sosreport (Ubuntu)
Importance: Undecided
Status:
Attaching debdiff for focal that contains a backport of commit
https://github.com/sshuttle/sshuttle/commit/9c873579348e3308123d1bf2a917b0c2f82b9dae
** Patch added: "lp1873368_focal.debdiff"
I created a ppa that contains the backported patch in case anyone wants
to test it - https://launchpad.net/~freyes/+archive/ubuntu/lp1873368
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
** Changed in: maas
Assignee: (unassigned) => Felipe Reyes (freyes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880495
Title:
Upgrade from 1.95 to 2.35 failure because col
I could reproduce this issue locally, and this is what I believe is
happening with this environment (and not for other upgrades) is that the
database has no domains defined for the interfaces related, so this
piece of code [0] is falling into the "else" section which calls
get_default_domain()
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802407
Title:
ssl_ca not supported
To manage notifications about this bug go to:
** Also affects: simplestreams (Ubuntu Bionic)
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/1802407
Title:
ssl_ca not supported
To manage notifications
** No longer affects: neutron
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862836
Title:
neutron-fwaas Percona-XtraDB-Cluster prohibits use of DML command on a
table
This error is similar to the one reported in Octavia
https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1826875 , but in
the case of neutron the table firewall_group_port_associations_v2 has a
primary key defined:
firewall_group_port_associations_v2 | CREATE TABLE
I think the charm is the one responsible of disabling chrony, something
like this would do the trick.
if is_container():
subprocess.check_call("sudo timedatectl set-ntp off")
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: sts
--
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 to auto-
install even on lxd
To manage notifications
taking a look closer, this could have happened since the neutron-gateway
(server side) had an older version that is not aware of 1.5 objects,
while neutron-ovs-agent (client side) requested a 1.5 versioned object,
the backwards compatibility layer is meant to be used the other way
around where the
According to the comments in https://review.opendev.org/#/c/669360/ the
backport mentioned earlier shouldn't have broken things.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859649
Title:
neutron
About "neutron.agent.rpc oslo_messaging.rpc.client.RemoteError: Remote
error: InvalidTargetVersion Invalid target version 1.5"
commit b452c508b62 landed in 14.0.3 which bumped up the Port object's
version to 1.5 making it incompatible with older versions ->
verified xenial-queens, no regressions detected, testing journal:
$ time tox -e func-smoke
func-smoke installed: DEPRECATION: Python 2.7 will reach the end of its life on
January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained
after that date. A future version of pip
@Corey, verification done ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782922
Title:
LDAP: changing user_id_attribute bricks group mapping
To manage notifications about this bug go to:
I went through the test case using the package available in -proposed
and everything worked fine, no regressions were detected when using
keystone neither.
Here it's the journal of my testing.
$ time tox -e func-smoke
func-smoke installed: DEPRECATION: Python 2.7 will reach the end of its life
tested the package that fixes this bugfollowing the instructions at
https://launchpadlibrarian.net/449185359/bug-1782922-testing.txt,
everything works ok, and no regressions were detected.
testing bed log:
$ tox -e func-smoke
func-smoke installed: DEPRECATION: Python 2.7 will reach the end of
I tested the fix for this code following the instructions at
https://launchpadlibrarian.net/449185359/bug-1782922-testing.txt and
everything works ok, and no regressions were detected.
testing bed log:
$ tox -e func-smoke
func-smoke installed: DEPRECATION: Python 2.7 will reach the end of its
Hello Corey,
I was trying to verify the SRU that it's in disco-proposed without success.
IIUC, the commands "openstack user list" and "openstack group list" should fail
when the package installed is 2:15.0.0-0ubuntu1.1 , here is the output of my
terminal, could you help me understand if I'm doing
I prepared a ppa for testing purposes, if someone is interested in
giving it a try please report back on how it works for you -
https://launchpad.net/~freyes/+archive/ubuntu/lp1829987
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
do-release-upgrade in this aspect have 2 modes: server and desktop mode,
the desktop mode is used whenever any of the packages defined in the
MetaPkgs[0] section is installed[2]
So when server mode is detected is when the presence of packages defined
in BaseMetaPkgs is NOT enforced[1]
[0]
*** This bug is a duplicate of bug 1710278 ***
https://bugs.launchpad.net/bugs/1710278
** This bug has been marked a duplicate of bug 1710278
[2.3a1] named stuck on reload, DNS broken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
I've been analyzing an environment that it's issuing too many times
"rndc reload" which eventually leads to the same symptoms seen in bug
1710278 , these are the numbers when the operator attempted to
commission a bit more than 50 machines at the same time.
In regiond.log*
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823718
Title:
Installation fails with Python3.7 SyntaxError on Ubuntu Disco
To manage notifications about this bug go to:
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816721
Title:
[SRU] Python3 librados incompatibility
To manage notifications about this bug go to:
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819453
Title:
keystone-ldap TypeError: cannot concatenate 'str' and 'NoneType'
object
To manage notifications about this bug go
On Tue, 2019-03-05 at 18:30 +, Corey Bryant wrote:
> @Jeremy, I think it's more of limited denial of service (if we can
> call
> it that) where a certain amount of computes could get negative weight
> and not considered for scheduling. I don't think it's a complete
> denial
> of service.
I
** Description changed:
[Impact]
currently the glance mirror requires hypervisor_mapping config in the api.
Better to not required that as a library consumer would not necessarily
provide it.
[Test Case]
- * deploy a openstack environment with keystone v3 enabled
- - get a copy
** Description changed:
+ [Impact]
currently the glance mirror requires hypervisor_mapping config in the api.
Better to not required that as a library consumer would not necessarily
provide it.
+
+ [Test Case]
+
+ * deploy a openstack environment with keystone v3 enabled
+ - get a copy
** Also affects: netplan
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/1815101
Title:
netplan removes keepalived configuration
To manage notifications
does anyone have a reproducer for this bug?, I've been having a hard
time trying to come up with one on my own.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686086
Title:
glance mirror and
for people being hit by this bug, it would be helpful if you could
generate a core file while rabbit is still stuck, this may give us some
insights of where the process is looping.
$ sudo gcore -o lp1783203.core $PID
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783203
Title:
Upgrade to RabbitMQ 3.6.10 causes beam lockup in clustered deployment
To manage notifications about this bug go to:
1 - 100 of 479 matches
Mail list logo
