Have completed verification on Groovy too.
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
)
Importance: Undecided
Status: Fix Released
** Affects: ovn (Ubuntu Focal)
Importance: High
Assignee: Frode Nordahl (fnordahl)
Status: In Progress
** Changed in: ovn (Ubuntu)
Status: New => In Progress
** Changed in: ovn (Ubuntu)
Status: In Progr
** Also affects: ovn (Ubuntu Hirsute)
Importance: Undecided
Status: Fix Released
** Also affects: ovn (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: ovn (Ubuntu Groovy)
Status: New => Fix Released
--
You received this bug notification because you are
Hello Dan,
> It looks to me like these two statements are in opposition: if OVS is
> managing an interface via a different datapath, then it won't have
> ID_NET_DRIVER=openvswitch in its `udevadm info`.
>
> If this is the case, then I think we have a couple of options.
That is correct, I rememb
> The next question is exactly which interfaces we should be excluding from the
> set of interfaces we consider. At the moment, my POC is excluding interfaces
> whose name matches an OVS bridge, determined via `ovs-vsctl list-br`. In an
> instance with an additional VLAN to the above configurati
> Another question: is there a canonical way to determine if OVS isn't
up? Currently I'm trying to execute a command and looking for "database
connection failed" in the output, is that appropriate?
In the Ubuntu systemd service we assess the database socket:
https://git.launchpad.net/~ubuntu-serve
ort being immediately updated and
the floating IP can be accessed.
** Changed in: ovn (Ubuntu)
Status: New => In Progress
** Changed in: ovn (Ubuntu)
Importance: Undecided => High
** Changed in: ovn (Ubuntu)
Assignee: (unassigned) => Frode Nordahl (fnordahl)
--
You re
https://patchwork.ozlabs.org/project/ovn/patch/20210302172353.1020143-1-frode.nord...@canonical.com/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917475
Title:
RBAC Permissions too strict for Port
Thanks for digging that up, does look relevant for sure. The linked
review appears to be backported to Ussuri already, and it is in the
neutron 16.3.2 point release (released 10 days ago). So we'll get that
in Ubuntu on the next point release update to the neutron package.
** Also affects: neutron
$ juju run --unit ovn-chassis/0 'ovs-vsctl remove open-vswitch . external-ids
hostname'
$ juju run --unit ovn-chassis/0 'sudo shutdown -r now'
$ juju run --unit ovn-chassis/0 'ovs-vsctl remove open-vswitch . external-ids
hostname'
$ juju run --unit ovn-chassis/0 'sudo shutdown -r now'
$ juju run
Terry, while I'd love it if Neutron had completed the migration to using
OVN services and database for everything as a replacement for the AMQP
RPC and agent infrastructure, the reality is that this is not (yet) the
case.
For the SR-IOV use case the OVN driver owns ports and provides DHCP- and
Met
With the gate job for the Octavia charm I deployed a bionic-ussuri cloud
with the currently released packages (Note that the amphora image was
built with focal pending resolution of bug 1895835).
I can confirm that the test fails with not being able to reach the FIP:
--2021-06-11 07:33:28-- http:
>From within Amphora:
# cat /var/log/amphora-agent.log
[2021-06-11 13:58:57 +] [1268] [DEBUG] Current configuration:
config: None
bind: ['[::]:9443']
backlog: 2048
workers: 1
worker_class: sync
threads: 1
worker_connections: 1000
max_requests: 0
max_requests_jitter: 0
timeo
** Changed in: octavia (Ubuntu)
Status: New => Invalid
** Changed in: snap-octavia-diskimage-retrofit
Status: New => 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/1928179
** Changed in: snap-octavia-diskimage-retrofit
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/1928179
Title:
[Victoria] Amphora fails to plug vip
To mana
With the gate job for the neutron-api-plugin-ovn charm I deployed a
Focal/Ussuri cloud using the currently released packages.
The test starts two instances and I have a ping going to each of them while
running these commands to upgrade to the in-proposed packages for both Open
vSwitch and OVN:
$
With the gate job for the neutron-api-plugin-ovn charm I deployed a
Groovy/Victoria cloud using the currently released packages.
The test starts two instances and I have a ping going to each of them while
running these commands to upgrade to the in-proposed packages for both Open
vSwitch and OVN
Thank you for pointing that out, Łukasz, I must have missed that.
I have investigated the artifacts from the build failure and it appears
to be a intermittent issue with the test itself, we have issued a
rebuild of the ppc64el package and that succeeded at first attempt.
I hope this will allow us
Thank you for adding the extended detail, Camille!
I would like to note that the fix for this is now in -proposed on Focal
and is just around the corner to be promoted to -updates. The SRU can be
tracked in bug 1924981.
--
You received this bug notification because you are a member of Ubuntu
Bug
$ juju run --unit ovn-chassis/0 'ovs-vsctl remove open-vswitch . external-ids
hostname'
$ juju run --unit ovn-chassis/0 'sudo shutdown -r now'
$ sudo ovs-vsctl list open-vswitch
...
external_ids: {hostname=juju-d4e71d-0-lxd-0,
rundir="/var/run/openvswitch", system-id="424e6f88-2e79-436f-9
Public bug reported:
The amphora agent will say:
2021-05-12 06:44:13.767 1318 INFO
octavia.amphorae.backends.health_daemon.health_daemon [-] Health Manager Sender
starting.
2021-05-12 06:44:22.418 1319 DEBUG
octavia.amphorae.backends.agent.api_server.osutils [-] b'' _bring_if_up
/usr/lib/pytho
Public bug reported:
New point release for OVN from the 20.03 branch which we track in Ubuntu
Focal.
** Affects: cloud-archive
Importance: Undecided
Status: Invalid
** Affects: cloud-archive/ussuri
Importance: Undecided
Status: New
** Affects: ovn (Ubuntu)
Impor
Public bug reported:
New point release for OVN from the 20.03 branch which we track in Ubuntu
Groovy.
** Affects: ovn (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: ovn (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: ovn (Ubuntu Groovy)
Backports are on the way here:
https://review.opendev.org/q/256ed3b72fa5b2a8030814e9e6cf299a887ea9b7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931244
Title:
ovn sriov broken from ussuri onwards
ded
Status: New
** Also affects: ovn (Ubuntu Impish)
Importance: High
Assignee: Frode Nordahl (fnordahl)
Status: Fix Committed
** Changed in: ovn (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: ovn (Ubuntu Groovy)
Status: New => Fix Released
*
** Changed in: ovn (Ubuntu)
Status: New => 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/1914988
Title:
IGMP Snooping does not work with RBAC enabled ovn-controllers
To manage
** Changed in: ovn (Ubuntu)
Status: Triaged => 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/1913024
Title:
RBAC Permissions too strict for Chassis_Private table
To manage noti
https://github.com/ovn-
org/ovn/commit/82a4e44e308171cb545211eb2534475ef16a4c0e
** Changed in: ovn (Ubuntu)
Status: Confirmed => 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/1857
** Summary changed:
- os-vif fails to get the correct UpLink Representor
+ Failure to get the correct UpLink Representor
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also af
** Changed in: python-os-vif (Ubuntu Groovy)
Status: New => In Progress
** Changed in: python-os-vif (Ubuntu Groovy)
Assignee: (unassigned) => Frode Nordahl (fnordahl)
** Changed in: python-os-vif (Ubuntu Focal)
Status: New => In Progress
** Changed in: python-os-vi
** Changed in: libvirt (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: libvirt (Ubuntu Hirsute)
Assignee: (unassigned) => Frode Nordahl (fnordahl)
** Changed in: libvirt (Ubuntu Groovy)
Status: New => In Progress
** Changed in: libvirt (Ubuntu Groovy)
** Description changed:
- Due to new kernel patch here [1], the PF and VF representors are linked
- to their parent PCI device.
+ [Impact]
+ An update to the mlx5_core driver [1] which will be made available to users
of stable releases both through HWE kernels and DKMS packages provided by
NVID
Public bug reported:
As reported and fixed in [0] if the node that is configured with an
empty ``--db-*-cluster-remote-addr`` is no longer the leader, the ovn-
ctl script will hang on startup.
Prior to the hang the script will successfully start the ovsdb-server,
but never get to the point where
Public bug reported:
After upgrading from linux-firmware 1.198 to 1.199 my connectivity
became unstable and I could see repeating hardware resets in `dmesg`
output.
Downgrading to linux-firmware 1.198 again resolved the issue.
Note: this bug was filed after downgrading the package, but hopefully
Attaching the kern.log from previous boot which shows the issues.
** Attachment added: "kern.log.1"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1937415/+attachment/5513187/+files/kern.log.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Apparently the kern.log just shows boot, adding syslog excerpt with the
kernel messages
** Attachment added: "syslog-excerpt.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1937415/+attachment/5513209/+files/syslog-excerpt.txt
--
You received this bug notification because
Circling back to this, I did make an attempt with linux-firmware 1.198
as base and then copying in just the firmwares that appeared relevant to
the hardware in question from 1.199. However I was no longer able to
reproduce the issue.
Now I have installed the 1.199 package again and I have had no i
** Merge proposal unlinked:
https://code.launchpad.net/~fnordahl/ubuntu/+source/ovn/+git/ovn/+merge/393441
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899369
Title:
ovn-controller: Disable of
** Description changed:
[Impact]
-
+ Service/host restart or upgrade of the ovn-host package may render a host
participating in a OVN network unusable as the ovn-controller process fails to
complete programming of the local Open vSwitch switch flows.
[Test Case]
-
+ The issue was discov
Verification done for Focal. Removed the workaround provided by the
`external-ids:ovn-openflow-probe-interval` key in the Open_vSwitch table
and installed the proposed package on a heavily loaded lab cluster and
confirmed continued operation with the new package.
** Tags removed: verification-need
Public bug reported:
When CMS configures ACLs with overlapping rules the flow rules OVN
programs into Open vSwitch may lead to unpredictable forwarding
behavior.
How to reproduce with OpenStack as CMS:
- Update the "default" group to accept ICMP, then:
openstack security group create a
op
Public bug reported:
In the systemd service we make use of the `ovn-ctl` script
`run_nb_ovsdb` and `run_sb_ovsdb` sub-commands introduced in [0]. These
sub-commands fit nicely with systemd's expectations of modern daemons to
no longer detachand run in the background.
However, the change in [0] ha
** Changed in: charm-ovn-central
Status: Triaged => In Progress
** Changed in: charm-ovn-central
Assignee: (unassigned) => Frode Nordahl (fnordahl)
** Summary changed:
- OVN database is not upgraded on package upgrade
+ Clustered OVN database is not upgraded on package u
** Changed in: ovn (Ubuntu)
Assignee: (unassigned) => Frode Nordahl (fnordahl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906922
Title:
Unpredictable behaviour on conflicting flow acti
** Changed in: ovn (Ubuntu)
Assignee: (unassigned) => Frode Nordahl (fnordahl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907081
Title:
Clustered OVN database is not upgraded on pack
** Changed in: ovn (Ubuntu)
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906922
Title:
Unpredictable behaviour on conflicting flow actions
To manage notifications
** Changed in: ovn (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906922
Title:
Unpredictable behaviour on conflicting flow actions
To manage notifica
** Changed in: ovn (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907081
Title:
Clustered OVN database is not upgraded on package upgrade
To manage no
ed) => Frode Nordahl (fnordahl)
** Changed in: ovn (Ubuntu Focal)
Assignee: (unassigned) => Frode Nordahl (fnordahl)
** Changed in: ovn (Ubuntu)
Status: In Progress => Triaged
** Changed in: ovn (Ubuntu)
Assignee: Frode Nordahl (fnordahl) => (unassigned)
--
You receiv
1) The 'No compute node record for host phanpy:
ComputeHostNotFound_Remote: Compute host phanpy could not be found.'
message is benign, this message appears on first start of the `nova-
compute` service. It keeps appearing in the log here due to failure to
register available resources. See 3)
2
** Attachment added: "libvirt-debug.log"
https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+attachment/5157735/+files/libvirt-debug.log
** Changed in: charm-nova-compute
Status: Incomplete => Invalid
** Also affects: nova
Importance: Undecided
Status: New
--
You re
Executive summary for kernel team:
What makes both libvirt and Nova unhappy about the Cavium Thunder X NIC is the
fact that they are denied with "Operation not supported" when attempting to
read from sysfs node phys_port_id from its virtual functions.
Example:
'/sys/devices/pci0003:00/0003:00:00
That is interesting indeed.
The difference being on other systems the virtual functions are by
default disabled which I guess is why no one is running into this
problem with other hardware.
An example from a system with the ixgbe driver:
# cat /sys/devices/pci\:00/\:00\:03.0/\:01\:00.
I can confirm that the octavia-dashboard package works, see attached
screen shot and steps provided below.
Steps for validation:
1) Deploy Octavia from tip charm
$ git review -d 614050
$ tox -e build
$ tox -c build/builds/octavia/tox.ini -e func-smoke --work-dir /tmp/tox
2) Deploy openstack-dashb
Quick addition for proof:
$ juju ssh openstack-dashboard/0 sudo -s
# dpkg -l | egrep "(neutron|octavia)"
ii python3-neutron-fwaas-dashboard 1.5.0-0ubuntu3~cloud0 all
OpenStack Firewall as a Service - dashboard plugin
ii python3-neutronclient1:6.7.0-0ubuntu1
Review: https://review.openstack.org/#/c/612253/
** Also affects: python-castellan (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/1799132
Title:
Public bug reported:
# octavia-db-manage upgrade head
2018-10-09 07:34:52.971 11688 CRITICAL octavia-db-manage [-] Unhandled error:
AttributeError: 'NoneType' object has no attribute '_instantiate_plugins'
2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage Traceback (most recent
call last):
2
** Description changed:
# octavia-db-manage upgrade head
2018-10-09 07:34:52.971 11688 CRITICAL octavia-db-manage [-] Unhandled error:
AttributeError: 'NoneType' object has no attribute '_instantiate_plugins'
2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage Traceback (most recent
call
Indeed, my configuration did have the database configuration per se, but
it was in the wrong section. Thank you for the pointer!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796811
Title:
octavia
Public bug reported:
root@direct-tiger:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Disco Dingo (development branch)
Release:19.04
Codename: disco
root@direct-tiger:~# apt update && apt -y install python3-libmaas
[ snip ... ]
Setting u
Note that ``python3-libmaas`` is a dependency of ``charm-hacluster``,
which means HA deployments of Ubuntu OpenStack are currently not
possible on Ubuntu Disco.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Public bug reported:
# sudo octavia-db-manage upgrade head
2019-04-08 13:57:50.232 23647 CRITICAL octavia-db-manage [-] Unhandled error:
ModuleNotFoundError: No module named 'MySQLdb'
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage Traceback (most recent
call last):
2019-04-08 13:57:50.232
It appears the issue here is that we have been carrying a patch in UCA
that adds ``+pymysql`` to the connection string.
That has been removed in UCA @ Stein, so we would have to add this back.
The connection string comes from here [0] and variables come from [1]
and [2].
We would also need to ve
** Also affects: layer-openstack
Importance: Undecided
Status: New
** Changed in: layer-openstack
Status: New => Triaged
** Changed in: layer-openstack
Importance: Undecided => Critical
** Changed in: layer-openstack
Assignee: (unassigned) => Frode Nordahl
** Changed in: layer-openstack
Status: Triaged => In Progress
** Changed in: charms.openstack
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823729
Title:
** Changed in: charms.openstack
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823729
Title:
Incorrect dependency at Stein
To manage notifications about this b
** Changed in: layer-openstack
Status: In Progress => 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/1823729
Title:
Incorrect dependency at Stein
To manage notifications about th
Public bug reported:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename: bionic
summary: there appear to be a set of packages with dependencies
explicitly pointing @ =13.2.1+dfsg1-0ubuntu3~cloud0 while the
Public bug reported:
The on-going work to wean OVN off of the `openvswitch-switch` package is
great, however it appears we're mising the `ovsdb-tool` binary.
Feb 18 06:46:15 juju-e5e5a4-zaza-0bd44e19b938-4 ovn-ctl[14536]:
/usr/share/ovn/scripts/ovn-ctl: 401: /usr/share/ovn/scripts/ovn-ctl:
ovsd
Public bug reported:
Example log messages:
bridge not found for localnet port
'provnet-9d4a9910-01c3-4fe3-bae3-0d93dc6c9b69' with network name 'physnet1'
Filing here for tracking and for pointing anybody hitting it to the patch.
There is a pattern among CMSes to create a `localnet` port
bindi
https://review.openstack.org/#/c/648618/
** Changed in: charm-ceph-rbd-mirror
Status: New => In Progress
** Changed in: charm-ceph-rbd-mirror
Importance: Undecided => Medium
** Changed in: charm-ceph-rbd-mirror
Assignee: (unassigned) => Frode Nordahl (fnordahl)
--
You
Public bug reported:
Running $ gnocchi status --debug
REQ: curl -g -i -X GET http://10.5.0.38:5000/v3 -H "Accept: application/json"
-H "User-Agent: gnocchi keystoneauth1/3.10.0 python-requests/2.18.4
CPython/3.6.7"
Starting new HTTP connection (1): 10.5.0.38
http://10.5.0.38:5000 "GET /v3 HTTP/1
Downgrading the ceph packages to 12.2.7 resolves the issue and gnocchi
status succeeds
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813582
Title:
Update to 12.2.8 leads to SIGSEGV Segmentation fau
I can confirm that using the packages from PPA mentioned in #4 solves
the issue for Bionic:
$ tox -c build/builds/gnocchi/tox.ini -e func27-smoke --workdir /tmp/tox
func27-smoke installed: DEPRECATION: Python 2.7 will reach the end of its life
on January 1st, 2020. Please upgrade your Python as P
DEBUG:runner:2019-01-31 14:44:29 Deployment complete in 606.56 seconds
DEBUG:runner:2019-01-31 14:45:34,400 __init__ INFO: Waiting on extended status
checks...
DEBUG:runner:2019-01-31 14:45:34,402 _auto_wait_for_status INFO: Waiting for
extended status on units for 5400s...
DEBUG:runner:2019-01-3
Unfortunately I am seeing this in Cosmic (and subsequently the Rocky
UCA).
https://openstack-ci-
reports.ubuntu.com/artifacts/test_charm_pipeline_func_full/openstack
/charm-gnocchi/634259/1/2558/consoleText.test_charm_func_full_5020.txt
** Changed in: ceph (Ubuntu Cosmic)
Status: Fix Relea
Amendment to comment #14, the test was executed on bionic-rocky UCA
which strictly speaking is not Cosmic. There might be other things at
play here, setting back to Fix Released for Cosmic
** Changed in: ceph (Ubuntu Cosmic)
Status: New => Fix Released
--
You received this bug notificati
Public bug reported:
Octavia have support for multiple provider drivers. To be able to use
non-builtin provider drivers one needs to run the ``octavia-driver-
agent`` service on the Octavia units.
The package currently does not contain this init script.
A working example is shipped with the cha
Public bug reported:
root@juju-c9e7e0-4:/etc# dpkg -l keystone
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Example of charm deploy on focal not coping with the change in https
://openstack-ci-
reports.ubuntu.com/artifacts/test_charm_pipeline_func_smoke/openstack
/charm-ceph-radosgw/714400/7/15452/index.html
Essentially the charm executes ``sudo -u keystone keystone-manage
fernet_setup`` and that fails
Public bug reported:
Something changed between ceph 15.1.x and ceph 15.2.x which prohibits
civetweb from binding to ports < 1024.
The packages have been running ceph radosgw as a non-root user since
forever, so I'm not quite sure what changed where, so this is mainly a
bug to track what may very
Yes, that resolved the issue, thank you @corey!
root@juju-ae56ef-0:~# dpkg -s keystone
Package: keystone
Status: install ok installed
Priority: extra
Section: python
Installed-Size: 31
Maintainer: Ubuntu Developers
Architecture: all
Version: 2:17.0.0~b3~git2020032415.9f9040257-0ubuntu2
root@juju
** Patch removed: "rsyslog-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900262/+files/rsyslog-trusty.debdiff
** Patch removed: "rsyslog-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4901471/+files/r
** Patch added: "rsysog-artful.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4903402/+files/rsysog-artful.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Patch removed: "rsysog-artful.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4903402/+files/rsysog-artful.debdiff
** Patch added: "rsysog-artful.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4903910/+files/rsysog
I can confirm that the proposed ubuntu-fan package resolves the issue.
If you are deploying with Juju and MaaS the Ubuntu proposed repository
can be installed automatically on the nodes deployed by MaaS. This could
be used as a temporary workaround for the issue.
Example for how it could be set u
Following previous discussions and proposals I understand there are some
issues with getting 'squashfuse' installed automatically for container
workloads.
In the meantime, for improved UX, would having "snap install" command
inform operator of 'squashfuse' dependency for in-container operation be
I'm seeing this too, so far it has not rendered my system unbootable
though.
I have been running with ZFS as root filesystem since Bionic and have
upgraded through Disco and the issue first appeared in an update
arriving after upgrading to Eoan.
Setting up zfsutils-linux (0.8.1-1ubuntu10) ...
zfs
A workaround to get the dependencies installed on upgrade would be:
$ sudo systemctl mask zfs-mount
$ sudo apt -f install
$ sudo systemctl unmask zfs-mount
After a reboot the ``zfs-mount`` service stays in a failed state, I wonder if
something else has taken on its duties and there is a conflic
Public bug reported:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
Codename: eoan
After the recent update of libc and locale packages to 2.30 I'm
experiencing issues on my developer worksta
$ locale
LANG=en_US.UTF-8
LANGUAGE=en
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=en_US.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=en_US.UTF-8
LC_NAME=en_US.UTF-8
LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=en_US.UTF-8
LC_I
I guess so, it may be the bug sources from somewhere else in the
ecosystem and that some package has to cope with the changes to make the
system not change behavior on upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Public bug reported:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
Codename: eoan
$ dpkg -l |grep gnome-control-center
ii gnome-control-center 1:3.33.90-1ubuntu2
$ cat /etc/default/locale
LANG=en_US.UTF-8
LANGUAGE=en_US
$ cat .pam_environment
LANGUAGEDEFAULT=en
LANGDEFAULT=en_US.UTF-8
LC_NUMERIC DEFAULT=en_US.UTF-8
LC_TIME DEFAULT=en_US.UTF-8
LC_MONETARY DEFAULT=en_US.UTF-8
LC_PAPERDEFAULT=en_US.UTF-8
LC_NAME DEFAULT=en_US.UT
Public bug reported:
I am working on Juju Charms for deploying OVN.
At present the OVN components are distributed in the following binary
packages:
- ``ovn-common``
- CLI tools, man pages, scripts
- ``ovn-docker``
- Docker components
- ``ovn-host``
- Host components, the local c
** Changed in: charm-keystone-ldap
Milestone: 19.07 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832265
Title:
py3: inconsistent encoding of token fields
To manage notifications about
** Changed in: charm-designate
Milestone: 19.07 => None
--
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 "Services not
runni
Public bug reported:
1)
At present the ``amphora-agent`` package has a init script that points the
amphora-agent at ``/etc/octavia/octavia.conf``. However, the upstream Octavia
project will tell cloud-init to write the agent configuration to
``/etc/octavia/amphora-agent.conf``.
Upstream refer
For 3) the upstream project has the ``/var/log/amphora-agent.log`` path
hard-coded, ref:
https://opendev.org/openstack/octavia/src/branch/master/octavia/cmd/agent.py#L80
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Public bug reported:
A recent addition to upstream OVN will allow operators, and indeed
charms, to query a ovn-northd process whether it is in active or standby
mode.
It would be great to have this included in the Ubuntu package until the
next upstream release is cut if possible.
** Affects: ope
1 - 100 of 589 matches
Mail list logo
