[Bug 1899369] Re: ovn-controller: Disable ofctrl probe by default
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.launchpad.net/bugs/1899369 Title: ovn-controller: Disable ofctrl probe by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1899369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905933] [NEW] Incorrect ARP processing when enable_distributed_floating_ip=True
Public bug reported: In a focal-ussuri deployment when enabling `enable-distributed-floating- ip` traffic from instances with FIPs should exit the HV directly and not go through a gateway chassis. However due to a bug each HV will attempt to do ARP processing locally even for IP addresses not in the external network CIDR. This results in loss of connectivity for instances with FIPs. The issue is not present in Groovy with OVN 20.06 and I suspect the issue is fixed by this commit: https://github.com/ovn-org/ovn/commit/d9ed450713eda62af1bec5009694b2d206c9f435 ** Affects: ovn (Ubuntu) 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 Progress => Fix Released ** Also affects: ovn (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ovn (Ubuntu Focal) Status: New => In Progress ** Changed in: ovn (Ubuntu Focal) Importance: Undecided => High ** Changed in: ovn (Ubuntu Focal) 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/1905933 Title: Incorrect ARP processing when enable_distributed_floating_ip=True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1905933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905933] Re: Incorrect ARP processing when enable_distributed_floating_ip=True
** 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 a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905933 Title: Incorrect ARP processing when enable_distributed_floating_ip=True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1905933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912844] Re: Bond with OVS bridging RuntimeError: duplicate mac found!
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 remembered the other datapath types after suggesting the driver approach. > Firstly, we could scope this down to only handle system datapath interfaces, so that it _is_ true that all the interfaces we're handling are owned by the openvswitch. I don't know enough about how OVS is used (either by us or more generally) to know if this is a reasonable suggestion, so your guidance would be appreciated. For the specific use case we're testing with right now it would be safe to assume the system datapath, however our product does also support the use of DPDK acceleration which is hinged on the netdev datapath. So I'm afraid leaving that out of scope might come back and bite us before we know it. But I guess it would be reasonable to split the work up in bite sized chunks as long as we allow for supporting this in the design. > If we can't do that, then I think we need to ask OVS directly, presumably via `ovs-vsctl show` as discussed above. This would require it to be in PATH, of course; avoiding that is a nice-to-have at best, so I think that's fine. Yes, we would be able to find the interface in the runtime state through `ovs-vsctl` and friends. The `show` sub-command is mostly meant for human readable overview of configuration, so we will probably dive to the depths of the interface and port tables. Many of the sub-commands support JSON output format, for example: `ovs-vsctl -f json find interface name=testport` `ovs-vsctl -f json find port name=testport` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912844 Title: Bond with OVS bridging RuntimeError: duplicate mac found! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1912844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912844] Re: Bond with OVS bridging RuntimeError: duplicate mac found!
> 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 configurations, I see: > > # ovs-vsctl list-br > ovs-br > ovs-br.100 > ovs-br.200 > > Does this seems appropriate? I also notice that querying for internal > interfaces returns the same set: While listing the bridges would work for configurations that make use of the 'fake-bridge' paradigm, it would not work for listing interfaces in configurations that do not use it. So I would rely on querying the port/interface tables as entry point instead. > # ovs-vsctl find interface type=internal | grep ^name > name : ovs-br > name : ovs-br.200 > name : ovs-br.100 The interface types I know about today are 'dpdk', 'system', and 'internal'. Interfaces of type 'dpdk' would probably be invisible from the kernel sysfs and netlink interfaces pov, interfaces of type 'system' have their origin in the system and cloud-init would most likely already know all about them. Interfaces of type 'internal' may be used for other things than VLANs so depending on what you want to match on it may or may not be precise enough. See below for some further discussion. > I don't think we want to exclude every interface known to OVS, because I > believe that would regress bug 1898997. From an instance launched from the > integration test for that bug: > > cb6840fc-f53d-471b-b7e7-aa7398fd4c37 > Bridge ovs-br > fail_mode: standalone > Port enp5s0 > Interface enp5s0 > Port ovs-br > Interface ovs-br > type: internal > ovs_version: "2.13.1" > > We _do_ still want to consider enp5s0 in cloud-init's code, because it's a > real interface that isn't (entirely?) configured by OVS. > > Thoughts? (If this isn't a sufficient problem description, let me know!) Do I understand correctly that the goal is to find any OVS managed interface with a VLAN tag to exclude it from the duplicate MAC check? If so the following may be an approach to find them: ovs-vsctl find port 'tag>0' >From the port name you can find the associated interfaces and there is also a shorthand to find on which bridge a port belongs: ovs-vsctl port-to-br -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912844 Title: Bond with OVS bridging RuntimeError: duplicate mac found! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1912844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912844] Re: Bond with OVS bridging RuntimeError: duplicate mac found!
> 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-server-dev/ubuntu/+source/openvswitch/tree/debian/openvswitch-switch.ovs-vswitchd.service#n7 But I guess assessing tools most likely to be in your path would be more portable, so calling `ovs-vsctl` and assessing the result would work ok. One thing to keep in mind is that the OVS/OVN -ctl tools may get into a situation where they wait indefinitely. That can for example happen if the OVSDB server is running but the vSwitch is not. To mitigate that you can use the -t or --timeout option when calling `ovs-vsctl`. To assess whether the `ovs-vswitchd` process is alive independently of the OVSDB you could have an additional check that talks to it on its control socket, for example: `ovs-appctl -t ovs-vswitchd version` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912844 Title: Bond with OVS bridging RuntimeError: duplicate mac found! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1912844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917475] Re: RBAC Permissions too strict for Port_Binding table
** Description changed:
When using Openstack Ussuri with OVN 20.03 and adding a floating IP
- address to a port the ovn-controller on the hypervisor repeatedly
- reports:
+ address to a unbound port the ovn-controller on the hypervisor
+ repeatedly reports:
2021-03-02T10:33:35.517Z|35359|ovsdb_idl|WARN|transaction error:
{"details":"RBAC rules for client
\"juju-eab186-zaza-d26c8c079cc7-11.project.serverstack\" role
\"ovn-controller\" prohibit modification of table
\"Port_Binding\".","error":"permission error"}
2021-03-02T10:33:35.518Z|35360|main|INFO|OVNSB commit failed, force recompute
next time.
The seams to be because the ovn-controller needs to update the
virtual_parent attribute of the port binding *2 but that is not included
in the list of permissions allowed by the ovn-controller role *1
-
*1
https://github.com/ovn-org/ovn/blob/aa8ef5588c119fa8615d78288a7db7e3df2d6fbe/northd/ovn-northd.c#L11331-L11332
*2 https://pastebin.ubuntu.com/p/4CfcxgDgdm/
Disabling rbac by changing the role to "" and stopping and starting the
southbound db listener results in the port 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 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_Binding table
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1917475/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917475] Re: RBAC Permissions too strict for Port_Binding table
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_Binding table To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1917475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928031] Re: neutron-ovn-metadata-agent AttributeError: 'MetadataProxyHandler' object has no attribute 'sb_idl'
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 (Ubuntu) Importance: Undecided Status: New ** Changed in: neutron (Ubuntu) Status: New => Triaged ** Changed in: neutron (Ubuntu) Importance: Undecided => High ** Changed in: charm-ovn-chassis 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/1928031 Title: neutron-ovn-metadata-agent AttributeError: 'MetadataProxyHandler' object has no attribute 'sb_idl' To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-chassis/+bug/1928031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915829] Re: FQDN / hostname recorded in OVSDB is unreliable
$ 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 --unit ovn-chassis/0 'ovs-vsctl get open-vswitch . external-ids:hostname' juju-a0db23-0-lxd-0.maas $ juju run --unit ovn-chassis/0 'apt-cache policy openvswitch-switch' openvswitch-switch: Installed: 2.13.3-0ubuntu0.20.04.1~cloud0 Candidate: 2.13.3-0ubuntu0.20.04.1~cloud0 Version table: *** 2.13.3-0ubuntu0.20.04.1~cloud0 500 500 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-proposed/ussuri/main amd64 Packages 100 /var/lib/dpkg/status 2.9.8-0ubuntu0.18.04.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.9.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Tags removed: verification-needed verification-ussuri-needed ** Tags added: verification-done verification-ussuri-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915829 Title: FQDN / hostname recorded in OVSDB is unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1915829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931244] Re: ovn sriov broken from ussuri onwards
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 Metadata- services to the consumers of the sriovnicsiwtch mechanism driver. At this point in time the sriovnicswitch driver still relies on an agent and RPC. The RPC code does indeed read and update ports and subsequently will call into the OVN driver. Thank you for the pointer to the RpcWorker class name. I will put up a proposal for how we could conditionally add OVN IDL connections to the RPC Workers gated on the presence of the sriovnicswitch driver. -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1931244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924981] Re: [SRU] OVN 20.03.2 point release
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://10.78.95.98/
Connecting to 10.78.95.98:80... failed: Connection timed out.
Retrying.
And I can confirm that the ovn-controller for the hypervisor hosting the load
balancer logs:
2021-06-11T05:36:21.649Z|00130|pinctrl|INFO|Claiming virtual lport
96582bd0-1823-49bd-9c40-fad147c47ca3 for this chassis with the virtual parent
38910d74-fe51-454e-907c-448c32c96661
2021-06-11T05:36:21.651Z|00131|ovsdb_idl|WARN|Dropped 17 log messages in last
55 seconds (most recently, 5 seconds ago) due to excessive rate
2021-06-11T05:36:21.651Z|00132|ovsdb_idl|WARN|transaction error:
{"details":"RBAC rules for client \"awake-mammal.maas\" role \"ovn-controller\"
prohibit modification of table \"Port_Binding\".","error":"permission error"}
2021-06-11T05:36:21.651Z|00133|main|INFO|OVNSB commit failed, force recompute
next time.
I can confirm that after adding the -proposed pocket on ovn-central and
ovn-chassis units and then upgrading the ovn-common, ovn-host and ovn-central
packages the test succeeds and the RBAC violation is no longer logged by
ovn-controller:
--2021-06-11 07:42:19-- (try: 5) http://10.78.95.98/
Connecting to 10.78.95.98:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10918 (11K) [text/html]
Saving to: ‘STDOUT’
- 100%[===>] 10.66K --.-KB/sin
0s
2021-06-11 07:42:19 (485 MB/s) - written to stdout [10918/10918]
2021-06-11 07:42:19 [INFO] Found "This is the default welcome page" in
page retrieved through load balancer (provider="amphora") at
"http://10.78.95.98/";
$ juju run --application ovn-central 'dpkg -l |grep ovn'
- Stdout: |
ii ovn-central20.03.2-0ubuntu0.20.04.1~cloud0
amd64OVN central components
ii ovn-common 20.03.2-0ubuntu0.20.04.1~cloud0
amd64OVN common components
UnitId: ovn-central/0
- Stdout: |
ii ovn-central20.03.2-0ubuntu0.20.04.1~cloud0
amd64OVN central components
ii ovn-common 20.03.2-0ubuntu0.20.04.1~cloud0
amd64OVN common components
UnitId: ovn-central/1
- Stdout: |
ii ovn-central20.03.2-0ubuntu0.20.04.1~cloud0
amd64OVN central components
ii ovn-common 20.03.2-0ubuntu0.20.04.1~cloud0
amd64OVN common components
UnitId: ovn-central/2
$ juju run --application ovn-chassis 'dpkg -l |grep ovn'
- Stdout: |
ii neutron-ovn-metadata-agent 2:16.3.1-0ubuntu1~cloud0
all Neutron is a virtual network service
for Openstack - OVN metadata agent
ii ovn-common 20.03.2-0ubuntu0.20.04.1~cloud0
amd64OVN common components
ii ovn-host 20.03.2-0ubuntu0.20.04.1~cloud0
amd64OVN host components
UnitId: ovn-chassis/0
- Stdout: |
ii neutron-ovn-metadata-agent 2:16.3.1-0ubuntu1~cloud0
all Neutron is a virtual network service
for Openstack - OVN metadata agent
ii ovn-common 20.03.2-0ubuntu0.20.04.1~cloud0
amd64OVN common components
ii ovn-host 20.03.2-0ubuntu0.20.04.1~cloud0
amd64OVN host components
UnitId: ovn-chassis/2
- Stdout: |
ii neutron-ovn-metadata-agent 2:16.3.1-0ubuntu1~cloud0
all Neutron is a virtual network service
for Openstack - OVN metadata agent
ii ovn-common 20.03.2-0ubuntu0.20.04.1~cloud0
amd64OVN common components
ii ovn-host 20.03.2-0ubuntu0.20.04.1~cloud0
amd64OVN host components
UnitId: ovn-chassis/1
For reference packages on the neutron-api units was not touched as part
of the test, and they were running python3-neutron
2:16.3.1-0ubuntu1~cloud0 for neutron-server.
** Tags removed: verification-ussuri-needed
** Tags added: verification-ussuri-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924981
Title:
[SRU] OVN 20.03.2 point release
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1924981/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928179] Re: [Victoria] Amphora fails to plug vip
>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
timeout: 180
graceful_timeout: 30
keepalive: 2
limit_request_line: 4094
limit_request_fields: 100
limit_request_field_size: 8190
reload: False
reload_engine: auto
reload_extra_files: []
spew: False
check_config: False
preload_app: True
sendfile: None
reuse_port: False
chdir: /root
daemon: False
raw_env: []
pidfile: None
worker_tmp_dir: None
user: 0
group: 0
umask: 0
initgroups: False
tmp_upload_dir: None
secure_scheme_headers: {'X-FORWARDED-PROTOCOL': 'ssl', 'X-FORWARDED-PROTO':
'https', 'X-FORWARDED-SSL': 'on'}
forwarded_allow_ips: ['127.0.0.1']
accesslog: /var/log/amphora-agent.log
disable_redirect_access_to_syslog: False
access_log_format: %(h)s %(l)s %(u)s %(t)s "%(r)s" %(s)s %(b)s "%(f)s" "%(a)s"
errorlog: /var/log/amphora-agent.log
loglevel: debug
capture_output: False
logger_class: gunicorn.glogging.Logger
logconfig: None
logconfig_dict: {}
syslog_addr: unix://run/rsyslog/octavia/log#dgram
syslog: True
syslog_prefix: None
syslog_facility: local1
enable_stdio_inheritance: False
statsd_host: None
dogstatsd_tags:
statsd_prefix:
proc_name: None
default_proc_name: gunicorn
pythonpath: None
paste: None
on_starting:
on_reload:
when_ready:
pre_fork:
post_fork:
post_worker_init:
worker_int:
worker_abort:
pre_exec:
pre_request:
post_request:
child_exit:
worker_exit:
nworkers_changed:
on_exit:
proxy_protocol: False
proxy_allow_ips: ['127.0.0.1']
keyfile: None
certfile: /etc/octavia/certs/server.pem
ssl_version: 5
cert_reqs: 2
ca_certs: /etc/octavia/certs/client_ca.pem
suppress_ragged_eofs: True
do_handshake_on_connect: False
ciphers: None
raw_paste_global_conf: []
strip_header_spaces: False
[2021-06-11 13:58:57 +] [1268] [INFO] Starting gunicorn 20.0.4
[2021-06-11 13:58:57 +] [1268] [DEBUG] Arbiter booted
[2021-06-11 13:58:57 +] [1268] [INFO] Listening at: http://[::]:9443 (1268)
[2021-06-11 13:58:57 +] [1268] [INFO] Using worker: sync
[2021-06-11 13:58:57 +] [1305] [INFO] Booting worker with pid: 1305
[2021-06-11 13:58:57 +] [1268] [DEBUG] 1 workers
[2021-06-11 13:58:59 +] [1305] [DEBUG] GET //
fc00:720b:3754:6680:f816:3eff:feaf:bab8 - - [11/Jun/2021:13:58:59 +] "GET
// HTTP/1.1" 200 21 "-" "Octavia HaProxy Rest Client/0.5
(https://wiki.openstack.org/wiki/Octavia)"
[2021-06-11 13:58:59 +] [1305] [DEBUG] GET /1.0/info
fc00:720b:3754:6680:f816:3eff:feaf:bab8 - - [11/Jun/2021:13:58:59 +] "GET
/1.0/info HTTP/1.1" 200 180 "-" "Octavia HaProxy Rest Client/0.5
(https://wiki.openstack.org/wiki/Octavia)"
[2021-06-11 13:59:06 +] [1305] [DEBUG] GET //
fc00:720b:3754:6680:f816:3eff:feaf:bab8 - - [11/Jun/2021:13:59:06 +] "GET
// HTTP/1.1" 200 21 "-" "Octavia HaProxy Rest Client/0.5
(https://wiki.openstack.org/wiki/Octavia)"
[2021-06-11 13:59:06 +] [1305] [DEBUG] POST /1.0/plug/vip/192.168.0.21
fc00:720b:3754:6680:f816:3eff:feaf:bab8 - - [11/Jun/2021:13:59:06 +] "POST
/1.0/plug/vip/192.168.0.21 HTTP/1.1" 500 133 "-" "Octavia HaProxy Rest
Client/0.5 (https://wiki.openstack.org/wiki/Octavia)"
root@amphora-c173d228-0d3c-4437-82b5-2c4e27b3616c:~# cat
/var/log/octavia/amphora-agent.log
2021-06-11 13:58:57.233 1268 INFO octavia.common.config [-] Logging enabled!
2021-06-11 13:58:57.235 1268 INFO octavia.common.config [-]
/usr/bin/amphora-agent version 7.1.1
2021-06-11 13:58:57.235 1268 DEBUG octavia.common.config [-] command line:
/usr/bin/amphora-agent --config-file=/etc/octavia/amphora-agent.conf
--log-file=/var/log/octavia/amphora-agent.log setup_logging
/usr/lib/python3/dist-packages/octavia/common/config.py:917
2021-06-11 13:58:57.552 1304 INFO
octavia.amphorae.backends.health_daemon.health_daemon [-] Health Manager Sender
starting.
2021-06-11 13:59:06.913 1305 DEBUG
octavia.amphorae.backends.agent.api_server.osutils [-] b'' _bring_if_up
/usr/lib/python3/dist-packages/octavia/amphorae/backends/agent/api_server/osutils.py:208
2021-06-11 13:59:06.918 1305 DEBUG
octavia.amphorae.backends.agent.api_server.osutils [-] b'' _bring_if_up
/usr/lib/python3/dist-packages/octavia/amphorae/backends/agent/api_server/osutils.py:212
2021-06-11 13:59:06.931 1305 ERROR
octavia.amphorae.backends.agent.api_server.osutils [-] Failed to ifup eth1 due
to error: Command '['ip', 'netns', 'exec', 'amphora-haproxy', 'ifup', 'eth1']'
returned non-zero exit status 1. b'/bin/sh: 1:
/usr/local/bin/udp-masquerade.sh: not found\nifup: failed to bring up eth1\n':
subprocess.CalledProcessError: Command '['ip', 'netns', 'exec',
'amphora-haproxy', 'ifup', 'eth1']' returned non-zero exit status 1.
The interface appears to already
[Bug 1928179] Re: [Victoria] Amphora fails to plug vip
** 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 Title: [Victoria] Amphora fails to plug vip To manage notifications about this bug go to: https://bugs.launchpad.net/snap-octavia-diskimage-retrofit/+bug/1928179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928179] Re: [Victoria] Amphora fails to plug vip
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/snap-octavia-diskimage-retrofit/+bug/1928179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924981] Re: [SRU] OVN 20.03.2 point release
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: $ sh upgrade.sh + juju run --application ovn-central echo "deb http://archive.ubuntu.com/ubuntu focal-proposed main restricted" >> /etc/apt/sources.list;apt update ... + juju run --application nova-compute echo "deb http://archive.ubuntu.com/ubuntu focal-proposed main restricted" >> /etc/apt/sources.list;apt update ... + juju run --application neutron-api echo "deb http://archive.ubuntu.com/ubuntu focal-proposed main restricted" >> /etc/apt/sources.list;apt update - Stderr: |2 ... + juju run --application neutron-api apt -y install python3-openvswitch; systemctl restart neutron-server - Stderr: |2+ WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Stdout: "Reading package lists...\nBuilding dependency tree...\nReading state information...\nThe following packages will be upgraded:\n python3-openvswitch\n1 upgraded, 0 newly installed, 0 to remove and 44 not upgraded.\nNeed to get 94.8 kB of archives.\nAfter this operation, 1024 B of additional disk space will be used.\nGet:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 python3-openvswitch all 2.13.3-0ubuntu0.20.04.1 [94.8 kB]\nFetched 94.8 kB in 0s (522 kB/s)\n(Reading database ... \r(Reading database ... 5%\r(Reading database ... 10%\r(Reading database ... 15%\r(Reading database ... 20%\r(Reading database ... 25%\r(Reading database ... 30%\r(Reading database ... 35%\r(Reading database ... 40%\r(Reading database ... 45%\r(Reading database ... 50%\r(Reading database ... 55%\r(Reading database ... 60%\r(Reading database ... 65%\r(Reading database ... 70%\r(Reading database ... 75%\r(Reading database ... 80%\r(Reading database ... 85%\r(Reading database ... 90%\r(Reading database ... 95%\r(Reading database ... 100%\r(Reading database ... 56448 files and directories currently installed.)\nPreparing to unpack .../python3-openvswitch_2.13.3-0ubuntu0.20.04.1_all.deb ...\nUnpacking python3-openvswitch (2.13.3-0ubuntu0.20.04.1) over (2.13.1-0ubuntu0.20.04.4) ...\nSetting up python3-openvswitch (2.13.3-0ubuntu0.20.04.1) ...\n" UnitId: neutron-api/0 - Stderr: |2+ WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Stdout: "Reading package lists...\nBuilding dependency tree...\nReading state information...\nThe following packages will be upgraded:\n python3-openvswitch\n1 upgraded, 0 newly installed, 0 to remove and 44 not upgraded.\nNeed to get 94.8 kB of archives.\nAfter this operation, 1024 B of additional disk space will be used.\nGet:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 python3-openvswitch all 2.13.3-0ubuntu0.20.04.1 [94.8 kB]\nFetched 94.8 kB in 0s (346 kB/s)\n(Reading database ... \r(Reading database ... 5%\r(Reading database ... 10%\r(Reading database ... 15%\r(Reading database ... 20%\r(Reading database ... 25%\r(Reading database ... 30%\r(Reading database ... 35%\r(Reading database ... 40%\r(Reading database ... 45%\r(Reading database ... 50%\r(Reading database ... 55%\r(Reading database ... 60%\r(Reading database ... 65%\r(Reading database ... 70%\r(Reading database ... 75%\r(Reading database ... 80%\r(Reading database ... 85%\r(Reading database ... 90%\r(Reading database ... 95%\r(Reading database ... 100%\r(Reading database ... 56448 files and directories currently installed.)\nPreparing to unpack .../python3-openvswitch_2.13.3-0ubuntu0.20.04.1_all.deb ...\nUnpacking python3-openvswitch (2.13.3-0ubuntu0.20.04.1) over (2.13.1-0ubuntu0.20.04.4) ...\nSetting up python3-openvswitch (2.13.3-0ubuntu0.20.04.1) ...\n" UnitId: neutron-api/1 - Stderr: |2+ WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Stdout: "Reading package lists...\nBuilding dependency tree...\nReading state information...\nThe following packages will be upgraded:\n python3-openvswitch\n1 upgraded, 0 newly installed, 0 to remove and 44 not upgraded.\nNeed to get 94.8 kB of archives.\nAfter this operation, 1024 B of additional disk space will be used.\nGet:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 python3-openvswitch all 2.13.3-0ubuntu0.20.04.1 [94.8 kB]\nFetched 94.8 kB in 0s (478 kB/s)\n(Reading database ... \r(Reading database ... 5%\r(Reading database ... 10%\r(Reading database ... 15%\r(Reading database ... 20%\r(Reading database ... 25%\r(Reading database ... 30%\r(Reading database ... 35%\r(Reading database ... 40%\r(Reading database ... 45%\r(Reading database ... 50%\r(Reading database ... 55%\r(Reading database ... 60%\r
[Bug 1924982] Re: [SRU] OVN 20.06.3 point release
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: $ sh upgrade.sh + juju run --application ovn-central echo "deb http://archive.ubuntu.com/ubuntu groovy-proposed main restricted" >> /etc/apt/sources.list;apt update + juju run --application nova-compute echo "deb http://archive.ubuntu.com/ubuntu groovy-proposed main restricted" >> /etc/apt/sources.list;apt update + juju run --application neutron-api echo "deb http://archive.ubuntu.com/ubuntu groovy-proposed main restricted" >> /etc/apt/sources.list;apt update + juju run --application neutron-api apt -y install python3-openvswitch; systemctl restart neutron-server - Stderr: |2+ WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Stdout: "Reading package lists...\nBuilding dependency tree...\nReading state information...\nThe following packages will be upgraded:\n python3-openvswitch\n1 upgraded, 0 newly installed, 0 to remove and 36 not upgraded.\nNeed to get 94.8 kB of archives.\nAfter this operation, 1024 B of additional disk space will be used.\nGet:1 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 python3-openvswitch all 2.13.3-0ubuntu0.20.10.1 [94.8 kB]\nFetched 94.8 kB in 0s (476 kB/s)\n(Reading database ... \r(Reading database ... 5%\r(Reading database ... 10%\r(Reading database ... 15%\r(Reading database ... 20%\r(Reading database ... 25%\r(Reading database ... 30%\r(Reading database ... 35%\r(Reading database ... 40%\r(Reading database ... 45%\r(Reading database ... 50%\r(Reading database ... 55%\r(Reading database ... 60%\r(Reading database ... 65%\r(Reading database ... 70%\r(Reading database ... 75%\r(Reading database ... 80%\r(Reading database ... 85%\r(Reading database ... 90%\r(Reading database ... 95%\r(Reading database ... 100%\r(Reading database ... 56764 files and directories currently installed.)\nPreparing to unpack .../python3-openvswitch_2.13.3-0ubuntu0.20.10.1_all.deb ...\nUnpacking python3-openvswitch (2.13.3-0ubuntu0.20.10.1) over (2.13.1-0ubuntu1.3) ...\nSetting up python3-openvswitch (2.13.3-0ubuntu0.20.10.1) ...\n" UnitId: neutron-api/1 - Stderr: |2+ WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Stdout: "Reading package lists...\nBuilding dependency tree...\nReading state information...\nThe following packages will be upgraded:\n python3-openvswitch\n1 upgraded, 0 newly installed, 0 to remove and 36 not upgraded.\nNeed to get 94.8 kB of archives.\nAfter this operation, 1024 B of additional disk space will be used.\nGet:1 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 python3-openvswitch all 2.13.3-0ubuntu0.20.10.1 [94.8 kB]\nFetched 94.8 kB in 0s (556 kB/s)\n(Reading database ... \r(Reading database ... 5%\r(Reading database ... 10%\r(Reading database ... 15%\r(Reading database ... 20%\r(Reading database ... 25%\r(Reading database ... 30%\r(Reading database ... 35%\r(Reading database ... 40%\r(Reading database ... 45%\r(Reading database ... 50%\r(Reading database ... 55%\r(Reading database ... 60%\r(Reading database ... 65%\r(Reading database ... 70%\r(Reading database ... 75%\r(Reading database ... 80%\r(Reading database ... 85%\r(Reading database ... 90%\r(Reading database ... 95%\r(Reading database ... 100%\r(Reading database ... 56764 files and directories currently installed.)\nPreparing to unpack .../python3-openvswitch_2.13.3-0ubuntu0.20.10.1_all.deb ...\nUnpacking python3-openvswitch (2.13.3-0ubuntu0.20.10.1) over (2.13.1-0ubuntu1.3) ...\nSetting up python3-openvswitch (2.13.3-0ubuntu0.20.10.1) ...\n" UnitId: neutron-api/2 - Stderr: |2+ WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Stdout: "Reading package lists...\nBuilding dependency tree...\nReading state information...\nThe following packages will be upgraded:\n python3-openvswitch\n1 upgraded, 0 newly installed, 0 to remove and 36 not upgraded.\nNeed to get 94.8 kB of archives.\nAfter this operation, 1024 B of additional disk space will be used.\nGet:1 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 python3-openvswitch all 2.13.3-0ubuntu0.20.10.1 [94.8 kB]\nFetched 94.8 kB in 0s (557 kB/s)\n(Reading database ... \r(Reading database ... 5%\r(Reading database ... 10%\r(Reading database ... 15%\r(Reading database ... 20%\r(Reading database ... 25%\r(Reading database ... 30%\r(Reading database ... 35%\r(Reading database ... 40%\r(Reading database ... 45%\r(Reading database ... 50%\r(Reading database ... 55%\r(Reading database ... 60%\r(Reading database ... 65%\r
[Bug 1924981] Re: [SRU] OVN 20.03.2 point release
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 to proceed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924981 Title: [SRU] OVN 20.03.2 point release To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1924981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917475] Re: RBAC Permissions too strict for Port_Binding table
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917475 Title: RBAC Permissions too strict for Port_Binding table To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1917475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915829] Re: FQDN / hostname recorded in OVSDB is unreliable
$ 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-99a8-d9e4dccf3c55"}
$ hostname -f
juju-d4e71d-0-lxd-0.maas
# sudo apt install openvswitch-common openvswitch-switch python3-openvswitch
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
openvswitch-doc
The following packages will be upgraded:
openvswitch-common openvswitch-switch python3-openvswitch
3 upgraded, 0 newly installed, 0 to remove and 21 not upgraded.
Need to get 2783 kB of archives.
After this operation, 28.7 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64
python3-openvswitch all 2.13.3-0ubuntu0.20.04.1 [94.8 kB]
Get:2 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64
openvswitch-common amd64 2.13.3-0ubuntu0.20.04.1 [1152 kB]
Get:3 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64
openvswitch-switch amd64 2.13.3-0ubuntu0.20.04.1 [1536 kB]
Fetched 2783 kB in 1s (1986 kB/s)
(Reading database ... 53438 files and directories currently installed.)
Preparing to unpack .../python3-openvswitch_2.13.3-0ubuntu0.20.04.1_all.deb ...
Unpacking python3-openvswitch (2.13.3-0ubuntu0.20.04.1) over (2.13.1-0ubuntu0.20
.04.4) ...
Preparing to unpack .../openvswitch-common_2.13.3-0ubuntu0.20.04.1_amd64.deb ...
Unpacking openvswitch-common (2.13.3-0ubuntu0.20.04.1) over (2.13.1-0ubuntu0.20.
04.4) ...
Preparing to unpack .../openvswitch-switch_2.13.3-0ubuntu0.20.04.1_amd64.deb ...
Unpacking openvswitch-switch (2.13.3-0ubuntu0.20.04.1) over (2.13.1-0ubuntu0.20.
04.4) ...
Setting up python3-openvswitch (2.13.3-0ubuntu0.20.04.1) ...
Setting up openvswitch-common (2.13.3-0ubuntu0.20.04.1) ...
Setting up openvswitch-switch (2.13.3-0ubuntu0.20.04.1) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for systemd (245.4-4ubuntu3.6) ...
$ 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.maas,
rundir="/var/run/openvswitch", system-id="424e6f88-2e79-436f-99a8-d9e4dccf3c55"}
** Description changed:
[ Impact ]
The Open vSwitch init script `ovs-ctl` determines the system hostname
and records it in the `external-ids:hostname` field of the `Open-
vSwitch` table in the local OVSDB.
This value may be consumed by downstream software and having it unset or
set to a incorrect value could lead to erratic behavior of a system.
In recent Ubuntu development we have also made it possible to configure
Open vSwitch with netplan.io, which allows for a Open vSwitch controlled
data path to be the only external network connection on a system.
As such the current startup sequence of Open vSwitch is insufficient to
allow for reliable recording of FQDN / hostname at system boot-up time.
Examples of downstream issues can be viewed in bug 1896630 and bug
1912844 comment #26.
[ Test Case ]
- 1) Use MAAS 2.9, configure a machine with Open vSwitch bridge for networking
and deploy.
- 2) Confirm that without the change the hostname recorded in Open vSwitch is
`ubuntu`.
- 3) Add a PPA with the updated Open vSwitch package to MAAS.
- 4) Re-deploy and confirm that the hostname recorded in Open vSwitch matches
the FQDN as provided by MAAS.
+ 1) Deploy bundle on metal:
+
+ series: focal
+ machines:
+ '0':
+ constraints: cores=48
+ relations:
+ - - octavia:ovsdb-subordinate
+- ovn-chassis:ovsdb-subordinate
+ applications:
+ ovn-chassis:
+ charm: cs:ovn-chassis
+ bindings:
+ "": public-space
+ octavia:
+ charm: cs:octavia
+ options:
+ openstack-origin: distro
+ num_units: 1
+ to:
+ - 'lxd:0'
+ bindings:
+ "": public-space
+
+ 2) juju run --unit ovn-chassis/0 'ovs-vsctl remove open-vswitch .
external-ids hostname'
+ 3) juju run --unit ovn-chassis/0 'sudo shutdown -r now'
+ 4) Observe external-ids:hostname being recorded as a shortname
+ 5) Add proposed and install openvswitch packages, repeat step 2-3
+ 6) Observe external-ids:hostname being recorded as a FQDN
[ Regression potential ]
Minimal, the update uses the exact same methods to accomplish the end
result of recording the hostname as before, we have only re-ordered when
the events occur to ensure successful operation.
[racb] A new service is added in packaging. Users who have overridden
existing services to change behaviour (eg. "disable all OVS-related
services") may have that configuration not have the same effect after
this update (eg. "I thought I disabled all OVS-related services but
what's this ovs-record-ho
[Bug 1928179] [NEW] [Victoria] Amphora fails to plug vip
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/python3/dist-packages/octavia/amphorae/backends/agent/api_server/osutils.py:208 2021-05-12 06:44:22.425 1319 DEBUG octavia.amphorae.backends.agent.api_server.osutils [-] b'' _bring_if_up /usr/lib/python3/dist-packages/octavia/amphorae/backends/agent/api_server/osutils.py:212 2021-05-12 06:44:22.445 1319 ERROR octavia.amphorae.backends.agent.api_server.osutils [-] Failed to ifup eth1 due to error: Command '['ip', 'netns', 'exec', 'amphora-haproxy', 'ifup', 'eth1']' returned non-zero exit status 1. b'/bin/sh: 1: /usr/local/bin/udp-masquerade.sh: not found\nifup: failed to bring up eth1\n': subprocess.CalledProcessError: Command '['ip', 'netns', 'exec', 'amphora-haproxy', 'ifup', 'eth1']' returned non-zero exit status 1. The octavia-worker will say: 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server [-] Exception during message handling: taskflow.exceptions.WrappedFailure: WrappedFailure: [Failure: octavia.amphorae.drivers.haproxy.exceptions.InternalServerError: Internal Server Error, Failure: octavia.amphorae.drivers.haproxy.exceptions.InternalServerError: Internal Server Error] 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/dispatcher.py", line 309, in dispatch 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/dispatcher.py", line 229, in _do_dispatch 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/octavia/controller/queue/v1/endpoints.py", line 45, in create_load_balancer 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server self.worker.create_load_balancer(load_balancer_id, flavor, 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 329, in wrapped_f 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server return self.call(f, *args, **kw) 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 409, in call 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server do = self.iter(retry_state=retry_state) 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 356, in iter 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server return fut.result() 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.8/concurrent/futures/_base.py", line 432, in result 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server return self.__get_result() 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.8/concurrent/futures/_base.py", line 388, in __get_result 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server raise self._exception 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 412, in call 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server result = fn(*args, **kwargs) 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/octavia/controller/worker/v1/controller_worker.py", line 370, in create_load_balancer 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server create_lb_tf.run() 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/taskflow/engines/action_engine/engine.py", line 247, in run 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server for _state in self.run_iter(timeout=timeout): 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/taskflow/engines/action_engine/engine.py", line 340, in run_iter 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server failure.Failure.reraise_if_any(er_failures) 2021-05-12 06:44:27.046 129193 ERROR oslo_messaging.rpc.server File "
[Bug 1924981] [NEW] [SRU] OVN 20.03.2 point release
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) Importance: Undecided Status: Invalid ** Affects: ovn (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ovn (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/ussuri Importance: Undecided Status: New ** Also affects: cloud-archive/victoria 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/1924981 Title: [SRU] OVN 20.03.2 point release To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1924981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924982] [NEW] [SRU] OVN 20.06.3 point release
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) 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/1924982 Title: [SRU] OVN 20.06.3 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1924982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931244] Re: ovn sriov broken from ussuri onwards
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 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1931244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917475] Re: RBAC Permissions too strict for Port_Binding table
** Changed in: ovn (Ubuntu)
Status: In Progress => Fix Committed
** Also affects: ovn (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: ovn (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: ovn (Ubuntu Focal)
Importance: Undecided
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 Focal)
Status: New => Fix Released
** Changed in: ovn (Ubuntu Impish)
Assignee: Frode Nordahl (fnordahl) => (unassigned)
** Changed in: ovn (Ubuntu Hirsute)
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/1917475
Title:
RBAC Permissions too strict for Port_Binding table
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1917475/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914988] Re: IGMP Snooping does not work with RBAC enabled ovn-controllers
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1914988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913024] Re: RBAC Permissions too strict for Chassis_Private table
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1913024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857026] Re: OVN doesn't seem to support reverse DNS lookups for instances
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/1857026 Title: OVN doesn't seem to support reverse DNS lookups for instances To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-central/+bug/1857026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892132] Re: Failure to get the correct UpLink Representor
** 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 affects: libvirt (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu Impish) Status: New => Fix Released ** Also affects: python-os-vif (Ubuntu) Importance: Undecided Status: New ** Changed in: python-os-vif (Ubuntu Impish) Status: New => Fix Released ** Changed in: python-os-vif (Ubuntu Hirsute) Status: New => 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/1892132 Title: Failure to get the correct UpLink Representor To manage notifications about this bug go to: https://bugs.launchpad.net/os-vif/+bug/1892132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892132] Re: Failure to get the correct UpLink Representor
** 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-vif (Ubuntu Focal) 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/1892132 Title: Failure to get the correct UpLink Representor To manage notifications about this bug go to: https://bugs.launchpad.net/os-vif/+bug/1892132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892132] Re: Failure to get the correct UpLink Representor
** 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) Assignee: (unassigned) => Frode Nordahl (fnordahl) ** Changed in: libvirt (Ubuntu Focal) Status: New => In Progress ** Changed in: libvirt (Ubuntu Focal) 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/1892132 Title: Failure to get the correct UpLink Representor To manage notifications about this bug go to: https://bugs.launchpad.net/os-vif/+bug/1892132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892132] Re: Failure to get the correct UpLink Representor
** 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 NVIDIA/Mellanox [2] makes some assumptions about sysfs layout made by OS-VIF and Libvirt apparent. + + To allow users with this hardware to continue to enjoy their existing + systems with the most recent drivers updates are required to os-vif and + libvirt. + + Without this update these systems will stop functioning when upgrading + to the new mlx5_core driver. + + [Test Plan] + Note: Hardware making use of the mlx5_core driver with support for HWOL is required to test these changes. + + 1. Deploy OpenStack on machines with HWOL enabled using kernel without [1] + 2. Create an instance using an HWOL port + 3. Confirm the instance can start and that it has connectivity + 4. Upgrade to kernel with [1] and re-confirm + + [Regression Potential] + For OS-VIF the changes are made to code paths used exclusively by consumers of this type of hardware and HWOL enabled. They are also made in a backward compatible way so that it works both with the old and new driver. + + For Libvirt the change is made in such a way that it will behave as + before when used to look up hardware that populates net/phys_port_id. + When used with hardware that do not populate net/phys_port_id but use + net_phys_port_name instead, which is typical for the hardware in + question, the new behavior is used. + + [Original Bug Description] + Due to new kernel patch here [1], the PF and VF representors are linked to their parent PCI device. Old Structure: The structure of VF's PCI Address/physfn/net contains only the PF of that VF $ ls /sys/bus/pci/devices//physfn/net/ enp2s0f0 $ ls -l /sys/class/net ... lrwxrwxrwx 1 root root 0 Aug 17 11:11 enp2s0f0_0 -> ../../devices/virtual/net/enp2s0f0_0 lrwxrwxrwx 1 root root 0 Aug 17 11:11 enp2s0f0_1 -> ../../devices/virtual/net/enp2s0f0_1 lrwxrwxrwx 1 root root 0 Aug 17 11:11 enp2s0f0_2 -> ../../devices/virtual/net/enp2s0f0_2 lrwxrwxrwx 1 root root 0 Aug 17 11:11 enp2s0f0_3 -> ../../devices/virtual/net/enp2s0f0_3 ... New Structure: The structure of VF's PCI Address/physfn/net contains the PF of that VF and the VF representors $ ls /sys/bus/pci/devices//physfn/net/ enp3s0f0 enp3s0f0_0 enp3s0f0_1 enp3s0f0_2 enp3s0f0_3 $ ls -l /sys/class/net ... lrwxrwxrwx. 1 root root0 Aug 17 08:43 enp3s0f0_0 -> ../../devices/pci:00/:00:02.0/:03:00.0/net/enp3s0f0_0 lrwxrwxrwx. 1 root root0 Aug 17 08:43 enp3s0f0_1 -> ../../devices/pci:00/:00:02.0/:03:00.0/net/enp3s0f0_1 lrwxrwxrwx. 1 root root0 Aug 17 08:43 enp3s0f0_2 -> ../../devices/pci:00/:00:02.0/:03:00.0/net/enp3s0f0_2 lrwxrwxrwx. 1 root root0 Aug 17 08:43 enp3s0f0_3 -> ../../devices/pci:00/:00:02.0/:03:00.0/net/enp3s0f0_3 ... - [1] - https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=123f0f53dd64b67e34142485fe866a8a581f12f1 + [1] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=123f0f53dd64b67e34142485fe866a8a581f12f1 + [2] https://www.mellanox.com/products/infiniband-drivers/linux/mlnx_ofed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892132 Title: Failure to get the correct UpLink Representor To manage notifications about this bug go to: https://bugs.launchpad.net/os-vif/+bug/1892132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937075] [NEW] ovn-ctl: ovsdb-server startup might sometimes get stuck and not upgrade clustered database
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 a clustered DB is upgraded in the event of a schema change. 0: https://github.com/ovn- org/ovn/commit/65cc0e225b5922a72f0d40c2c39da0210669c21a ** Affects: ovn (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: ovn (Ubuntu Focal) Importance: High Status: Triaged ** Affects: ovn (Ubuntu Groovy) Importance: Undecided Status: Fix Released ** Affects: ovn (Ubuntu Hirsute) Importance: Undecided Status: Fix Released ** Affects: ovn (Ubuntu Impish) Importance: Undecided Status: Fix Released ** Also affects: ovn (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: ovn (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: ovn (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ovn (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: ovn (Ubuntu Impish) Status: New => Fix Released ** Changed in: ovn (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: ovn (Ubuntu Groovy) Status: New => Fix Released ** Changed in: ovn (Ubuntu Focal) Status: New => Triaged ** Changed in: ovn (Ubuntu Focal) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937075 Title: ovn-ctl: ovsdb-server startup might sometimes get stuck and not upgrade clustered database To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1937075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937415] [NEW] Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199
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 apport would have caught the kernel logs from previous boot as well. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.199 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 15:25:46 2021 Dependencies: InstallationDate: Installed on 2021-01-18 (185 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.198 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.release: 14.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd01/15/2021:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Description changed: 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 apport would have caught the kernel logs from previous boot as well. ProblemType: Bug DistroRelease: Ubuntu 21.10 - Package: linux-firmware 1.198 + Package: linux-firmware 1.199 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 15:25:46 2021 Dependencies: - + InstallationDate: Installed on 2021-01-18 (185 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.11.0-16-generic N/A - linux-backports-modules-5.11.0-16-generic N/A - linux-firmware 1.198 + linux-restricted-modules-5.11.0-16-generic N/A + linux-backports-modules-5.11.0-16-generic N/A + linux-firmware 1.198 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.release: 14.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd01/15/2021:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937415 Title: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199 To manage notifications about this bug go to: https://bugs.launchpad.net/
[Bug 1937415] Re: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199
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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937415 Title: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1937415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937415] Re: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199
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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937415 Title: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1937415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937415] Re: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199
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 issues after one full day of use. I wonder if this only occurred on the first boot with the new firmware, or if some other external activity caused the issue? I'm going to mark this as incomplete for now as I can no longer reproduce, feel free to downgrade to Invalid if you deem that appropriate. ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937415 Title: Intel Wi-Fi 6 AX200 (iwlwifi) unstable with linux-firmware 1.199 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1937415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899369] Re: ovn-controller: Disable ofctrl probe by default
** 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 ofctrl probe by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1899369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899369] Re: ovn-controller: Disable ofctrl probe by default
** 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 discovered when migrating a 3-node OpenStack cloud with 1000 instances deployed in our test lab. A test case could be to repeat that setup. [Regression Potential] - + None, the change of behavior was introduced upstream in [0] and later reversed in [1]. Keeping an idle probe for a unix socket type connection is clearly unnecessary. [Original Bug Report] A change [0] prior to the release of OVN v20.03.0 introduced a change of behavior where the inactivity probe for the ofctrl connection defaults to 5 seconds. Since this normally is a unix socket the default was not to have a inactivity probe at all. On a busy system a inactivity probe of 5 seconds is not enough for the OVN Controller to complete programming of the switch. The change of behavior was corrected in [1] and I think it would be beneficial if Ubuntu backported this fix to the OVN package rather than having charms and/or end users work around the issue by manually configuring the timeout through the `external-ids:ovn-openflow-probe- interval` key in the Open_vSwitch table. Symptoms of this problem is that a OVN controller is either unable to do initial programming of a switch for a host with many ports and flows or that updates are lost on a functional system. The following will be printed in the log: 2020-10-11T18:56:09.355Z|30186|rconn|ERR|unix:/var/run/openvswitch/br- int.mgmt: no response to inactivity probe after 5 seconds, disconnecting 0: https://github.com/ovn-org/ovn/commit/c99069c8934c9ea55d310a8b6d48fb66aa477589 1: https://github.com/ovn-org/ovn/commit/b8af8549396e62d6523be18e104352e334825783 -- 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 ofctrl probe by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1899369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899369] Re: ovn-controller: Disable ofctrl probe by default
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-needed-focal ** Tags added: verification-done-focal -- 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 ofctrl probe by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1899369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906922] [NEW] Unpredictable behaviour on conflicting flow actions
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 openstack security group create b openstack security group create c openstack security group rule create --ingress --ethertype IPv4 --protocol icmp --remote-group b b openstack security group rule create --ingress --ethertype IPv6 --protocol icmp --remote-group b b openstack security group rule create --ingress --ethertype IPv4 --protocol icmp --remote-group c c openstack security group rule create --ingress --ethertype IPv6 --protocol icmp --remote-group c c openstack server add security group for server in zaza-neutrontests-ins-1 zaza-neutrontests-ins-2; do for group in a b c; do openstack server add security group $server $group;done;done Look for bad conjunction messages in ovn-controller log and monitor ICMP reachability to the instances. Fixed upstream: https://github.com/ovn-org/ovn/commit/986b3d5e4ad6f05245d021ba699c957246294a22 Other bug trackers: https://bugzilla.redhat.com/1871931 Symptoms: Every other packet does not arrive. 2020-12-05T10:33:38.304Z|00016|ofctrl|INFO|OpenFlow error: OFPT_ERROR (OF1.3) (xid=0x1af): NXBAC_BAD_CONJUNCTION OFPT_FLOW_MOD (OF1.3) (xid=0x1af): ***decode error: NXBAC_BAD_CONJUNCTION*** 04 0e 00 b0 00 00 01 af-00 00 00 00 e6 89 28 3a |..(:| 0010 00 00 00 00 00 00 00 00-2c 00 00 00 00 00 07 d2 |,...| 0020 ff ff ff ff ff ff ff ff-ff ff ff ff 00 00 00 00 || 0030 00 01 00 53 80 00 0a 02-08 00 80 00 14 01 01 00 |...S| 0040 01 1e 04 00 00 00 03 00-01 d3 08 00 00 00 22 00 |..".| 0050 00 00 2b 00 01 d9 20 00-00 00 00 00 00 00 00 00 |..+... .| 0060 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 || 0070 00 00 00 00 00 00 01 80-00 04 08 00 00 00 00 00 || 0080 00 00 03 00 00 00 00 00-00 04 00 28 00 00 00 00 |...(| 0090 ff ff 00 10 00 00 23 20-00 0e ff f8 2d 00 00 00 |..# -...| 00a0 ff ff 00 10 00 00 23 20-00 22 01 02 00 00 00 09 |..# ."..| I have been able to backport this fix to 20.03.1 with minor adaption using these commits from master, however a flaky test may need some more investigation: commit 986b3d5e4ad6f05245d021ba699c957246294a22 commit 33c15c145988daa6172928dc870f3a0225515f50 commit 107bb25029350bd0f7dfeeb0ef3053adbd504e3e commit e49ce9a33f38f29c44e3c30afcc189b5f6a9ef8e commit dadae4f800ccb1f2759378f0bd804dd002e31605 commit 7cab7bd1268ba67429954da4f73de91090acf779 commit 9d2e8d32fb9865513b70408a665184a67564390d commit f4e508dd7a6cfbfc2e3250a8c11a8d0fdc1dfdd0 commit 6f0b1e02d9ab3a94048c4818f2d382938cad4b71 commit 23063cf4178c05f5d6b3e4ec6d323ccc88df6101 commit 354d3853d40cbce89a434632f67daed7fc992d8b The list of commits is quite long and this is due to how controller/ofctrl.c has changed from 20.03.1 was cut until now, but the nature of the changes look sane to me. ** Affects: ovn (Ubuntu) Importance: High Status: Triaged ** Changed in: ovn (Ubuntu) Status: New => Triaged ** Changed in: ovn (Ubuntu) Importance: Undecided => High -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1906922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907081] [NEW] OVN database is not upgraded on package upgrade
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] has the side effect of disabling automatic upgrading of clustered databases. Previously this would have been done on every startup [1]. A recent commit to master [2] addresses this and uses the combination of presence of `--db-*-cluster-local-addr` and non-presence of the `--db -*-cluster-remote-addr` to determine if the upgrade should be run. We should backport [2] to our supported OVN packages to prepare for supporting upgrades that require database schema changes. We may also need to change the behavior of the ovn-central charm to not set the `--db-*-cluster-remote-addr` argument on the leader unit. 0: https://github.com/ovn-org/ovn/commit/6444059b5f9444ce06634794d275257f945a6ce5 1: https://github.com/ovn-org/ovn/blob/5c2d311b8b7b4d5c3a619de72be6a433aa4c44db/utilities/ovn-ctl#L312-L314 2: https://github.com/ovn-org/ovn/commit/67e2f386cc838d0b0f9b4b5da7fe611e1113b70c ** Affects: charm-ovn-central Importance: Medium Status: Triaged ** Affects: ovn (Ubuntu) Importance: Medium Status: Triaged ** Changed in: ovn (Ubuntu) Status: New => Triaged ** Changed in: ovn (Ubuntu) Importance: Undecided => Medium ** Also affects: charm-ovn-central Importance: Undecided Status: New ** Changed in: charm-ovn-central Status: New => Triaged ** Changed in: charm-ovn-central Importance: Undecided => Medium -- 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: OVN database is not upgraded on package upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-central/+bug/1907081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907081] Re: OVN database is not upgraded on package upgrade
** 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 upgrade -- 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 notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-central/+bug/1907081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906922] Re: Unpredictable behaviour on conflicting flow actions
** 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 actions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1906922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907081] Re: Clustered OVN database is not upgraded on package upgrade
** 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 package upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-central/+bug/1907081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906922] Re: Unpredictable behaviour on conflicting flow actions
** 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1906922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906922] Re: Unpredictable behaviour on conflicting flow actions
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1906922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907081] Re: Clustered OVN database is not upgraded on package upgrade
** 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 notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-central/+bug/1907081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906922] Re: Unpredictable behaviour on conflicting flow actions
** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: ovn (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: ovn (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ovn (Ubuntu Focal) Status: New => In Progress ** Changed in: ovn (Ubuntu Groovy) Status: New => In Progress ** Changed in: ovn (Ubuntu Groovy) Importance: Undecided => Critical ** Changed in: ovn (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: ovn (Ubuntu Groovy) Assignee: (unassigned) => 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 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 about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1906922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name
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) Technically, the compute hosts are partially registered with `nova`: $ nova service-list +++-+--+-+---++-+ | Id | Binary | Host| Zone | Status | State | Updated_at | Disabled Reason | +++-+--+-+---++-+ | 1 | nova-conductor | juju-302a0a-2-lxd-2 | internal | enabled | up| 2018-06-29T10:28:00.00 | - | | 14 | nova-scheduler | juju-302a0a-2-lxd-2 | internal | enabled | up| 2018-06-29T10:28:01.00 | - | | 15 | nova-compute | phanpy | nova | enabled | up| 2018-06-29T10:28:01.00 | - | | 16 | nova-compute | aurorus | nova | enabled | up| 2018-06-29T10:28:05.00 | - | | 26 | nova-compute | zygarde | nova | enabled | up| 2018-06-29T10:28:05.00 | - | +++-+--+-+---++-+ 3) However the compute hosts does not have any resources. The reason for no resources appearing in `nova` is that `nova-compute` service hits a TraceBack during initial host registration: 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager Traceback (most recent call last): 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 7277, in update_available_resource_for_node 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager rt.update_available_resource(context, nodename) 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py", line 664, in update_available_resource 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager resources = self.driver.get_available_resource(nodename) 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 6438, in get_available_resource 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager self._get_pci_passthrough_devices() 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5945, in _get_pci_passthrough_devices 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager pci_info.append(self._get_pcidev_info(name)) 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5906, in _get_pcidev_info 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager device.update(_get_device_capabilities(device, address)) 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5877, in _get_device_capabilities 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager pcinet_info = self._get_pcinet_info(address) 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5820, in _get_pcinet_info 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager virtdev = self._host.device_lookup_by_name(devname) 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/host.py", line 838, in device_lookup_by_name 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager return self.get_connection().nodeDeviceLookupByName(name) 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 186, in doit 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager result = proxy_call(self._autowrap, f, *args, **kwargs) 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 144, in proxy_call 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager rv = execute(f, *args, **kwargs) 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 125, in execute 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager six.reraise(c, e, tb) 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 83, in tworker 2018-06-29 06:25:57.161 35528 ERROR nova.compute.manager rv = meth(*args, **kwargs) 2018-06-29 06:25:57.161 35528 ERROR
[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name
** 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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771662 Title: libvirtError: Node device not found: no node device with matching name To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name
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.0/0003:01:00.0/0003:02:09.0/0003:09:00.0/net/enP3p9s0f0/phys_port_id': Operation not supported -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771662 Title: libvirtError: Node device not found: no node device with matching name To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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.1/sriov_totalvfs 63 # cat /sys/devices/pci\:00/\:00\:03.0/\:01\:00.1/sriov_numvfs 0 # ls -l /sys/devices/pci\:00/\:00\:03.0/\:01\:00.1/virtfn* ls: cannot access '/sys/devices/pci:00/:00:03.0/:01:00.1/virtfn*': No such file or directory While on a system with the Cavium Thunder X card: cat /sys/devices/pci0002\:00/0002\:00\:02.0/0002\:01\:00.0/sriov_totalvfs 128 # cat /sys/devices/pci0002\:00/0002\:00\:02.0/0002\:01\:00.0/sriov_numvfs 18 # ls -l /sys/devices/pci0002\:00/0002\:00\:02.0/0002\:01\:00.0/virtfn* lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn0 -> ../0002:01:00.1 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn1 -> ../0002:01:00.2 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn10 -> ../0002:01:01.3 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn11 -> ../0002:01:01.4 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn12 -> ../0002:01:01.5 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn13 -> ../0002:01:01.6 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn14 -> ../0002:01:01.7 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn15 -> ../0002:01:02.0 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn16 -> ../0002:01:02.1 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn17 -> ../0002:01:02.2 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn2 -> ../0002:01:00.3 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn3 -> ../0002:01:00.4 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn4 -> ../0002:01:00.5 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn5 -> ../0002:01:00.6 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn6 -> ../0002:01:00.7 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn7 -> ../0002:01:01.0 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn8 -> ../0002:01:01.1 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn9 -> ../0002:01:01.2 # cat /sys/devices/pci0002\:00/0002\:00\:02.0/0002\:01\:00.0/virtfn0/net/enP2p1s0f1/phys_port_id cat: '/sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn0/net/enP2p1s0f1/phys_port_id': Operation not supported And this is on by default, without a operator having enabled the virtual functions. libvirt finds the virtual functions this way: https://github.com/libvirt/libvirt/blob/0b86e23d25696c08234d4b73c90cef9515befe84/src/util/virpci.c#L2688 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771662 Title: [bionic] libvirtError: Node device not found: no node device with matching name To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800516] Re: [SRU] octavia-dashboard should be 2.0.0 for Cosmic/Rocky
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-dashboard and octavia-dashboard charm $ juju deploy --series bionic openstack-dashboard \ --config openstack-origin=cloud:bionic-rocky/proposed $ juju deploy --series bionic cs:~openstack-charmers-next/octavia-dashboard $ juju add-relation openstack-dashboard:identity-service keystone:identity-service $ juju add-relation openstack-dashboard mysql $ juju add-relation openstack-dashboard octavia-dashboard 3) Get dashboard URL and admin password $ juju status openstack-dashboard $ juju run --unit keystone/0 'leader-get admin_passwd' 4) Log into dashboard 5) Visit Project -> Network -> Load Balancers 6) Confirm that you see the Load Balancer created by the Zaza functional test 7) Create Load Balancer from GUI and confirm that it succeeds ** Attachment added: "octavia-dashboard.png" https://bugs.launchpad.net/ubuntu/+source/octavia-dashboard/+bug/1800516/+attachment/5216977/+files/octavia-dashboard.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800516 Title: [SRU] octavia-dashboard should be 2.0.0 for Cosmic/Rocky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia-dashboard/+bug/1800516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800516] Re: [SRU] octavia-dashboard should be 2.0.0 for Cosmic/Rocky
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 all client API library for Neutron - Python 3.x ii python3-octavia-dashboard2.0.0-0ubuntu1~cloud0 all OpenStack Load Balance as a service - dashboard plugin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800516 Title: [SRU] octavia-dashboard should be 2.0.0 for Cosmic/Rocky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia-dashboard/+bug/1800516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799132] Re: vault_plugin: TypeError: 'NoneType' object is not subscriptable on secret_store operation
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: vault_plugin: TypeError: 'NoneType' object is not subscriptable on secret_store operation To manage notifications about this bug go to: https://bugs.launchpad.net/castellan/+bug/1799132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796811] [NEW] octavia-db-manage upgrade head fails with Traceback
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): 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/bin/octavia-db-manage", line 10, in 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage sys.exit(main()) 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/octavia/db/migration/cli.py", line 138, in main 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage CONF.command.func(config, CONF.command.name) 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/octavia/db/migration/cli.py", line 68, in do_upgrade 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage do_alembic_command(config, cmd, revision, sql=CONF.command.sql) 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/octavia/db/migration/cli.py", line 36, in do_alembic_command 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage getattr(alembic_cmd, cmd)(config, *args, **kwargs) 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/alembic/command.py", line 254, in upgrade 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage script.run_env() 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/alembic/script/base.py", line 427, in run_env 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage util.load_python_file(self.dir, 'env.py') 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/alembic/util/pyfiles.py", line 81, in load_python_file 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage module = load_module_py(module_id, path) 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/alembic/util/compat.py", line 82, in load_module_py 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage spec.loader.exec_module(module) 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "", line 678, in exec_module 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "", line 219, in _call_with_frames_removed 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/octavia/db/migration/alembic_migrations/env.py", line 88, in 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage run_migrations_online() 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/octavia/db/migration/alembic_migrations/env.py", line 72, in run_migrations_online 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage poolclass=pool.NullPool) 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/__init__.py", line 424, in create_engine 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage return strategy.create(*args, **kwargs) 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/strategies.py", line 52, in create 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage plugins = u._instantiate_plugins(kwargs) 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage AttributeError: 'NoneType' object has no attribute '_instantiate_plugins' 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage My reference test is devstack which runs this under python2.7, could this be a Py3 regression? ** Affects: octavia (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/1796811 Title: octavia-db-manage upgrade head fails with Traceback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1796811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796811] Re: octavia-db-manage upgrade head fails with Traceback
** 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 last): 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/bin/octavia-db-manage", line 10, in 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage sys.exit(main()) 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/octavia/db/migration/cli.py", line 138, in main 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage CONF.command.func(config, CONF.command.name) 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/octavia/db/migration/cli.py", line 68, in do_upgrade 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage do_alembic_command(config, cmd, revision, sql=CONF.command.sql) 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/octavia/db/migration/cli.py", line 36, in do_alembic_command 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage getattr(alembic_cmd, cmd)(config, *args, **kwargs) 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/alembic/command.py", line 254, in upgrade 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage script.run_env() 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/alembic/script/base.py", line 427, in run_env 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage util.load_python_file(self.dir, 'env.py') 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/alembic/util/pyfiles.py", line 81, in load_python_file 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage module = load_module_py(module_id, path) 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/alembic/util/compat.py", line 82, in load_module_py 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage spec.loader.exec_module(module) 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "", line 678, in exec_module 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "", line 219, in _call_with_frames_removed 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/octavia/db/migration/alembic_migrations/env.py", line 88, in 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage run_migrations_online() 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/octavia/db/migration/alembic_migrations/env.py", line 72, in run_migrations_online 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage poolclass=pool.NullPool) 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/__init__.py", line 424, in create_engine 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage return strategy.create(*args, **kwargs) 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/strategies.py", line 52, in create 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage plugins = u._instantiate_plugins(kwargs) 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage AttributeError: 'NoneType' object has no attribute '_instantiate_plugins' - 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage - - My reference test is devstack which runs this under python2.7, could - this be a Py3 regression? + 2018-10-09 07:34:52.971 11688 ERROR octavia-db-manage -- 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-db-manage upgrade head fails with Traceback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1796811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796811] Re: octavia-db-manage upgrade head fails with Traceback
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-db-manage upgrade head fails with Traceback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1796811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823718] [NEW] Installation fails with Python3.7 SyntaxError on Ubuntu Disco
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 up python3-libmaas (0.6.0-0ubuntu1) ... File "/usr/lib/python3/dist-packages/maas/client/__init__.py", line 8 from .utils.async import asynchronous ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/maas/client/bones/__init__.py", line 23 from ..utils.async import asynchronous ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/maas/client/bones/helpers.py", line 31 from ..utils.async import asynchronous ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/maas/client/flesh/controllers.py", line 16 from ..utils.async import asynchronous ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/maas/client/flesh/fabrics.py", line 15 from ..utils.async import asynchronous ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/maas/client/flesh/machines.py", line 26 from ..utils.async import asynchronous ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/maas/client/flesh/profiles.py", line 28 from ..utils.async import asynchronous ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/maas/client/flesh/spaces.py", line 15 from ..utils.async import asynchronous ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/maas/client/flesh/subnets.py", line 15 from ..utils.async import asynchronous ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/maas/client/flesh/vlans.py", line 15 from ..utils.async import asynchronous ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/maas/client/viscera/__init__.py", line 49 from ..utils.async import Asynchronous ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/maas/client/viscera/events.py", line 25 from ..utils.async import is_loop_running ^ SyntaxError: invalid syntax dpkg: error processing package python3-libmaas (--configure): installed python3-libmaas package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: python3-libmaas E: Sub-process /usr/bin/dpkg returned an error code (1) root@direct-tiger:~# ** Affects: python-libmaas (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/1823718 Title: Installation fails with Python3.7 SyntaxError on Ubuntu Disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-libmaas/+bug/1823718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823718] Re: Installation fails with Python3.7 SyntaxError on Ubuntu Disco
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/bugs/1823718 Title: Installation fails with Python3.7 SyntaxError on Ubuntu Disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-libmaas/+bug/1823718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823729] [NEW] Incorrect dependency at Stein
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 23647 ERROR octavia-db-manage File
"/usr/bin/octavia-db-manage", line 10, in
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage sys.exit(main())
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage File
"/usr/lib/python3/dist-packages/octavia/db/migration/cli.py", line 138, in main
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage
CONF.command.func(config, CONF.command.name)
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage File
"/usr/lib/python3/dist-packages/octavia/db/migration/cli.py", line 68, in
do_upgrade
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage
do_alembic_command(config, cmd, revision, sql=CONF.command.sql)
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage File
"/usr/lib/python3/dist-packages/octavia/db/migration/cli.py", line 36, in
do_alembic_command
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage getattr(alembic_cmd,
cmd)(config, *args, **kwargs)
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage File
"/usr/lib/python3/dist-packages/alembic/command.py", line 254, in upgrade
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage script.run_env()
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage File
"/usr/lib/python3/dist-packages/alembic/script/base.py", line 427, in run_env
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage
util.load_python_file(self.dir, 'env.py')
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage File
"/usr/lib/python3/dist-packages/alembic/util/pyfiles.py", line 81, in
load_python_file
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage module =
load_module_py(module_id, path)
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage File
"/usr/lib/python3/dist-packages/alembic/util/compat.py", line 82, in
load_module_py
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage
spec.loader.exec_module(module)
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage File "", line 678, in exec_module
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage File "", line 219, in _call_with_frames_removed
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage File
"/usr/lib/python3/dist-packages/octavia/db/migration/alembic_migrations/env.py",
line 88, in
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage
run_migrations_online()
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage File
"/usr/lib/python3/dist-packages/octavia/db/migration/alembic_migrations/env.py",
line 72, in run_migrations_online
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage
poolclass=pool.NullPool)
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage File
"/usr/lib/python3/dist-packages/sqlalchemy/engine/__init__.py", line 425, in
create_engine
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage return
strategy.create(*args, **kwargs)
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage File
"/usr/lib/python3/dist-packages/sqlalchemy/engine/strategies.py", line 81, in
create
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage dbapi =
dialect_cls.dbapi(**dbapi_args)
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage File
"/usr/lib/python3/dist-packages/sqlalchemy/dialects/mysql/mysqldb.py", line
102, in dbapi
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage return
__import__('MySQLdb')
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage ModuleNotFoundError: No
module named 'MySQLdb'
2019-04-08 13:57:50.232 23647 ERROR octavia-db-manage
Installing ``python3-mysqldb`` resolves the issue.
# apt show python3-octavia
# apt show python3-octavia
Package: python3-octavia
Version: 4.0.0~rc1-0ubuntu1~cloud0
Priority: optional
Section: python
Source: octavia
Maintainer: Ubuntu Developers
Original-Maintainer: Debian OpenStack
Installed-Size: 5,359 kB
Depends: alembic (>= 0.8.10), python3-alembic (>= 0.8.10), python3-babel (>=
2.3.4), python3-barbicanclient (>= 4.5.2), python3-castellan (>= 0.16.0),
python3-cotyledon (>= 1.3.0), python3-cryptography (>= 2.1),
python3-diskimage-builder (>= 1.1.2), python3-distro (>= 1.2.0), python3-flask
(>= 0.10), python3-futurist (>= 1.2.0), python3-glanceclient (>= 1:2.8.0),
python3-gunicorn (>= 19.0.0), python3-jinja2 (>= 2.10), python3-jsonschema (>=
2.6.0), python3-keystoneauth1 (>= 3.4.0), python3-keystonemiddleware (>=
4.17.0), python3-netifaces (>= 0.10.4), python3-neutronclient (>= 1:6.7.0),
python3-novaclient (>= 2:9.1.0), python3-octavia-lib (>= 1.1.1),
python3-openssl (>= 17.1.0), python3-oslo.config (>= 1:5.2.0),
python3-oslo.context (>= 1:2.19.2), python3-oslo.db (>= 4.27.0),
python3-oslo.i18n (>= 3.15.3), python3-oslo.log (>= 3.36.0),
python3-oslo.messaging (>= 5.29.0), python3-oslo.midd
[Bug 1823729] Re: Incorrect dependency at Stein
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 version fence this given UCA prior to Stein has the above mentioned patch. 0: https://github.com/openstack/charm-layer-openstack/blob/master/templates/parts/section-database 1: https://github.com/openstack/charm-interface-mysql-shared/blob/master/requires.py 2: https://github.com/openstack/charms.openstack/blob/e57acaacdbdf98813e905fecd07e69ce5c86378a/charms_openstack/adapters.py#L449 ** Also affects: charms.openstack Importance: Undecided Status: New ** Changed in: octavia (Ubuntu) Status: New => Invalid ** Changed in: charms.openstack Status: New => Triaged ** Changed in: charms.openstack Importance: Undecided => Critical -- 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 bug go to: https://bugs.launchpad.net/charms.openstack/+bug/1823729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823729] Re: Incorrect dependency at Stein
** 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 (fnordahl) ** Changed in: charms.openstack 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/1823729 Title: Incorrect dependency at Stein To manage notifications about this bug go to: https://bugs.launchpad.net/charms.openstack/+bug/1823729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823729] Re: Incorrect dependency at Stein
** 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: Incorrect dependency at Stein To manage notifications about this bug go to: https://bugs.launchpad.net/charms.openstack/+bug/1823729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823729] Re: Incorrect dependency at Stein
** 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 bug go to: https://bugs.launchpad.net/charms.openstack/+bug/1823729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823729] Re: Incorrect dependency at Stein
** 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 this bug go to: https://bugs.launchpad.net/charms.openstack/+bug/1823729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824154] [NEW] bionic/stein: python-ceph missing dependencies
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 packages actually are @ 13.2.4+dfsg1-0ubuntu1~cloud0 2019-04-10 05:43:55 INFO juju-log Reactive main running for hook install 2019-04-10 05:43:55 DEBUG juju-log tracer: set flag apt.queued_installs tracer: set flag apt.queued_installs tracer: set flag config.changed.install_keys tracer: set flag config.changed.install_sources tracer: set flag config.default.install_keys tracer: set flag config.default.install_sources tracer: ++ queue handler reactive/ceph_fs.py:61:install_ceph_base tracer: ++ queue handler reactive/ceph_fs.py:67:install_cephfs 2019-04-10 05:43:55 INFO juju-log Invoking reactive handler: reactive/ceph_fs.py:61:install_ceph_base 2019-04-10 05:43:56 DEBUG install Reading package lists... 2019-04-10 05:43:57 DEBUG install Building dependency tree... 2019-04-10 05:43:57 DEBUG install Reading state information... 2019-04-10 05:43:57 DEBUG install The following package was automatically installed and is no longer required: 2019-04-10 05:43:57 DEBUG install grub-pc-bin 2019-04-10 05:43:57 DEBUG install Use 'apt autoremove' to remove it. 2019-04-10 05:43:57 DEBUG install The following NEW packages will be installed: 2019-04-10 05:43:57 DEBUG install ubuntu-cloud-keyring 2019-04-10 05:43:57 DEBUG install 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 2019-04-10 05:43:57 DEBUG install Need to get 6008 B of archives. 2019-04-10 05:43:57 DEBUG install After this operation, 22.5 kB of additional disk space will be used. 2019-04-10 05:43:57 DEBUG install Get:1 http://nova.clouds.archive.ubuntu.com/ubuntu bionic-updates/main amd64 ubuntu-cloud-keyring all 2018.09.18.1~18.04.0 [6008 B] 2019-04-10 05:43:57 DEBUG install Fetched 6008 B in 0s (45.5 kB/s) 2019-04-10 05:43:57 DEBUG install Selecting previously unselected package ubuntu-cloud-keyring. (Reading database ... 66836 files and directories currently installed.) 2019-04-10 05:43:57 DEBUG install Preparing to unpack .../ubuntu-cloud-keyring_2018.09.18.1~18.04.0_all.deb ... 2019-04-10 05:43:57 DEBUG install Unpacking ubuntu-cloud-keyring (2018.09.18.1~18.04.0) ... 2019-04-10 05:43:57 DEBUG install Setting up ubuntu-cloud-keyring (2018.09.18.1~18.04.0) ... 2019-04-10 05:43:58 INFO juju-log Invoking reactive handler: reactive/ceph_fs.py:67:install_cephfs 2019-04-10 05:43:59 DEBUG install Hit:1 http://nova.clouds.archive.ubuntu.com/ubuntu bionic InRelease 2019-04-10 05:43:59 DEBUG install Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease 2019-04-10 05:43:59 DEBUG install Hit:3 http://nova.clouds.archive.ubuntu.com/ubuntu bionic-updates InRelease 2019-04-10 05:43:59 DEBUG install Ign:4 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/stein InRelease 2019-04-10 05:43:59 DEBUG install Hit:5 http://nova.clouds.archive.ubuntu.com/ubuntu bionic-backports InRelease 2019-04-10 05:43:59 DEBUG install Get:6 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/stein Release [7882 B] 2019-04-10 05:43:59 DEBUG install Get:7 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/stein Release.gpg [543 B] 2019-04-10 05:43:59 DEBUG install Get:8 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/stein/main amd64 Packages [177 kB] 2019-04-10 05:44:00 DEBUG install Fetched 186 kB in 1s (170 kB/s) 2019-04-10 05:44:01 DEBUG install Reading package lists... tracer: ++ queue handler reactive/apt.py:43:install_queued 2019-04-10 05:44:01 INFO juju-log Invoking reactive handler: reactive/apt.py:43:install_queued 2019-04-10 05:44:01 DEBUG install Reading package lists... 2019-04-10 05:44:02 DEBUG install Building dependency tree... 2019-04-10 05:44:02 DEBUG install Reading state information... 2019-04-10 05:44:02 DEBUG install btrfs-tools is already the newest version (4.15.1-1build1). 2019-04-10 05:44:02 DEBUG install gdisk is already the newest version (1.0.3-1). 2019-04-10 05:44:02 DEBUG install xfsprogs is already the newest version (4.9.0+nmu1ubuntu2). 2019-04-10 05:44:02 DEBUG install Some packages could not be installed. This may mean that you have 2019-04-10 05:44:02 DEBUG install requested an impossible situation or if you are using the unstable 2019-04-10 05:44:02 DEBUG install distribution that some required packages have not yet been created 2019-04-10 05:44:02 DEBUG install or been moved out of Incoming. 2019-04-10 05:44:02 DEBUG install The following information may help to resolve the situation: 2019-04-10 05:44:02 DEBUG install 2019-04-10 05:44:02 DEBUG install The following packages have unmet dependencies: 2019-04-10 05:44:02 DEBUG install python-ceph : Depends: python-cephfs (>= 13.2.1+dfsg1-0ubuntu3~cloud0) but it is not going to be installed 2019-0
[Bug 1863711] [NEW] [focal] `ovsdb-tool` not in `openvswitch-common`
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: ovsdb-tool: not found Feb 18 06:46:15 juju-e5e5a4-zaza-0bd44e19b938-4 ovn-ctl[14536]: * Creating cluster database /var/lib/ovn/ovnnb_db.db # ovsdb-tool Command 'ovsdb-tool' not found, but can be installed with: apt install openvswitch-switch ** Affects: openvswitch (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/1863711 Title: [focal] `ovsdb-tool` not in `openvswitch-common` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1863711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865127] [NEW] ovn-controller: No bridge for localnet port is not an error
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 binding without any chassis affiliation. It is then up to the user to configure chassis with external connectivity by adding a mapping under the `external_ids:ovn-bridge-mappings` key in the Open_vSwitch table of the local OVS instance. This may be some chassis or all chassis depending on end user requirements. At present `ovn-controller` will repeatedly log an error on chassis without mapping for a localnet port while in reality it is not an error. https://patchwork.ozlabs.org/patch/1245848/ ** Affects: ovn (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/1865127 Title: ovn-controller: No bridge for localnet port is not an error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1865127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820976] Re: librbd: mirror pool status occasionally leads to segmentation fault
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820976 Title: librbd: mirror pool status occasionally leads to segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-rbd-mirror/+bug/1820976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813582] [NEW] Update to 12.2.8 leads to SIGSEGV Segmentation fault in python3-rados
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.1" 200 249
RESP: [200] Connection: Keep-Alive Content-Length: 249 Content-Type:
application/json Date: Mon, 28 Jan 2019 11:34:39 GMT Keep-Alive: timeout=5,
max=100 Server: Apache/2.4.29 (Ubuntu) Vary: X-Auth-Token X-Distribution:
Ubuntu x-openstack-request-id: req-d74445b8-1567-41d0-b741-a27000a80f14
RESP BODY: {"version": {"status": "stable", "updated": "2018-02-28T00:00:00Z",
"media-types": [{"base": "application/json", "type":
"application/vnd.openstack.identity-v3+json"}], "id": "v3.10", "links":
[{"href": "http://10.5.0.38:5000/v3/";, "rel": "self"}]}}
GET call to http://10.5.0.38:5000/v3 used request id
req-d74445b8-1567-41d0-b741-a27000a80f14
Making authentication request to http://10.5.0.38:5000/v3/auth/tokens
http://10.5.0.38:5000 "POST /v3/auth/tokens HTTP/1.1" 201 1780
{"token": {"is_domain": false, "methods": ["password"], "roles": [{"id":
"5a1b23e27bbe47609df2ed5aae809543", "name": "Admin"}, {"id":
"9499c375bc694f55891f5c2ed5b89a90", "name": "Member"}], "is_admin_project":
true, "project": {"domain": {"id": "d008601304584178a632480f1b5658f1", "name":
"admin_domain"}, "id": "efd4af8ba3c147379f140e0fcf03c1a0", "name": "admin"},
"catalog": [{"endpoints": [{"url": "http://10.5.0.38:35357/v3";, "interface":
"admin", "region": "RegionOne", "region_id": "RegionOne", "id":
"564d822b8912406ca8ca86ff0e6fdde3"}, {"url": "http://10.5.0.38:5000/v3";,
"interface": "public", "region": "RegionOne", "region_id": "RegionOne", "id":
"56e351a2cff74c24beebf951cea8f099"}, {"url": "http://10.5.0.38:5000/v3";,
"interface": "internal", "region": "RegionOne", "region_id": "RegionOne", "id":
"f451dcf182b14bdd9955f4d526011bf9"}], "type": "identity", "id":
"f4528ee1a55e434488244066eae3bb70", "name": "keystone"}, {"endpoints": [{"url":
"http://10.5.0.17:8041";, "interface": "internal", "region": "RegionOne",
"region_id": "RegionOne", "id": "93b7789c73f24134971a99cf9773e45c"}, {"url":
"http://10.5.0.17:8041";, "interface": "admin", "region": "RegionOne",
"region_id": "RegionOne", "id": "e2c3aea790d54df89e4c36b815ce0f18"}, {"url":
"http://10.5.0.17:8041";, "interface": "public", "region": "RegionOne",
"region_id": "RegionOne", "id": "f20ba6de8db8453bbd57cfc9f0e18e51"}], "type":
"metric", "id": "39131ce26e2a40f18b56a89f61d76bce", "name": "gnocchi"}],
"expires_at": "2019-01-28T12:34:39.00Z", "user": {"password_expires_at":
null, "domain": {"id": "d008601304584178a632480f1b5658f1", "name":
"admin_domain"}, "id": "f656e0c9ff90432ca6a16fbcf689c39b", "name": "admin"},
"audit_ids": ["ORciQMnASuaRQBdBa6uuIg"], "issued_at":
"2019-01-28T11:34:39.00Z"}}
REQ: curl -g -i -X GET http://10.5.0.17:8041/v1/status?details=False -H
"Accept: application/json, */*" -H "User-Agent: gnocchi keystoneauth1/3.10.0
python-requests/2.18.4 CPython/3.6.7" -H "X-Auth-Token:
{SHA1}f16e953e1742980359603aef5a704611dd23a651"
Starting new HTTP connection (1): 10.5.0.17
http://10.5.0.17:8041 "GET /v1/status?details=False HTTP/1.1" 500 608
RESP: [500] Connection: close Content-Length: 608 Content-Type: text/html;
charset=iso-8859-1 Date: Mon, 28 Jan 2019 11:34:39 GMT Server: Apache/2.4.29
(Ubuntu)
RESP BODY: Omitted, Content-Type is set to text/html; charset=iso-8859-1. Only
application/json responses have their bodies logged.
500 Internal Server Error
Internal Server Error
The server encountered an internal error or
misconfiguration and was unable to complete
your request.
Please contact the server administrator at
[no address given] to inform them of the time this error occurred,
and the actions you performed just before this error.
More information about this error may be available
in the server error log.
Apache/2.4.29 (Ubuntu) Server at 10.5.0.17 Port 8041
(HTTP 500)
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cliff/app.py", line 400, in
run_subcommand
result = cmd.run(parsed_args)
File "/usr/lib/python3/dist-packages/cliff/display.py", line 116, in run
column_names, data = self.take_action(parsed_args)
File "/usr/lib/python3/dist-packages/gnocchiclient/v1/status_cli.py", line
23, in take_action
status = utils.get_client(self).status.get()
File "/usr/lib/python3/dist-packages/gnocchiclient/v1/status.py", line 21, in
get
return self._get(self.url + '?details=%s' % details).json()
File "/usr/lib/python3/dist-packages/gnocchiclient/v1/base.py", line 37, in
_get
return self.client.api.get(*args, **kwargs)
File "/usr/lib/python3/dist-packages/keystoneauth1/adapter.py", line 328, in
get
return self.request(url, 'GET', **kwargs)
File "/usr/lib/python3/dist-packages/gnocchiclient/client.py", line 52, in
request
raise exceptions.from_response(r
[Bug 1813582] Re: Update to 12.2.8 leads to SIGSEGV Segmentation fault in python3-rados
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 fault in python3-rados To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1813582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813582] Re: Update to 12.2.8 leads to SIGSEGV Segmentation fault in python3-rados
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 Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.,amulet==1.21.0,aodhclient==1.1.1,appdirs==1.4.3,asn1crypto==0.24.0,Babel==2.6.0,backports.os==0.1.1,blessings==1.6,bundletester==0.12.2,certifi==2018.11.29,cffi==1.11.5,chardet==3.0.4,charm-tools==2.4.5,charmhelpers==0.19.6,Cheetah3==3.1.0,cliff==2.14.0,cmd2==0.8.9,colander==1.0b1,configparser==3.7.1,contextlib2==0.5.5,coverage==4.5.2,cryptography==2.5,debtcollector==1.20.0,decorator==4.3.2,distro==1.3.0,distro-info==0.0.0,docutils==0.14,dogpile.cache==0.7.1,entrypoints==0.3,enum34==1.1.6,extras==1.0.0,fixtures==3.0.0,flake8==2.4.1,funcsigs==1.0.2,functools32==3.2.3.post2,future==0.17.1,futures==3.2.0,futurist==1.8.0,gnocchiclient==3.1.1,httplib2==0.12.0,idna==2.8,importlib-metadata==0.8,ipaddress==1.0.22,iso8601==0.1.12,Jinja2==2.10,jmespath==0.9.3,jsonpatch==1.23,jsonpointer==2.0,jsonschema==2.5.1,juju-deployer==0.11.0,juju-wait==2.5.0,jujubundlelib==0.5.6,jujuclient==0.54.0,keyring==17.1.1,keystoneauth1==3.11.2,launchpadlib==1.10.6,lazr.authentication==0.1.3,lazr.restfulclient==0.14.2,lazr.uri==1.0.3,libcharmstore==0.0.9,linecache2==1.0.0,macaroonbakery==1.2.1,MarkupSafe==1.1.0,mccabe==0.3.1,mock==2.0.0,monotonic==1.5,msgpack==0.6.1,munch==2.3.2,netaddr==0.7.19,netifaces==0.10.9,nose==1.3.7,oauth==1.0.1,oauthlib==3.0.1,openstacksdk==0.23.0,os-client-config==1.31.2,os-service-types==1.5.0,os-testr==1.0.0,osc-lib==1.12.0,oslo.config==6.8.0,oslo.context==2.22.0,oslo.i18n==3.23.0,oslo.log==3.42.2,oslo.serialization==2.28.1,oslo.utils==3.40.1,otherstuf==1.1.0,parse==1.11.1,path.py==11.5.0,pathlib2==2.3.3,pathspec==0.3.4,pbr==5.1.1,pep8==1.7.1,pika==0.13.0,pkg-resources==0.0.0,prettytable==0.7.2,protobuf==3.6.1,pycparser==2.19,pyflakes==0.8.1,pyinotify==0.9.6,pymacaroons==0.13.0,PyNaCl==1.3.0,pyOpenSSL==19.0.0,pyparsing==2.3.1,pyperclip==1.7.0,pyRFC3339==1.1,python-barbicanclient==4.8.1,python-ceilometerclient==2.9.0,python-cinderclient==4.1.0,python-dateutil==2.7.5,python-designateclient==2.11.0,python-glanceclient==2.15.0,python-heatclient==1.17.0,python-keystoneclient==3.18.0,python-manilaclient==1.26.0,python-mimeparse==1.6.0,python-neutronclient==6.11.0,python-novaclient==11.1.0,python-openstackclient==3.17.0,python-subunit==1.3.0,python-swiftclient==3.6.0,pytz==2018.9,pyudev==0.21.0,PyYAML==3.11,requests==2.21.0,requestsexceptions==1.4.0,rfc3986==1.2.0,ruamel.base==1.0.0,ruamel.ordereddict==0.4.13,ruamel.yaml==0.10.23,scandir==1.9.0,SecretStorage==2.3.1,simplejson==3.16.0,six==1.12.0,stestr==2.2.0,stevedore==1.30.0,stuf==0.9.16,subprocess32==3.5.3,Tempita==0.5.2,testresources==2.0.1,testtools==2.3.0,theblues==0.5.1,traceback2==1.4.0,translationstring==1.3,unicodecsv==0.14.1,unittest2==1.1.0,urllib3==1.24.1,virtualenv==16.3.0,voluptuous==0.11.5,wadllib==1.3.3,warlock==1.3.0,wcwidth==0.1.7,websocket-client==0.40.0,wrapt==1.11.1,wsgi-intercept==1.8.0,zipp==0.3.3,zope.interface==4.6.0 func27-smoke runtests: PYTHONHASHSEED='0' func27-smoke runtests: commands[0] | bundletester -vl DEBUG -r json -o func-results.json gate-basic-bionic-queens --no-destroy DEBUG:bundletester.utils:Updating JUJU_MODEL: "" -> "fnordahl-serverstack:admin/default" DEBUG:root:Bootstrap environment: fnordahl-serverstack:admin/default DEBUG:deployer.env:Connecting to fnordahl-serverstack:admin/default... DEBUG:jujuclient.connector:Connecting to wss://10.5.0.3:17070/model/8bab6f50-03a0-4ef8-8df1-1bf865dfae3f/api DEBUG:deployer.env:Connected. DEBUG:deployer.env: Terminating machines forcefully INFO:deployer.env: Waiting for machine termination DEBUG:jujuclient.connector:Connecting to wss://10.5.0.3:17070/model/8bab6f50-03a0-4ef8-8df1-1bf865dfae3f/api DEBUG:root:Waiting for applications to be removed... DEBUG:runner:call ['/tmp/tox/func27-smoke/bin/charm-proof'] (cwd: /tmp/bundletester-_FRmpX/gnocchi) DEBUG:runner:I: `display-name` not provided, add for custom naming in the UI DEBUG:runner:I: config.yaml: option ssl_key has no default value DEBUG:runner:I: config.yaml: option os-admin-network has no default value DEBUG:runner:I: config.yaml: option haproxy-server-timeout has no default value DEBUG:runner:I: config.yaml: option os-public-hostname has no default value DEBUG:runner:I: config.yaml: option vip has no default value DEBUG:runner:I: config.yaml: option os-admin-hostname has no default value DEBUG:runner:I: config.yaml: option haproxy-client-timeout has no default value DEBUG:runner:I: config.yaml: option ssl_ca has no default value DEBUG:runner:I: config.yaml: option ssl_cert has no default value DEBUG:runner:I: config.yaml: option os-internal-network has no default value DEBUG:runner:I: config.yaml: option haproxy-queue-time
[Bug 1813582] Re: Update to 12.2.8 leads to SIGSEGV Segmentation fault in python3-rados
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-31 14:45:34,402 _auto_wait_for_status DEBUG: Default extended status wait match: contains READY (case-insensitive) DEBUG:runner:2019-01-31 14:45:34,402 _auto_wait_for_status DEBUG: Excluding services from extended status match: ['mysql', 'mongodb', 'memcached', 'ceilometer'] DEBUG:runner:2019-01-31 14:45:34,403 _auto_wait_for_status DEBUG: Waiting up to 5400s for extended status on services: ['percona-cluster', 'rabbitmq-server', 'keystone', 'ceph-osd', 'ceph-mon', 'gnocchi'] DEBUG:runner:2019-01-31 14:45:37,063 _auto_wait_for_status INFO: OK DEBUG:runner:2019-01-31 14:45:37,064 get_default_keystone_session DEBUG: Authenticating keystone admin... DEBUG:runner:2019-01-31 14:45:37,876 run_ceilometer_upgrade_action DEBUG: Checking ceilometer-upgrade DEBUG:runner:2019-01-31 14:46:06,343 _auto_wait_for_status INFO: Waiting for extended status on units for 5400s... DEBUG:runner:2019-01-31 14:46:06,344 _auto_wait_for_status DEBUG: Default extended status wait match: contains READY (case-insensitive) DEBUG:runner:2019-01-31 14:46:06,344 _auto_wait_for_status DEBUG: Excluding services from extended status match: ['mysql', 'mongodb', 'memcached'] DEBUG:runner:2019-01-31 14:46:06,344 _auto_wait_for_status DEBUG: Waiting up to 5400s for extended status on services: ['ceilometer', 'percona-cluster', 'rabbitmq-server', 'keystone', 'ceph-osd', 'ceph-mon', 'gnocchi'] DEBUG:runner:2019-01-31 14:46:37,214 _auto_wait_for_status INFO: OK DEBUG:runner:2019-01-31 14:46:37,214 run_ceilometer_upgrade_action DEBUG: OK DEBUG:runner:2019-01-31 14:46:37,214 test_100_services DEBUG: Checking system services on units... DEBUG:runner:2019-01-31 14:46:37,214 validate_services_by_name DEBUG: Checking status of system services... DEBUG:runner:2019-01-31 14:46:41,478 get_ubuntu_release_from_sentry DEBUG: gnocchi/0 lsb_release: bionic DEBUG:runner:2019-01-31 14:46:42,763 validate_services_by_name DEBUG: gnocchi/0 `sudo service haproxy status` returned 0 DEBUG:runner:2019-01-31 14:46:44,045 validate_services_by_name DEBUG: gnocchi/0 `sudo service gnocchi-metricd status` returned 0 DEBUG:runner:2019-01-31 14:46:45,348 validate_services_by_name DEBUG: gnocchi/0 `sudo service apache2 status` returned 0 DEBUG:runner:2019-01-31 14:46:45,349 test_100_services DEBUG: OK DEBUG:runner:2019-01-31 14:46:45,349 test_200_api_connection DEBUG: Checking api functionality... DEBUG:runner:2019-01-31 14:46:45,960 test_200_api_connection DEBUG: OK DEBUG:runner:2019-01-31 14:46:49,735 run_action WARNING: charmhelpers.contrib.amulet.utils.run_action has been deprecated for amulet.run_action DEBUG:runner:2019-01-31 14:47:01,997 run_action WARNING: charmhelpers.contrib.amulet.utils.run_action has been deprecated for amulet.run_action DEBUG:runner:Exit Code: 0 DEBUG:bundletester.utils:Updating JUJU_MODEL: "fnordahl-serverstack:admin/default" -> "" summary _ func27-smoke: commands succeeded congratulations :) ubuntu@test:~/src/charm-gnocchi$ source ../openstack-charm-testing/rcs/openrc Using Keystone v3 API ubuntu@test:~/src/charm-gnocchi$ juju ssh gnocchi/0 'dpkg -l |grep ceph' ii ceph-common 12.2.8-0ubuntu0.18.04.2 amd64common utilities to mount and interact with a ceph storage cluster ii libcephfs2 12.2.8-0ubuntu0.18.04.2 amd64Ceph distributed file system client library ii python-cephfs 12.2.8-0ubuntu0.18.04.2 amd64Python libraries for the Ceph libcephfs library Connection to 10.5.0.26 closed. ubuntu@test:~/src/charm-gnocchi$ gnocchi status +-+---+ | Field | Value | +-+---+ | storage/number of metric having measures to process | 0 | | storage/total number of measures to process | 0 | +-+---+ ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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 fault in python3-rados To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1813582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubu
[Bug 1813582] Re: Update to 12.2.8 leads to SIGSEGV Segmentation fault in python3-rados
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 Released => New -- 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 fault in python3-rados To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1813582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813582] Re: Update to 12.2.8 leads to SIGSEGV Segmentation fault in python3-rados
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 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 fault in python3-rados To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1813582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861671] [NEW] No init script / systemd service for ``octavia-driver-agent``
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 charm and can be viewed in https://review.opendev.org/#/c/705257/ ** Affects: octavia (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/1861671 Title: No init script / systemd service for ``octavia-driver-agent`` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1861671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869132] [NEW] [focal] /etc/keystone owned by root
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 Architecture Description +++-==--- ii keystone 2:17.0.0~b3~git2020032415.9f9040257-0ubuntu1 all OpenStack identity service - Daemons root@juju-c9e7e0-4:/etc# ls -ld /etc drwxr-xr-x 82 root root 154 Mar 26 06:51 /etc root@juju-c9e7e0-4:/etc# ls -ld /etc/keystone drwxr-x--- 3 root keystone 8 Mar 26 06:51 /etc/keystone root@juju-c9e7e0-4:/etc# ls -l /etc/keystone total 215 -rw-r- 1 root keystone 2303 Mar 24 19:01 default_catalog.templates -rw-r- 1 root keystone 104730 Mar 24 19:02 keystone.conf -rw-r- 1 root keystone 96670 Mar 24 19:02 keystone.policy.yaml -rw-r- 1 root keystone 1046 Mar 24 19:02 logging.conf drwxrwxr-x 2 keystone keystone 2 Mar 26 06:51 policy.d -rw-r- 1 root keystone665 Mar 24 19:01 sso_callback_template.html root@juju-c9e7e0-4:/etc# ** Affects: keystone (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/1869132 Title: [focal] /etc/keystone owned by root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1869132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869132] Re: [focal] /etc/keystone owned by root
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 with Permission denied when it attempts to create a directory under /etc/keystone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869132 Title: [focal] /etc/keystone owned by root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1869132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869324] [NEW] civetweb: 0x7f4763896580: cannot bind to 70: 13 (Permission denied)
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 well be a upstream issue. ** Affects: ceph (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/1869324 Title: civetweb: 0x7f4763896580: cannot bind to 70: 13 (Permission denied) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1869324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869132] Re: [focal] /etc/keystone owned by root
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-ae56ef-0:~# ls -ld /etc/keystone/ drwxr-x--- 5 keystone keystone 11 Mar 27 13:32 /etc/keystone/ root@juju-ae56ef-0:~# ls -ld /etc/keystone/fernet-keys/ drwx-- 2 keystone keystone 4 Mar 27 13:32 /etc/keystone/fernet-keys/ $ juju status keystone ModelController Cloud/Region Version SLA Timestamp default localhost-localhost localhost/localhost 2.7.4unsupported 14:40:28+01:00 App Version Status Scale Charm Store Rev OS Notes keystone 17.0.0~b3~gi... waiting 1 keystone jujucharms 489 ubuntu mysql-router 8.0.19 waiting 1 mysql-router jujucharms8 ubuntu Unit Workload Agent Machine Public address Ports Message keystone/0*waiting idle 010.219.3.82 5000/tcp Incomplete relations: database mysql-router/0* waiting idle10.219.3.82 'db-router' incomplete, MySQL Router not yet bootstrapped Machine StateDNS Inst idSeries AZ Message 0started 10.219.3.82 juju-ae56ef-0 focal Running -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869132 Title: [focal] /etc/keystone owned by root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1869132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d
** 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/rsyslog-xenial.debdiff ** Patch removed: "rsyslog-artful.debdiff" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4901470/+files/rsyslog-artful.debdiff ** Patch removed: "rsyslog-yakkety.debdiff" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900272/+files/rsyslog-yakkety.debdiff ** Patch removed: "rsyslog-zesty.debdiff" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900271/+files/rsyslog-zesty.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668639 Title: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d
** 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/1668639 Title: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d
** 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-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/1668639 Title: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures
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 up in MaaS: https://gist.githubusercontent.com/fnordahl/f6e6b734484363e980a6e7fa2cfe51de/raw/b64d83225e0d11c1bd236e4f4625b0c466ad755f/maas-ubuntu-proposed.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737640 Title: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628289] Re: snapd should depend on squashfuse (for use in containers)
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 something? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628289 Title: snapd should depend on squashfuse (for use in containers) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1628289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835697] Re: Upgrade to zfsutils-linux 0.8.1-1ubuntu5 fails on Ubuntu 19.10
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-import-scan.service is a disabled or a static unit not running, not starting it. Job for zfs-mount.service failed because the control process exited with error code. See "systemctl status zfs-mount.service" and "journalctl -xe" for details. invoke-rc.d: initscript zfs-mount, action "restart" failed. ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2019-09-06 06:07:23 CEST; 3ms ago Docs: man:zfs(8) Process: 6487 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 6487 (code=exited, status=1/FAILURE) Sep 06 06:07:23 frode-Precision-7530 systemd[1]: Starting Mount ZFS filesystems... Sep 06 06:07:23 frode-Precision-7530 zfs[6487]: cannot mount '/root': directory is not empty Sep 06 06:07:23 frode-Precision-7530 zfs[6487]: cannot mount '/var/lib': directory is not empty Sep 06 06:07:23 frode-Precision-7530 systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE Sep 06 06:07:23 frode-Precision-7530 systemd[1]: zfs-mount.service: Failed with result 'exit-code'. Sep 06 06:07:23 frode-Precision-7530 systemd[1]: Failed to start Mount ZFS filesystems. dpkg: error processing package zfsutils-linux (--configure): installed zfsutils-linux package post-installation script subprocess returned error exit status 1 No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835697 Title: Upgrade to zfsutils-linux 0.8.1-1ubuntu5 fails on Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1835697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835697] Re: Upgrade to zfsutils-linux 0.8.1-1ubuntu5 fails on Ubuntu 19.10
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 conflict when in a ZFS-on-root scenario? My ZFS filesystems are definitely mounted, live and kicking $ sudo systemctl status zfs-mount ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2019-09-06 06:17:35 CEST; 3min 28s ago Docs: man:zfs(8) Process: 2995 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 2995 (code=exited, status=1/FAILURE) Sep 06 06:17:35 frode-Precision-7530 systemd[1]: Starting Mount ZFS filesystems... Sep 06 06:17:35 frode-Precision-7530 zfs[2995]: cannot mount '/root': directory is not empty Sep 06 06:17:35 frode-Precision-7530 zfs[2995]: cannot mount '/var/lib': directory is not empty Sep 06 06:17:35 frode-Precision-7530 systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE Sep 06 06:17:35 frode-Precision-7530 systemd[1]: zfs-mount.service: Failed with result 'exit-code'. Sep 06 06:17:35 frode-Precision-7530 systemd[1]: Failed to start Mount ZFS filesystems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835697 Title: Upgrade to zfsutils-linux 0.8.1-1ubuntu5 fails on Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1835697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843366] [NEW] [eoan][2.30] locale woes, 12 hour clock and other issues
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 workstation. The most visible change is that my terminal will format the clock in 12 hour AM/PM format regardless of settings. I am able to restore the 24 hour clock by forcing LC_TIME to C. However, this also affects applications doing datetime calculations, an example being the Zaza test framework written in Python suddenly generating TLS certificates with a not valid until time into the future, with the consequence of test runs failing. So there is something more unnerving than a mere time display format change going on. Will try to dig up some more details, but wanted to flag this here in case someone know more about what has changed and/or are seeing similar issues. ** Affects: glibc (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/1843366 Title: [eoan][2.30] locale woes, 12 hour clock and other issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1843366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843366] Re: [eoan][2.30] locale woes, 12 hour clock and other issues
$ 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_IDENTIFICATION=en_US.UTF-8 LC_ALL= ** Changed in: glibc (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843366 Title: [eoan][2.30] locale woes, 12 hour clock and other issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1843366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843366] Re: [eoan][2.30] locale woes, 12 hour clock and other issues
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://bugs.launchpad.net/bugs/1843366 Title: [eoan][2.30] locale woes, 12 hour clock and other issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1843366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843426] [NEW] Time format setting no longer applies to terminal shell
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 amd64utilities to configure the GNOME desktop ii gnome-control-center-data 1:3.33.90-1ubuntu2 all configuration applets for GNOME - data files ii gnome-control-center-faces 1:3.33.90-1ubuntu2 all utilities to configure the GNOME desktop - faces images After a recent change in Eoan, I believe it was glibc, the Time Format selector between 24-hour and 12-hour no longer applies to the terminal. I would like my system to use the English language and English formats, but I do want it to adhere to my local custom of displaying the 24-hour clock. Until recently this worked automatically, but now I have to manually set LC_TIME to ``C.UTF-8`` to get the desired effect. While this may have been my responsibility all along the behavior did change recently. ** Affects: gnome-control-center (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/1843426 Title: Time format setting no longer applies to terminal shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1843426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843426] Re: Time format setting no longer applies to terminal shell
$ 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.UTF-8 LC_ADDRESS DEFAULT=en_US.UTF-8 LC_TELEPHONEDEFAULT=en_US.UTF-8 LC_MEASUREMENT DEFAULT=en_US.UTF-8 LC_IDENTIFICATION DEFAULT=en_US.UTF-8 PAPERSIZE DEFAULT=letter hum, that could explain where the LANGUAGE=en came from when I looked around previously. Would that affect clock output at all? I'll have a look. Just wanted to note that I have not created the .pam_environment file and my system has gone through the loops of upgrading to Eoan from Bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843426 Title: Time format setting no longer applies to terminal shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1843426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843582] [NEW] ovn: additional systemd units requested
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 controller to install on each participant in a OVN network - ``ovn-central`` - ovn-northd daemon, OVSDB database schemas for the Northbound and Southbound databases - ``ovn-controller-vtep`` - Controller to integrate with hardware VTEP-enabled switches The ``ovn-central`` package contains a SysV init script that reads some parameters from ``/etc/default/ovn-central`` and calls out to the ``/usr/share/openvswitch/scripts/ovn-ctl`` script from the ``ovn- common`` package. The default mode of operation for this init script is to start ovsdb- server processes for both the Northbound and Southbound databases and then start the ``ovn-northd`` daemon. While working on the design of the charm [0] it has been identified [1][2] that the Southbound DB has different scaling requirements than the other components, and its load will be relative to the number of transport nodes (controllers) in the system [3]. As a consequence the charm will aim to support separate placement of the Southbound DB. To accomplish this I would need individual service control for the ``ovn-northd`` daemon, the ``ovsdb-server`` for Northound DB and the ``ovsdb-server`` for Southbound DB. You get to pull most levers by controlling command line arguments through the ``OVN_CTL_OPTS`` variable in ``/etc/default/ovn-central``, including starting the ``ovn-northd`` daemon by itself. But you do not get to individual service control of the Northbound- and Southbound- databases. What I propose is that we add systemd units for ``nb_ovsdb`` and ``sb_ovsdb`` which pulls in variables from /etc/default/ in similar fashion as the existing ``ovn-central`` script and then calls out to ``/usr/share/openvswitch/scripts/ovn-ctl`` with ``start_nb_ovsdb`` and ``start_sb_ovsdb`` parameters respectively. I guess a generic approach would be to support this for all the start and stop targets the ``ovn-ctl`` script supports, but I only have use for individual control of ``ovn-northd``, ``nb_ovsdb`` and ``sb_ovsdb`` at this point. A argument for not just using the ``ovn-ctl`` script directly from the charm is that there are well established workflows in our charm frameworks for service control through init scripts, and it would be useful to be able to use that directly. Side note: the OVN project have recently moved into its own set of repositories [4] and we may need to consider creating a separate source package for it at some point. 0: https://specs.openstack.org/openstack/charm-specs/specs/train/approved/charm-openstack-ovn.html 1: https://review.opendev.org/#/c/680415/ 2: https://pbs.twimg.com/media/EDr3IPXXsAAg2Vb.jpg 3: http://www.openvswitch.org/support/dist-docs/ovn-architecture.7.html 4: https://github.com/ovn-org/ ** Affects: openvswitch (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/1843582 Title: ovn: additional systemd units requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1843582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832265] Re: py3: inconsistent encoding of token fields
** 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 this bug go to: https://bugs.launchpad.net/charm-keystone-ldap/+bug/1832265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828534] Re: [19.04][Queens -> Rocky] Upgrading to Rocky resulted in "Services not running that should be: designate-producer"
** 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 running that should be: designate-producer" To manage notifications about this bug go to: https://bugs.launchpad.net/charm-designate/+bug/1828534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831642] [NEW] amphora-agent package, its init script and configuration file
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 reference:
https://opendev.org/openstack/octavia/src/branch/master/octavia/controller/worker/tasks/compute_tasks.py#L89
Config-drive contents:
root@amphora-82c4877a-d932-49af-b590-7859c6edb84c:~# mount /dev/sr0 /mnt
mount: /mnt: WARNING: device write-protected, mounted read-only.
root@amphora-82c4877a-d932-49af-b590-7859c6edb84c:~# cd /mnt
root@amphora-82c4877a-d932-49af-b590-7859c6edb84c:/mnt# ls -l
total 4
dr-xr-xr-x 4 root root 2048 Jun 4 13:03 ec2
dr-xr-xr-x 12 root root 2048 Jun 4 13:03 openstack
root@amphora-82c4877a-d932-49af-b590-7859c6edb84c:/mnt# cd openstack/
root@amphora-82c4877a-d932-49af-b590-7859c6edb84c:/mnt/openstack# ls -l
total 20
dr-xr-xr-x 2 root root 2048 Jun 4 13:03 2012-08-10
dr-xr-xr-x 2 root root 2048 Jun 4 13:03 2013-04-04
dr-xr-xr-x 2 root root 2048 Jun 4 13:03 2013-10-17
dr-xr-xr-x 2 root root 2048 Jun 4 13:03 2015-10-15
dr-xr-xr-x 2 root root 2048 Jun 4 13:03 2016-06-30
dr-xr-xr-x 2 root root 2048 Jun 4 13:03 2016-10-06
dr-xr-xr-x 2 root root 2048 Jun 4 13:03 2017-02-22
dr-xr-xr-x 2 root root 2048 Jun 4 13:03 2018-08-27
dr-xr-xr-x 2 root root 2048 Jun 4 13:03 content
dr-xr-xr-x 2 root root 2048 Jun 4 13:03 latest
root@amphora-82c4877a-d932-49af-b590-7859c6edb84c:/mnt/openstack# cd latest
root@amphora-82c4877a-d932-49af-b590-7859c6edb84c:/mnt/openstack/latest# ls -l
total 4
-r--r--r-- 1 root root 2136 Jun 4 13:03 meta_data.json
-r--r--r-- 1 root root 506 Jun 4 13:03 network_data.json
-r--r--r-- 1 root root2 Jun 4 13:03 vendor_data.json
-r--r--r-- 1 root root 14 Jun 4 13:03 vendor_data2.json
root@amphora-82c4877a-d932-49af-b590-7859c6edb84c:/mnt/openstack/latest# cat
meta_data.json
{"uuid": "0aedb1b1-46a1-4734-aa1c-f1aed62f427f", "files": [{"path":
"/etc/octavia/amphora-agent.conf", "content_path": "/content/"}, {"path":
"/etc/octavia/certs/client_ca.pem", "content_path": "/content/0001"}, {"path":
"/etc/octavia/certs/server.pem", "content_path": "/content/0002"}],
"admin_pass": "boHNY7N32jAb", "public_keys": {"test": "ssh-rsa
B3NzaC1yc2EDAQABAAABAQCi1Mwv77hDyu/68syJflcPO6oKGkUBzjBIcPwC1hNdWvVHyaBI2lm6millJIBVQdLYHh/MJe6FRz6iOOZ7eBnnzd63D8GOTS6UnpX+F7BmT8ICH1CBqbnVAn+LJxCfzs8+Q706jTXqkiU3Rgl7A6v8+Tqqu6VsI+4/lODj43LXhlN4+tt3jvbNCXXo0d4jRBEysEnINjsmxcNce3sCeAaDY1trC8DsGAFUJxoPi8We2qYPVvHbWj7yLgDzJULf05TEIxR1IvbaU/2K+eT2ITyPdTgsSCP7E2DAK8WtKiOWJRBiOwE46yT6Os/rAjoIrzv9IqPDnp97uxf1Ia1jD4Ah
ubuntu@test\n"}, "keys": [{"name": "test", "type": "ssh", "data": "ssh-rsa
B3NzaC1yc2EDAQABAAABAQCi1Mwv77hDyu/68syJflcPO6oKGkUBzjBIcPwC1hNdWvVHyaBI2lm6millJIBVQdLYHh/MJe6FRz6iOOZ7eBnnzd63D8GOTS6UnpX+F7BmT8ICH1CBqbnVAn+LJxCfzs8+Q706jTXqkiU3Rgl7A6v8+Tqqu6VsI+4/lODj43LXhlN4+tt3jvbNCXXo0d4jRBEysEnINjsmxcNce3sCeAaDY1trC8DsGAFUJxoPi8We2qYPVvHbWj7yLgDzJULf05TEIxR1IvbaU/2K+eT2ITyPdTgsSCP7E2DAK8WtKiOWJRBiOwE46yT6Os/rAjoIrzv9IqPDnp97uxf1Ia1jD4Ah
ubuntu@test\n"}], "hostname":
"amphora-82c4877a-d932-49af-b590-7859c6edb84c.novalocal", "name":
"amphora-82c4877a-d932-49af-b590-7859c6edb84c", "launch_index": 0,
"availability_zone": "nova", "random_seed":
"TbGbfew/Ie7ZwKL2CIOYTiJ5mMAEddIsbzAK3Tg8aa6pitSZiY67oLXgadY7TUhNGon5ZsW7hnUCmAweHbNMXsYOs5jkMljURsuh55ihJb7+Uz57kNTQaMaLi6mLy0PmHXdhpzWs3PJRxddQGtzLa4k1j7dX4O4otViD4kHwVp8K/ZfDORVd8Ot+xOP9oYkvTCf76kjGl/z8Jnwhm83YlOGvjcYxKVEKAy87QAb7k0qxzcai8as1zwck3nyHe6Frl/lHelywoTadSelXkWUCqxfbN/594bTjQobMZPp2O4iixGjeQMzU0utOGJM+AYG9VjZvI9uZ9T3WW+eERn9vg+TOk0mF7bCTNgtzdd2K5zBthTf+g1+3rBNWp4/iSqbHrA+PHK2CEKwiM/5SIarW4/raoBrsDMep47P2ax4XMcZKuTXKZjcnht1hOblDRKtW65fgELkv5/aixCJmD4k5ks9u4FDJgWxdGRZzTNSpWbmnz+qPOk2R+/n3KkIeevQHR3U341Xq4Oyxff1d/9+unRNU6ujC7o7HyDynlnTYcjOHlUcg1KW5Wl7PZ7qredWVmNgwTdotNPJJQe6E9TZjjeVxXBzTxHGoZuvzAKkew5r60Ky2LyUAm+sZiv5Y9pp/P55Hejntg5U9JvVq870m+dqVbLeqdRWYT3G3ysLX/HI=",
"project_id": "964a97ca99c6489b817dd8fb8b6ee740", "devices":
[]}root@amphora-82c4877a-d932-49af-b590-7859c6edb84c:/mnt/openstack/latest# cd
..
root@amphora-82c4877a-d932-49af-b590-7859c6edb84c:/mnt/openstack# cd content/
root@amphora-82c4877a-d932-49af-b590-7859c6edb84c:/mnt/openstack/content# ls -l
total 6
-r--r--r-- 1 root root 727 Jun 4 13:03
-r--r--r-- 1 root root 1135 Jun 4 13:03 0001
-r--r--r-- 1 root root 2875 Jun 4 13:03 0002
root@amphora-82c4877a-d932-49af-b590-7859c6edb84c:/mnt/openstack/content# cat
[DEFAULT]
debug = True
[haproxy_amphora]
base_cert_dir = /var/lib/octavia/certs
base_path = /var/lib/octavia
bind_host = ::
bind_port = 9443
haproxy_cmd = /usr/sbin/haproxy
respawn_count = 2
respawn_interval = 2
use_upstart = True
[health_manager]
controller_ip_port_list = fc00:4f4a:d87f:9a6c:f816:3eff:fe58:3dd0:,
fc00:4f4a:d87f:9a6c:f816:3eff:fee0:a2d9:,
fc00:4f4a:d87f:9a6c:f816:3eff:fee4:669b:
heartbe
[Bug 1831642] Re: amphora-agent package, its init script and configuration file
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.launchpad.net/bugs/1831642 Title: amphora-agent package, its init script and configuration file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1831642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853431] [NEW] [rfe] northd: Add `status` management command
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: openvswitch (Ubuntu) Importance: Undecided Status: New ** Patch added: "openvswitch-northd-status.patch" https://bugs.launchpad.net/bugs/1853431/+attachment/5306840/+files/openvswitch-northd-status.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853431 Title: [rfe] northd: Add `status` management command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1853431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
