[Bug 2028830] Re: [mpt3sas, UBSAN] ]linux 6.5-rc give error messages at boot
** Also affects: linux-meta-hwe-6.5 (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/2028830 Title: [mpt3sas, UBSAN] ]linux 6.5-rc give error messages at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073643] Re: [Errno 2] No such file or directory: '/usr/lib/python3/dist- packages/ironic/drivers/raid_config_schema.json'.
** Description changed: [Impact] The python3-ironic package available in Ubuntu Noble fails when trying to load the ironic drivers, because there is a json schema file missing. This is because the package is not including it when it was built. Stacktrace: 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service [None req-ee11f675-cc73-4c39-92d5-9a2ace917501 - - - - - -] Error starting thread.: ironic.common.exception.DriverLoadError: Driver, hardware type or interface no-raid could - not be loaded. Reason: [Errno 2] No such file or directory: '/usr/lib/python3/dist-packages/ironic/drivers/raid_config_schema.json'. + not be loaded. Reason: [Errno 2] No such file or directory: '/usr/lib/python3/dist-packages/ironic/drivers/raid_config_schema.json'. 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service Traceback (most recent call last): 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service File "/usr/lib/python3/dist-packages/stevedore/extension.py", line 206, in _load_plugins 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service ext = self._load_one_plugin(ep, 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service File "/usr/lib/python3/dist-packages/stevedore/named.py", line 156, in _load_one_plugin 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service return super(NamedExtensionManager, self)._load_one_plugin( 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service File "/usr/lib/python3/dist-packages/stevedore/extension.py", line 242, in _load_one_plugin 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service obj = plugin(*invoke_args, **invoke_kwds) 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service File "/usr/lib/python3/dist-packages/ironic/drivers/base.py", line 1461, in __init__ 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service with open(RAID_CONFIG_SCHEMA, 'r') as raid_schema_fobj: 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/python3/dist-packages/ironic/drivers/raid_config_schema.json' + + + [ Test Plan ] + + 1. Install python3-ironic: apt-get install python3-ironic + 2. Check the file /usr/lib/python3/dist- packages/ironic/drivers/raid_config_schema.json is available + + [ Where problems could occur ] + + This change will make the python3-ironic package larger in size since + it's including all files present in the released tarball, but not less. + A possible issue could be that unused files are installed in the system, + and this could be a problem for users producing OCI images, rocks and + cheaseled images. + + [ Other Info ] + + This patch[0] was used to test this fix in jammy-caracal -> jammy- + caracal-alt https://openstack-ci- + reports.ubuntu.com/artifacts/6e7/924544/2/check/jammy-caracal- + alt/6e746fb/ : SUCCESS in 59m 10s + + [0] https://review.opendev.org/c/openstack/charm-ironic- + conductor/+/924544 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073643 Title: [Errno 2] No such file or directory: '/usr/lib/python3/dist- packages/ironic/drivers/raid_config_schema.json'. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2073643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073643] [NEW] [Errno 2] No such file or directory: '/usr/lib/python3/dist- packages/ironic/drivers/raid_config_schema.json'.
Public bug reported: [Impact] The python3-ironic package available in Ubuntu Noble fails when trying to load the ironic drivers, because there is a json schema file missing. This is because the package is not including it when it was built. Stacktrace: 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service [None req-ee11f675-cc73-4c39-92d5-9a2ace917501 - - - - - -] Error starting thread.: ironic.common.exception.DriverLoadError: Driver, hardware type or interface no-raid could not be loaded. Reason: [Errno 2] No such file or directory: '/usr/lib/python3/dist-packages/ironic/drivers/raid_config_schema.json'. 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service Traceback (most recent call last): 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service File "/usr/lib/python3/dist-packages/stevedore/extension.py", line 206, in _load_plugins 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service ext = self._load_one_plugin(ep, 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service File "/usr/lib/python3/dist-packages/stevedore/named.py", line 156, in _load_one_plugin 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service return super(NamedExtensionManager, self)._load_one_plugin( 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service File "/usr/lib/python3/dist-packages/stevedore/extension.py", line 242, in _load_one_plugin 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service obj = plugin(*invoke_args, **invoke_kwds) 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service File "/usr/lib/python3/dist-packages/ironic/drivers/base.py", line 1461, in __init__ 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service with open(RAID_CONFIG_SCHEMA, 'r') as raid_schema_fobj: 2024-07-19 15:24:28.547 1009815 ERROR oslo_service.service FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/python3/dist-packages/ironic/drivers/raid_config_schema.json' ** Affects: cloud-archive Importance: Undecided Status: Triaged ** Affects: cloud-archive/caracal Importance: Undecided Status: Triaged ** Affects: ironic (Ubuntu) Importance: Critical Assignee: Felipe Reyes (freyes) Status: Triaged ** Affects: ironic (Ubuntu Noble) Importance: Undecided Status: Triaged ** Also affects: ironic (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/caracal Importance: Undecided Status: New ** Changed in: ironic (Ubuntu) Status: New => Triaged ** Changed in: cloud-archive Status: New => Triaged ** Changed in: cloud-archive/caracal Status: New => Triaged ** Changed in: ironic (Ubuntu Noble) Status: New => Triaged ** Changed in: ironic (Ubuntu) Importance: Undecided => Critical ** Changed in: ironic (Ubuntu) Assignee: (unassigned) => Felipe Reyes (freyes) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073643 Title: [Errno 2] No such file or directory: '/usr/lib/python3/dist- packages/ironic/drivers/raid_config_schema.json'. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2073643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038663] Re: no option to override the fixed_subnet when creating a new cluster
marking magnum-ui (ubuntu)/devel as invalid since the fix is part of the package shipped with Noble ** Changed in: magnum-ui (Ubuntu) Status: Confirmed => Invalid ** Changed in: cloud-archive Status: New => Invalid ** No longer affects: cloud-archive/caracal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038663 Title: no option to override the fixed_subnet when creating a new cluster To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2038663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038663] Re: no option to override the fixed_subnet when creating a new cluster
marking magnum-ui as fix released, since the patch landed during the Caracal devel cycle and it's part of magnum-ui-14.0.0 - https://github.com/openstack/magnum- ui/commit/6f6c3db282fe2f0e08ad69c557eb153858b0164a ** Changed in: magnum-ui 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/2038663 Title: no option to override the fixed_subnet when creating a new cluster To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2038663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038663] Re: no option to override the fixed_subnet when creating a new cluster
Zed is EOL ** Changed in: cloud-archive/zed Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038663 Title: no option to override the fixed_subnet when creating a new cluster To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2038663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038663] Re: no option to override the fixed_subnet when creating a new cluster
Marking Bobcat as won't fix since it's going EOL and this patch is not needed when doing upgrades. ** Changed in: cloud-archive/bobcat Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038663 Title: no option to override the fixed_subnet when creating a new cluster To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2038663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038663] Re: no option to override the fixed_subnet when creating a new cluster
Removing tasks for the releases that are EOL. ** No longer affects: cloud-archive/victoria ** No longer affects: cloud-archive/wallaby ** No longer affects: cloud-archive/xena -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038663 Title: no option to override the fixed_subnet when creating a new cluster To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2038663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038109] Re: Failed to create port on network , because fixed_ips included invalid subnet
Attaching debdiff for Jammy (Yoga) ** Patch added: "lp2038109_jammy.debdiff" https://bugs.launchpad.net/cloud-archive/zed/+bug/2038109/+attachment/5798101/+files/lp2038109_jammy.debdiff ** Changed in: magnum (Ubuntu Jammy) Status: New => 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/2038109 Title: Failed to create port on network , because fixed_ips included invalid subnet To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2038109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038109] Re: Failed to create port on network , because fixed_ips included invalid subnet
Attaching debdiff for Focal (Ussuri) ** Patch added: "lp2038109_focal.debdiff" https://bugs.launchpad.net/ubuntu/jammy/+source/magnum/+bug/2038109/+attachment/5798102/+files/lp2038109_focal.debdiff ** Changed in: magnum (Ubuntu Focal) Status: New => 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/2038109 Title: Failed to create port on network , because fixed_ips included invalid subnet To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2038109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038109] Re: Failed to create port on network , because fixed_ips included invalid subnet
Attaching debdiff for Antelope ** Patch added: "lp2038109_antelope.debdiff" https://bugs.launchpad.net/cloud-archive/+bug/2038109/+attachment/5798098/+files/lp2038109_antelope.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038109 Title: Failed to create port on network , because fixed_ips included invalid subnet To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2038109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038109] Re: Failed to create port on network , because fixed_ips included invalid subnet
Attaching debdiff for Zed ** Patch added: "lp2038109_zed.debdiff" https://bugs.launchpad.net/cloud-archive/+bug/2038109/+attachment/5798100/+files/lp2038109_zed.debdiff ** Changed in: cloud-archive/antelope Status: New => In Progress ** Changed in: cloud-archive/bobcat Status: New => In Progress ** Changed in: cloud-archive/zed Status: New => 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/2038109 Title: Failed to create port on network , because fixed_ips included invalid subnet To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2038109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038109] Re: Failed to create port on network , because fixed_ips included invalid subnet
Attaching debdiff for Bobcat ** Patch added: "lp2038109_bobcat.debdiff" https://bugs.launchpad.net/cloud-archive/+bug/2038109/+attachment/5798099/+files/lp2038109_bobcat.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038109 Title: Failed to create port on network , because fixed_ips included invalid subnet To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2038109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038109] Re: Failed to create port on network , because fixed_ips included invalid subnet
Marking Caracal as invalid since this patch is already included in the version shipped with OpenStack Caracal ** Also affects: magnum (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: magnum (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/yoga Importance: Undecided Status: New ** Also affects: cloud-archive/zed Importance: Undecided Status: New ** Also affects: cloud-archive/bobcat Importance: Undecided Status: New ** Also affects: cloud-archive/antelope Importance: Undecided Status: New ** Also affects: cloud-archive/ussuri Importance: Undecided Status: New ** Changed in: cloud-archive 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/2038109 Title: Failed to create port on network , because fixed_ips included invalid subnet To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2038109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041480] Re: Netplan 0.106.1-7ubuntu0.22.04.2 breaks mac address match
*** This bug is a duplicate of bug 2022947 *** https://bugs.launchpad.net/bugs/2022947 I'm having the following warnings when issuing 'netplan apply' for nics which are members of bonds (since they share the same mac address after they're brought up) WARNING:root:Cannot find unique matching interface for eno2 WARNING:root:Cannot find unique matching interface for eno1 WARNING:root:Cannot find unique matching interface for enp4s0f1 WARNING:root:Cannot find unique matching interface for enp4s0f0 I believe this is due to netifaces returning the spoofed mac address and not the permanent one [1][2]. [1] - https://github.com/canonical/netplan/blob/5df4140c49f242cb63efcd5edffe6a06419150fb/netplan/cli/commands/apply.py#L381 [2] - https://github.com/canonical/netplan/blob/5df4140c49f242cb63efcd5edffe6a06419150fb/netplan/cli/utils.py#L173 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2041480 Title: Netplan 0.106.1-7ubuntu0.22.04.2 breaks mac address match To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072526] Re: ERROR octavia.controller.worker.v2.controller_worker jinja2.exceptions.TemplateNotFound: amphora_agent_conf.template
** Changed in: octavia (Ubuntu) Assignee: James Page (james-page) => Felipe Reyes (freyes) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072526 Title: ERROR octavia.controller.worker.v2.controller_worker jinja2.exceptions.TemplateNotFound: amphora_agent_conf.template To manage notifications about this bug go to: https://bugs.launchpad.net/charm-octavia/+bug/2072526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072526] Re: ERROR octavia.controller.worker.v2.controller_worker jinja2.exceptions.TemplateNotFound: amphora_agent_conf.template
The Debian package in sid has this file - https://packages.debian.org/search?searchon=contents=amphora_agent_conf.template=path=unstable=any FilePackages /usr/lib/python3/dist-packages/octavia/amphorae/backends/agent/templates/amphora_agent_conf.template python3-octavia ** Changed in: charm-octavia Status: New => Invalid ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/caracal Importance: Undecided Status: New ** Also affects: octavia (Ubuntu Noble) 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/2072526 Title: ERROR octavia.controller.worker.v2.controller_worker jinja2.exceptions.TemplateNotFound: amphora_agent_conf.template To manage notifications about this bug go to: https://bugs.launchpad.net/charm-octavia/+bug/2072526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072526] Re: ERROR octavia.controller.worker.v2.controller_worker jinja2.exceptions.TemplateNotFound: amphora_agent_conf.template
Adding charm-octavia in case the charm is at fault, although everything seems to point out to a packaging issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072526 Title: ERROR octavia.controller.worker.v2.controller_worker jinja2.exceptions.TemplateNotFound: amphora_agent_conf.template To manage notifications about this bug go to: https://bugs.launchpad.net/charm-octavia/+bug/2072526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072526] [NEW] ERROR octavia.controller.worker.v2.controller_worker jinja2.exceptions.TemplateNotFound: amphora_agent_conf.template
Public bug reported: [Impact] Octavia fails to provision the amphora, the stacktrace logged is: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/taskflow/engines/action_engine/executor.py", line 52, in _execute_task result = task.execute(**arguments) File "/usr/lib/python3/dist-packages/octavia/controller/worker/v2/tasks/compute_tasks.py", line 199, in execute return super().execute( File "/usr/lib/python3/dist-packages/octavia/controller/worker/v2/tasks/compute_tasks.py", line 122, in execute agent_cfg = agent_jinja_cfg.AgentJinjaTemplater() File "/usr/lib/python3/dist-packages/octavia/amphorae/backends/agent/agent_jinja_cfg.py", line 34, in __init__ self.agent_template = jinja_env.get_template( File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 997, in get_template return self._load_template(name, globals) File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 958, in _load_template template = self.loader.load(self, name, self.make_globals(globals)) File "/usr/lib/python3/dist-packages/jinja2/loaders.py", line 125, in load source, filename, uptodate = self.get_source(environment, name) File "/usr/lib/python3/dist-packages/jinja2/loaders.py", line 214, in get_source raise TemplateNotFound(template) jinja2.exceptions.TemplateNotFound: amphora_agent_conf.template When searching for a package where this file is, apt-file can't find any. https://packages.ubuntu.com/search?searchon=contents=amphora_agent_conf.template=exactfilename=noble=any This file has been around for many years - https://opendev.org/openstack/octavia/commits/branch/master/octavia/amphorae/backends/agent/templates/amphora_agent_conf.template - and the code that's trying to use it hasn't really received changes during the Caracal cycle - https://opendev.org/openstack/octavia/commits/branch/master/octavia/amphorae/backends/agent/agent_jinja_cfg.py [Environment] * OpenStack 2024.1 (Caracal) * python3-octavia 1:14.0.0-0ubuntu1~cloud0 ** Affects: charm-octavia Importance: Undecided Status: New ** Affects: octavia (Ubuntu) Importance: Undecided Status: New ** Also affects: charm-octavia 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/2072526 Title: ERROR octavia.controller.worker.v2.controller_worker jinja2.exceptions.TemplateNotFound: amphora_agent_conf.template To manage notifications about this bug go to: https://bugs.launchpad.net/charm-octavia/+bug/2072526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756785] Re: lxcfs startup failues because fuse directory not empty
I have no way to reproduce this issue reliably. Next time I notice it, I will make sure to get the files list before deleting them. It can take days or months. :( For example, I wonder if this issue happens when OS crashes and reboots ungracefully, or when the VM gets down abruptely for whatever reason and doesn't give the chance for lxcfs to clean up its stuff. But since it's a mountpoint, I expect that lxcfs would in fact never write anything to /var/lib/lxcfs (before it's mounted). So, I'm afraid I can't provide any more clues to help fix this issue at this point (but will update if I get more data). I just wanted to cast my support for the initial suggestion of "nuking" the directory in case it's not empty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756785 Title: lxcfs startup failues because fuse directory not empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1756785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1982969] Re: Missing binary package for octavia prometheus-proxy
I believe this is not a RFE/Wishlist, but rather a deb packaging issue,
the package python3-octavia already ships the prometheus-proxy binary,
but fails to include it's systemd unit[1].
By just creating the unit everything works as expected.
---
root@amphora-90334dfd-e3fa-4977-bf74-a6a9ab69ea01:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.6 LTS
Release:20.04
Codename: focal
root@amphora-90334dfd-e3fa-4977-bf74-a6a9ab69ea01:~# dpkg -S
/usr/bin/prometheus-proxy
python3-octavia: /usr/bin/prometheus-proxy
root@amphora-90334dfd-e3fa-4977-bf74-a6a9ab69ea01:~# dpkg -S
/usr/lib/systemd/system/prometheus-proxy.service
dpkg-query: no path found matching pattern
/usr/lib/systemd/system/prometheus-proxy.service
root@amphora-90334dfd-e3fa-4977-bf74-a6a9ab69ea01:~# ls -l
/usr/lib/systemd/system/prometheus-proxy.service
ls: cannot access '/usr/lib/systemd/system/prometheus-proxy.service': No such
file or directory
root@amphora-90334dfd-e3fa-4977-bf74-a6a9ab69ea01:~# cat >
/usr/lib/systemd/system/prometheus-proxy.service < /var/run/prometheus-proxy.pid"
PIDFile=/var/run/prometheus-proxy.pid
[Install]
WantedBy=multi-user.target
EOF
root@amphora-90334dfd-e3fa-4977-bf74-a6a9ab69ea01:~# systemctl daemon-reload
root@amphora-90334dfd-e3fa-4977-bf74-a6a9ab69ea01:~# systemctl start
prometheus-proxy
root@amphora-90334dfd-e3fa-4977-bf74-a6a9ab69ea01:~# systemctl status
prometheus-proxy
● prometheus-proxy.service - OpenStack Octavia Prometheus Proxy
Loaded: loaded (/lib/systemd/system/prometheus-proxy.service; enabled;
vendor preset: enabled)
Active: active (running) since Wed 2024-07-03 15:48:42 UTC; 3s ago
Process: 57115 ExecStartPost=/bin/sh -c echo $MAINPID >
/var/run/prometheus-proxy.pid (code=exited, status=0/SUCCESS)
Main PID: 57114 (prometheus-prox)
Tasks: 2 (limit: 2324)
Memory: 14.8M
CGroup: /system.slice/prometheus-proxy.service
└─57114 /usr/bin/python3 /usr/bin/prometheus-proxy
Jul 03 15:48:42 amphora-90334dfd-e3fa-4977-bf74-a6a9ab69ea01 systemd[1]:
Starting OpenStack Octavia Prometheus Proxy...
Jul 03 15:48:42 amphora-90334dfd-e3fa-4977-bf74-a6a9ab69ea01 systemd[1]:
Started OpenStack Octavia Prometheus Proxy.
root@amphora-90334dfd-e3fa-4977-bf74-a6a9ab69ea01:~# ip netns exec
amphora-haproxy bash
root@amphora-90334dfd-e3fa-4977-bf74-a6a9ab69ea01:~# curl -s
http://127.0.0.1:9102|tail -n 5
# HELP octavia_member_idle_connections_limit Limit on the number of available
idle connections
# TYPE octavia_member_idle_connections_limit gauge
octavia_member_idle_connections_limit{pool="de7983a9-f1fd-40e1-afe0-fd7830d462d7:734b3ed3-738d-4a79-8189-5e025d19491d",member="3a4e01ff-8e99-490c-9f12-bc7e9eaa4b65"}
0
octavia_member_idle_connections_limit{pool="de7983a9-f1fd-40e1-afe0-fd7830d462d7:734b3ed3-738d-4a79-8189-5e025d19491d",member="6fba9350-5f9a-49e1-8148-eb9dcd97001e"}
0
octavia_member_idle_connections_limit{pool="de7983a9-f1fd-40e1-afe0-fd7830d462d7:734b3ed3-738d-4a79-8189-5e025d19491d",member="240b3896-b404-4381-ba74-9b8c23e40fbc"}
0
---
[1]https://github.com/openstack/octavia/blob/master/elements/amphora-
agent/install.d/amphora-agent-source-install/prometheus-proxy.service
** Changed in: snap-octavia-diskimage-retrofit
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1982969
Title:
Missing binary package for octavia prometheus-proxy
To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-octavia-diskimage-retrofit/+bug/1982969/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756785] Re: lxcfs startup failues because fuse directory not empty
I've got to say I stumble upon this issue every now and then. And in my case, my /var/lib/lxcfs directory is dedicated to lxcfs. I don't know how come it gets populated with files, but every time I just need to delete the folder to make it work again. Given the directory is exclusive to lxcfs I totally agree it would be nice if lxcfs had an option like --clean-up-if-not-empty, so that I don't need to manually intervene every time this issue happens for whatever reason. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756785 Title: lxcfs startup failues because fuse directory not empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1756785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process
Hey Jeremy, I opened a new bug, https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2067519 Would you give me any tips to try to debug this further ? The error is coming from this section of the code: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/master/src/grd-settings.c#L303 And from the message it seems that it is some credential file misisng, or corrupted. Maybe this could be something simple ? I already tried to find information on the web but I can't find anything related to this. I am almost giving up and using something else. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/206 Title: gnome-remote-desktop.service: Failed to determine user credentials: No such process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067519] Re: gnome-remote-de[891989]: Init file credentials failed: Key file does not start with a group
Hi, I still have this issue. Any tips on what I can do to try to debug this further would be appreciated. Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067519 Title: gnome-remote-de[891989]: Init file credentials failed: Key file does not start with a group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2067519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038663] Re: no option to override the fixed_subnet when creating a new cluster
** Also affects: magnum-ui (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: magnum-ui (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/victoria Importance: Undecided Status: New ** Also affects: cloud-archive/bobcat Importance: Undecided Status: New ** Also affects: cloud-archive/ussuri Importance: Undecided Status: New ** Also affects: cloud-archive/wallaby Importance: Undecided Status: New ** Also affects: cloud-archive/antelope Importance: Undecided Status: New ** Also affects: cloud-archive/caracal Importance: Undecided Status: New ** Also affects: cloud-archive/xena Importance: Undecided Status: New ** Also affects: cloud-archive/yoga Importance: Undecided Status: New ** Also affects: cloud-archive/zed 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/2038663 Title: no option to override the fixed_subnet when creating a new cluster To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2038663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067519] [NEW] gnome-remote-de[891989]: Init file credentials failed: Key file does not start with a group
Public bug reported: Hi, I am encountering a problem similar to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/206 I do have the latest package installed: $ apt search gnome-remote Sorting... Done Full Text Search... Done gnome-remote-desktop/noble-updates,noble-security,now 46.2-1~ubuntu24.04.2 amd64 [installed,automatic] Remote desktop daemon for GNOME using PipeWire I tried forcing re-install: sudo apt-get install --reinstall gnome-remote-desktop I tried running these workaround commands described here: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/206 sudo systemd-tmpfiles --create /usr/lib/tmpfiles.d/gnome-remote-desktop-tmpfiles.conf sudo systemd-sysusers /usr/lib/sysusers.d/gnome-remote-desktop-sysusers.conf sudo systemd-tmpfiles --create /usr/lib/tmpfiles.d/gnome-remote-desktop-tmpfiles.conf Any help on how to fix it ? I am still seeing the problem: May 28 10:06:18 cuica systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... May 28 10:06:18 cuica gnome-remote-de[891989]: Init TPM credentials failed because Failed to initialize transmission interface context: tcti:IO failure, using GKeyFile as fallback May 28 10:06:18 cuica gnome-remote-de[891989]: Init file credentials failed: Key file does not start with a group May 28 10:06:18 cuica gnome-remote-desktop-daemon[891989]: ** May 28 10:06:18 cuica gnome-remote-desktop-daemon[891989]: ERROR:../src/grd-settings.c:345:grd_settings_constructed: assertion failed: (priv->credentials) May 28 10:06:18 cuica gnome-remote-desktop-daemon[891989]: Bail out! ERROR:../src/grd-settings.c:345:grd_settings_constructed: assertion failed: (priv->credentials) May 28 10:06:18 cuica systemd[1]: gnome-remote-desktop.service: Main process exited, code=dumped, status=6/ABRT May 28 10:06:18 cuica systemd[1]: gnome-remote-desktop.service: Failed with result 'core-dump'. May 28 10:06:18 cuica systemd[1]: Failed to start gnome-remote-desktop.service - GNOME Remote Desktop. May 28 10:06:19 cuica systemd[1]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 5. May 28 10:06:19 cuica systemd[1]: gnome-remote-desktop.service: Start request repeated too quickly. May 28 10:06:19 cuica systemd[1]: gnome-remote-desktop.service: Failed with result 'core-dump'. May 28 10:06:19 cuica systemd[1]: Failed to start gnome-remote-desktop.service - GNOME Remote Desktop. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-remote-desktop 46.2-1~ubuntu24.04.2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 29 22:17:54 2024 InstallationDate: Installed on 2024-04-28 (31 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: gnome-remote-desktop UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-remote-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067519 Title: gnome-remote-de[891989]: Init file credentials failed: Key file does not start with a group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2067519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process
Hi, I am encountering the same issue described here. I do have the latest package installed: $ apt search gnome-remote Sorting... Done Full Text Search... Done gnome-remote-desktop/noble-updates,noble-security,now 46.2-1~ubuntu24.04.2 amd64 [installed,automatic] Remote desktop daemon for GNOME using PipeWire I tried forcing re-install: sudo apt-get install --reinstall gnome-remote-desktop Any help on how to fix it ? I am still seeing the problem: May 28 10:06:18 cuica systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... May 28 10:06:18 cuica gnome-remote-de[891989]: Init TPM credentials failed because Failed to initialize transmission interface context: tcti:IO failure, using GKeyFile as fallback May 28 10:06:18 cuica gnome-remote-de[891989]: Init file credentials failed: Key file does not start with a group May 28 10:06:18 cuica gnome-remote-desktop-daemon[891989]: ** May 28 10:06:18 cuica gnome-remote-desktop-daemon[891989]: ERROR:../src/grd-settings.c:345:grd_settings_constructed: assertion failed: (priv->credentials) May 28 10:06:18 cuica gnome-remote-desktop-daemon[891989]: Bail out! ERROR:../src/grd-settings.c:345:grd_settings_constructed: assertion failed: (priv->credentials) May 28 10:06:18 cuica systemd[1]: gnome-remote-desktop.service: Main process exited, code=dumped, status=6/ABRT May 28 10:06:18 cuica systemd[1]: gnome-remote-desktop.service: Failed with result 'core-dump'. May 28 10:06:18 cuica systemd[1]: Failed to start gnome-remote-desktop.service - GNOME Remote Desktop. May 28 10:06:19 cuica systemd[1]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 5. May 28 10:06:19 cuica systemd[1]: gnome-remote-desktop.service: Start request repeated too quickly. May 28 10:06:19 cuica systemd[1]: gnome-remote-desktop.service: Failed with result 'core-dump'. May 28 10:06:19 cuica systemd[1]: Failed to start gnome-remote-desktop.service - GNOME Remote Desktop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/206 Title: gnome-remote-desktop.service: Failed to determine user credentials: No such process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064647] Re: Documentation for how to enable gnome-remote-desktop on a completly headless system
I saw Jeremy had a fix. What should I do to get the fix ? I already did the usual apt-get update upgrade etc... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064647 Title: Documentation for how to enable gnome-remote-desktop on a completly headless system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2064647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064647] Re: Documentation for how to enable gnome-remote-desktop on a completly headless system
Hey Robert, I had the exact same issue as you had. How did you solve it ? You mentioned trying to run the grdctrl command. Which ones ? I couldn't find in the link you provide above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064647 Title: Documentation for how to enable gnome-remote-desktop on a completly headless system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2064647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064717] Re: ceph-volume needs "packaging" module
** Changed in: charm-ceph-osd Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064717 Title: ceph-volume needs "packaging" module To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-osd/+bug/2064717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064717] Re: ceph-volume needs "packaging" module
** Changed in: charm-ceph-osd/reef Assignee: (unassigned) => Felipe Reyes (freyes) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064717 Title: ceph-volume needs "packaging" module To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-osd/+bug/2064717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064717] Re: ceph-volume needs "packaging" module
** Also affects: charm-ceph-osd Importance: Undecided Status: New ** Also affects: charm-ceph-osd/reef Importance: Undecided Status: New ** Changed in: charm-ceph-osd Status: New => Fix Committed ** Changed in: charm-ceph-osd Assignee: (unassigned) => Peter Sabaini (peter-sabaini) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064717 Title: ceph-volume needs "packaging" module To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-osd/+bug/2064717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064190] Re: Failed to pre-delete resources for cluster XXXX
** Changed in: cloud-archive/victoria Status: New => Won't Fix ** Changed in: cloud-archive/wallaby Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064190 Title: Failed to pre-delete resources for cluster To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2064190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064190] [NEW] Failed to pre-delete resources for cluster XXXX
Public bug reported:
[Impact]
When deleting a cluster (k8s) and the load balancer associated to it has
already been deleted, a 404 error is returned by Heat which raises a
heatclient.exc.HTTPNotFound exception.
Full stack trace:
[req-7a8d257d-9cca-4d2d-b108-de8f33f60ae1 - - - - -] Exception during message
handling: magnum.common.exception.PreDeletionFailed: Failed to pre-delete
resources for cluster 6d553e2f-74bb-4dbe-9fd1-1a123b76530b, error: ERROR: The
Stack (37032d90-66f1-41dd-b584-67d10f438bd9) could not be found..
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/magnum/common/octavia.py", line 109, in
delete_loadbalancers
lb_resources = heat_client.resources.list(
File "/usr/lib/python3/dist-packages/heatclient/v1/resources.py", line 70, in
list
return self._list(url, "resources")
File "/usr/lib/python3/dist-packages/heatclient/common/base.py", line 114, in
_list
body = self.client.get(url).json()
File "/usr/lib/python3/dist-packages/heatclient/common/http.py", line 289, in
get
return self.client_request("GET", url, **kwargs)
File "/usr/lib/python3/dist-packages/heatclient/common/http.py", line 282, in
client_request
resp, body = self.json_request(method, url, **kwargs)
File "/usr/lib/python3/dist-packages/heatclient/common/http.py", line 271, in
json_request
resp = self._http_request(url, method, **kwargs)
File "/usr/lib/python3/dist-packages/heatclient/common/http.py", line 234, in
_http_request
raise exc.from_response(resp)
heatclient.exc.HTTPNotFound: ERROR: The Stack
(37032d90-66f1-41dd-b584-67d10f438bd9) could not be found.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/server.py", line 165,
in _process_incoming
res = self.dispatcher.dispatch(message)
File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/dispatcher.py", line
276, in dispatch
return self._do_dispatch(endpoint, method, ctxt, args)
File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/dispatcher.py", line
196, in _do_dispatch
result = func(ctxt, **new_args)
File
"/usr/lib/python3/dist-packages/magnum/conductor/handlers/cluster_conductor.py",
line 191, in cluster_delete
cluster_driver.delete_cluster(context, cluster)
File "/usr/lib/python3/dist-packages/magnum/drivers/heat/driver.py", line
162, in delete_cluster
self.pre_delete_cluster(context, cluster)
File "/usr/lib/python3/dist-packages/magnum/drivers/heat/driver.py", line
307, in pre_delete_cluster
octavia.delete_loadbalancers(context, cluster)
File "/usr/lib/python3/dist-packages/magnum/common/octavia.py", line 130, in
delete_loadbalancers
raise exception.PreDeletionFailed(cluster_uuid=cluster.uuid,
magnum.common.exception.PreDeletionFailed: Failed to pre-delete resources for
cluster 6d553e2f-74bb-4dbe-9fd1-1a123b76530b, error: ERROR: The Stack
(37032d90-66f1-41dd-b584-67d10f438bd9) could not be found..
2024-03-12 14:38:35.878 3553570 ERROR oslo_messaging.rpc.server
[ Test Plan ]
TBD
[ Where problems could occur ]
TBD
[Other Info]
This issue has been fixed in Magnum by commit
https://opendev.org/openstack/magnum/commit/4888f706c8a0280971df398cbc1ff06ad5d63e7f
( https://review.opendev.org/c/openstack/magnum/+/818563 ), this was
released in Magnum-14.0.0 (Yoga release) and backported to 13.1.0
(Xena), and even when it was backported into the stable/wallaby branch (
https://review.opendev.org/c/openstack/magnum/+/820334 ), no releases
were cut after it was merged
** Affects: cloud-archive
Importance: Undecided
Status: Invalid
** Affects: cloud-archive/ussuri
Importance: Undecided
Status: New
** Affects: cloud-archive/victoria
Importance: Undecided
Status: New
** Affects: cloud-archive/wallaby
Importance: Undecided
Status: New
** Affects: magnum (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: magnum (Ubuntu Focal)
Importance: Undecided
Assignee: Felipe Reyes (freyes)
Status: New
** Also affects: magnum (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: magnum (Ubuntu)
Status: New => Invalid
** Changed in: magnum (Ubuntu Focal)
Assignee: (unassigned) => Felipe Reyes (freyes)
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/victoria
Importance: Undecided
Status: New
** Also affects: cloud-archive/wallaby
Importance: Undecided
Status: New
** Also affects: cloud-archive/ussuri
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New => Invalid
--
You received this bug notification because you are a member
[Bug 2063077] Re: Keyboard does not work after waking up from suspend with 5.15.0-105 (but works with 5.15.0-101)
Hi, I can confirm that linux 5.15.0.106.106 (package version 5.15.0-106.116) from -proposed works, without the issue. Thanks! FF PS: To clarify: the previous versions I had were 5.15.0-101.111 and -105.115, not -102.112. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063077 Title: Keyboard does not work after waking up from suspend with 5.15.0-105 (but works with 5.15.0-101) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063077] [NEW] Keyboard does not work after waking up from suspend with 5.15.0-105 (but works with 5.15.0-101)
Public bug reported: Dear Ubuntu maintainers, I think I found a regression in linux 5.15.0-105. In the past few days, my keyboard stopped working after waking up from suspend (sleep), so I couldn't unlock my laptop. Various workarounds found on the internet helped, but I wanted to investigate if it was a gdm issue, grub, or a hardware failure. I managed to narrow it down to the kernel, which is why I'm filing this bug report. AFAICT the only keys that work are the keyboard lights and the brightness knobs (in the Fn functions). I can confirm that 5.15.0-105 has the issue, and I can consistently reproduce it with the following steps: 1. boot fresh with 5.15.0-105 2. login to my account 3. choose suspend from the power menu 4. wake up Following the same steps above with the last kernel available does not cause the issue (package version 5.15.0-101.111). I'll keep using that one for the time being. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-105-generic 5.15.0-105.115 ProcVersionSignature: Ubuntu 5.15.0-105.115-generic 5.15.148 Uname: Linux 5.15.0-105-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philsf 5465 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 02:58:26 2024 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ab7cb5b3-b98e-4d3a-8923-b75a557d5ddc InstallationDate: Installed on 2018-06-07 (2145 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28c1 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-105-generic root=UUID=670af779-d73e-4cb4-b272-d3240de0c998 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-5.15.0-105-generic N/A linux-backports-modules-5.15.0-105-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2023 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0TXW78 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/06/2023:br1.14:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0TXW78:rvrA00:cvnDellInc.:ct10:cvr:sku0810: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Summary changed: - Keyboard does not work after waking up from suspend in 5.15.0-105 (but works for 5.15.0-101) + Keyboard does not work after waking up from suspend with 5.15.0-105 (but works with 5.15.0-101) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063077 Title: Keyboard does not work after waking up from suspend with 5.15.0-105 (but works with 5.15.0-101) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926249] Re: postcopy migration fails in hirsute (solved)
Hi @ajkavanagh, this affects focal-hwe, jammy and will affect any new releases unless this sysctl is set to 1. ** No longer affects: charm-nova-compute ** Also affects: qemu Importance: Undecided Status: New ** No longer affects: qemu ** Also affects: charm-nova-compute 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/1926249 Title: postcopy migration fails in hirsute (solved) To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1926249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926249] Re: postcopy migration fails in hirsute (solved)
juju config live-migration-permit-post-copy on the nova-compute charm, could auto enable vm.unprivileged_userfaultfd=1, or at least state this requirement on it's description. ** Also affects: charm-nova-compute 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/1926249 Title: postcopy migration fails in hirsute (solved) To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1926249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039161] Re: When attaching multiattach volumes apparmor nova-compute profile blocks some operations
** Also affects: charm-nova-compute/zed Importance: Undecided Status: New ** Also affects: charm-nova-compute/2023.2 Importance: Undecided Status: New ** Also affects: charm-nova-compute/yoga Importance: Undecided Status: New ** Also affects: charm-nova-compute/2023.1 Importance: Undecided Status: New ** Changed in: charm-nova-compute/2023.1 Status: New => Fix Released ** Changed in: charm-nova-compute/2023.2 Status: New => Fix Released ** Changed in: charm-nova-compute/zed 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/2039161 Title: When attaching multiattach volumes apparmor nova-compute profile blocks some operations To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/2039161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054444] Re: Cluster Resize is failing in UI
Marking magnum-ui (upstream) as invalid since this is an issue found in the ubuntu focal archive. ** Changed in: magnum-ui Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/205 Title: Cluster Resize is failing in UI To manage notifications about this bug go to: https://bugs.launchpad.net/magnum-ui/+bug/205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054444] Re: Cluster Resize is failing in UI
** Also affects: magnum-ui (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/205 Title: Cluster Resize is failing in UI To manage notifications about this bug go to: https://bugs.launchpad.net/magnum-ui/+bug/205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Request New OpenStack SRU Exception for Magnum
On Fri, 2023-04-14 at 11:13 -0700, Steve Langasek wrote: > On Tue, Apr 11, 2023 at 04:32:54PM +0100, James Page wrote: > > On Tue, Mar 7, 2023 at 1:03 PM James Page wrote: > > > > [...] > > > Please could the proposed update to the OpenStack policy be reviewed in > > this context as we'd like to get the issues the point releases resolve > > fixed in Ubuntu. > > Yes, please update https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates to > include magnum. > > I will review the current SRUs in accordance with the exception. Thank you, appreciated. -- Felipe Reyes Software Engineer @ Canonical felipe.re...@canonical.com (GPG:0x9B1FFF39) Launchpad: ~freyes | IRC: freyes -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
Request New OpenStack SRU Exception for Magnum
Hello SRU team, I'd like to request the inclusion of Magnum in the OpenStack SRU Exception list at https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates. Magnum is an OpenStack API service making container orchestration engines (COE) such as Kubernetes available. Magnum is already included in our regression testing and is validated via Tempest smoke tests[0]. Best, [0] https://github.com/openstack-charmers/charmed-openstack-tester/pull/98 -- Felipe Reyes Software Engineer @ Canonical felipe.re...@canonical.com (GPG:0x9B1FFF39) Launchpad: ~freyes | IRC: freyes -- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
[Bug 1975634] Re: [SRU] Xena stable releases
neutron-19.3.0 from cloud-archive:xena-proposed fixed LP#1947127 in our environments. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975634 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1975634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972665] Re: [SRU] Xena stable releases
On Horizon I was able to launch an instance with a floating ip and navigate across the different panels with no problem. ubuntu@freyes-bastion:~$ juju ssh openstack-dashboard/0 apt policy openstack-dashboard openstack-dashboard: Installed: 4:20.1.2-0ubuntu1~cloud0 Candidate: 4:20.1.2-0ubuntu1~cloud0 Version table: *** 4:20.1.2-0ubuntu1~cloud0 500 500 http://ubuntu-cloud.archive.canonical.com/ubuntu focal-proposed/xena/main amd64 Packages 100 /var/lib/dpkg/status 3:18.3.5-0ubuntu2 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 3:18.3.2-0ubuntu0.20.04.4 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 3:18.2.1~git2020041013.754804667-0ubuntu3 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal/main amd64 Packages Connection to 10.5.2.169 closed. ** Tags removed: verification-xena-needed ** Tags added: verification-xena-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972665 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1972665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972665] Re: [SRU] Xena stable releases
I was able to run successfully charmed-openstack-tester (tox -e func- target -- focal-xena) for the Xena UCA, here it's the list of packages used by the testing bed. ubuntu@freyes-bastion:~$ juju ssh neutron-api/0 apt policy neutron-common neutron-common: Installed: 2:19.2.0-0ubuntu1~cloud0 Candidate: 2:19.2.0-0ubuntu1~cloud0 Version table: *** 2:19.2.0-0ubuntu1~cloud0 500 500 http://ubuntu-cloud.archive.canonical.com/ubuntu focal-proposed/xena/main amd64 Packages 100 /var/lib/dpkg/status 2:16.4.2-0ubuntu1 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 2:16.0.0~b3~git2020041516.5f42488a9a-0ubuntu2 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal/main amd64 Packages Connection to 10.5.2.110 closed. ubuntu@freyes-bastion:~$ juju ssh nova-compute/0 apt policy nova-common nova-common: Installed: 3:24.1.0-0ubuntu2~cloud0 Candidate: 3:24.1.0-0ubuntu2~cloud0 Version table: *** 3:24.1.0-0ubuntu2~cloud0 500 500 http://ubuntu-cloud.archive.canonical.com/ubuntu focal-proposed/xena/main amd64 Packages 100 /var/lib/dpkg/status 2:21.2.4-0ubuntu1 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 2:21.0.0~b3~git2020041013.57ff308d6d-0ubuntu2 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal/main amd64 Packages Connection to 10.5.2.218 closed. ubuntu@freyes-bastion:~$ juju ssh cinder/0 apt policy cinder-common cinder-common: Installed: 2:19.0.0-0ubuntu4~cloud0 Candidate: 2:19.0.0-0ubuntu4~cloud0 Version table: *** 2:19.0.0-0ubuntu4~cloud0 500 500 http://ubuntu-cloud.archive.canonical.com/ubuntu focal-proposed/xena/main amd64 Packages 100 /var/lib/dpkg/status 2:16.4.2-0ubuntu2 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 2:16.1.0-0ubuntu1 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 2:16.0.0~b3~git2020041012.eb915e2db-0ubuntu1 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal/main amd64 Packages Connection to 10.5.2.13 closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972665 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1972665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1972730] Re: WARNING: crmadmin -S unexpected output
On Wed, 2022-05-11 at 19:13 +, Lucas Kanashiro wrote: > Thanks for working with upstream to fix this. Would you be willing to > backport this fix to Jammy? Or do you prefer me to do it? I can propose the SRU (via debdiff) if you can sponsor it :-) > > For Kinetic we will be moving to the newer version (4.4.0 as upstream > suggested) so this will not be an issue. I am going to talk to the > Debian maintainer to see if we can get version 4.4.0 in unstable so we > can merge it. That's great, thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972730 Title: WARNING: crmadmin -S unexpected output To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1972730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972730] Re: WARNING: crmadmin -S unexpected output
ppa with the fix proposed at https://github.com/ClusterLabs/crmsh/pull/972 for testing purposes available at https://launchpad.net/~freyes/+archive/ubuntu/lp1972730 ** Changed in: charm-hacluster Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972730 Title: WARNING: crmadmin -S unexpected output To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1972730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972730] Re: WARNING: crmadmin -S unexpected output
The way this error is exposed in the hacluster is when running the
`stop` hook:
unit-hacluster-1: 16:53:41 DEBUG juju.worker.uniter.runner starting jujuc
server {unix @/var/lib/juju/agents/unit-hacluster-1/agent.socket }
unit-hacluster-1: 16:53:41 INFO unit.hacluster/1.juju-log Setting node
juju-0c8f53-zaza-723eab24403d-4 to maintenance
unit-hacluster-1: 16:53:43 WARNING unit.hacluster/1.stop Traceback (most recent
call last):
unit-hacluster-1: 16:53:43 WARNING unit.hacluster/1.stop File
"/var/lib/juju/agents/unit-hacluster-1/charm/hooks/stop", line 767, in
unit-hacluster-1: 16:53:43 WARNING unit.hacluster/1.stop
hooks.execute(sys.argv)
unit-hacluster-1: 16:53:43 WARNING unit.hacluster/1.stop File
"/var/lib/juju/agents/unit-hacluster-1/charm/charmhelpers/core/hookenv.py",
line 962, in execute
unit-hacluster-1: 16:53:43 WARNING unit.hacluster/1.stop
self._hooks[hook_name]()
unit-hacluster-1: 16:53:43 WARNING unit.hacluster/1.stop File
"/var/lib/juju/agents/unit-hacluster-1/charm/hooks/stop", line 617, in stop
unit-hacluster-1: 16:53:43 WARNING unit.hacluster/1.stop
pcmk.set_node_status_to_maintenance(node)
unit-hacluster-1: 16:53:43 WARNING unit.hacluster/1.stop File
"/var/lib/juju/agents/unit-hacluster-1/charm/hooks/pcmk.py", line 201, in
set_node_status_to_maintenance
unit-hacluster-1: 16:53:43 WARNING unit.hacluster/1.stop commit('crm -w -F
node maintenance {}'.format(node_name),
unit-hacluster-1: 16:53:43 WARNING unit.hacluster/1.stop File
"/var/lib/juju/agents/unit-hacluster-1/charm/hooks/pcmk.py", line 90, in commit
unit-hacluster-1: 16:53:43 WARNING unit.hacluster/1.stop return
subprocess.check_output(cmd.split(), stderr=subprocess.STDOUT)
unit-hacluster-1: 16:53:43 WARNING unit.hacluster/1.stop File
"/usr/lib/python3.10/subprocess.py", line 420, in check_output
unit-hacluster-1: 16:53:43 WARNING unit.hacluster/1.stop return
run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
unit-hacluster-1: 16:53:43 WARNING unit.hacluster/1.stop File
"/usr/lib/python3.10/subprocess.py", line 524, in run
unit-hacluster-1: 16:53:43 WARNING unit.hacluster/1.stop raise
CalledProcessError(retcode, process.args,
unit-hacluster-1: 16:53:43 WARNING unit.hacluster/1.stop
subprocess.CalledProcessError: Command '['crm', '-w', '-F', 'node',
'maintenance', 'juju-0c8f53-zaza-723eab24403d-4']' returned non-zero exit
status 1.
unit-hacluster-1: 16:53:43 ERROR juju.worker.uniter.operation hook "stop" (via
explicit, bespoke hook script) failed: exit status 1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972730
Title:
WARNING: crmadmin -S unexpected output
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1972730/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972730] [NEW] WARNING: crmadmin -S unexpected output
Public bug reported: Pacemaker changed the output string of "crmadmin -S " in 2.1.0 with the commit https://github.com/ClusterLabs/pacemaker/commit/c26c9951d863e83126f811ee5b91a174fe0cc991 , this is different from the ouput that wait4dc() expects https://github.com/ClusterLabs/crmsh/blob/master/crmsh/utils.py#L898 . Example output of `crm -w -F node maintenance ` of a cluster running on Ubuntu 22.04 ``` root@juju-0c8f53-zaza-723eab24403d-4:~# crm -w -F node maintenance juju-0c8f53-zaza-723eab24403d-4 WARNING: crmadmin -S juju-0c8f53-zaza-723eab24403d-5 unexpected output: Controller on juju-0c8f53-zaza-723eab24403d-5 in state S_IDLE: ok (exit code: 0) root@juju-0c8f53-zaza-723eab24403d-4:~# echo $? 1 root@juju-0c8f53-zaza-723eab24403d-4:~# crmadmin -S juju-0c8f53-zaza-723eab24403d-5 Controller on juju-0c8f53-zaza-723eab24403d-5 in state S_IDLE: ok root@juju-0c8f53-zaza-723eab24403d-4:~# dpkg -l pacemaker crmsh | cat 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 VersionArchitecture Description +++-==-==--=== ii crmsh 4.3.1-1ubuntu2 all CRM shell for the pacemaker cluster manager ii pacemaker 2.1.2-1ubuntu3 amd64cluster resource manager ``` Upstream bug filed: https://github.com/ClusterLabs/crmsh/issues/970 ** Affects: charm-hacluster Importance: Undecided Status: New ** Affects: crmsh (Ubuntu) Importance: Undecided Status: New ** Affects: crmsh (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: crmsh (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: charm-hacluster 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/1972730 Title: WARNING: crmadmin -S unexpected output To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1972730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972665] Re: [SRU] Xena stable releases
** Description changed: [Impact] This release comes with bug fixes that we would like to make available to our users. The following packages come in this set of point releases: * neutron 19.2.0 * nova 24.1.0 + * cinder 19.1.0 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] ** Description changed: [Impact] This release comes with bug fixes that we would like to make available to our users. The following packages come in this set of point releases: * neutron 19.2.0 * nova 24.1.0 * cinder 19.1.0 + * horizon 20.1.2 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972665 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1972665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972665] Re: [SRU] Xena stable releases
** Merge proposal linked: https://code.launchpad.net/~freyes/ubuntu/+source/neutron/+git/neutron/+merge/421764 ** Merge proposal linked: https://code.launchpad.net/~freyes/ubuntu/+source/neutron/+git/neutron/+merge/421763 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972665 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1972665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972665] [NEW] [SRU] Xena stable releases
Public bug reported: [Impact] This release comes with bug fixes that we would like to make available to our users. The following packages come in this set of point releases: * neutron 19.2.0 * nova 24.1.0 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] ** Affects: cloud-archive Importance: Undecided Status: Invalid ** Affects: cloud-archive/xena Importance: Undecided Status: New ** Affects: neutron (Ubuntu) Importance: Undecided Status: Invalid ** Affects: nova (Ubuntu) Importance: Undecided Status: Invalid ** Affects: neutron (Ubuntu Impish) Importance: Undecided Status: New ** Affects: nova (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: cloud-archive/xena Importance: Undecided Status: New ** Changed in: cloud-archive Status: New => Invalid ** Also affects: neutron (Ubuntu) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: neutron (Ubuntu) Status: New => Invalid ** Also affects: nova (Ubuntu) Importance: Undecided Status: New ** Changed in: nova (Ubuntu) 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/1972665 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1972665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972014] [NEW] template-initconfig is missing
Public bug reported: In 20.04 When I run setup-ds.pl, it always errors out thus: ``` Could not open the script template file '/etc/dirsrv/config/template-initconfig'. Error: No such file or directory ``` Going by this page: https://manpages.ubuntu.com/manpages/focal/man5/template- initconfig.5.html … it seems that this file is meant to be included in the package but just isn’t there: ``` > apt-file show 389-ds-base | grep etc 389-ds-base: /etc/default/389-ds-base 389-ds-base: /etc/dirsrv/config/certmap.conf 389-ds-base: /etc/dirsrv/config/ldap-agent.conf 389-ds-base: /etc/dirsrv/config/slapd-collations.conf 389-ds-base: /etc/dirsrv/schema/99user.ldif ``` Thank you for your time! ** Affects: 389-ds-base (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/1972014 Title: template-initconfig is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/1972014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971565] Re: charm no longer works with latest mysql-router version
** Changed in: charm-mysql-router Milestone: None => 22.04 ** Changed in: charm-mysql-router Assignee: (unassigned) => Felipe Reyes (freyes) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971565 Title: charm no longer works with latest mysql-router version To manage notifications about this bug go to: https://bugs.launchpad.net/charm-mysql-router/+bug/1971565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971565] Re: charm no longer works with latest mysql-router version
From a charm's perspective, I believe we should be setting [DEFAULT].unknown_config_option to "warning", so (possible) future changes in this area won't break a running cluster. From the docs https://dev.mysql.com/doc/mysql-router/8.0/en/mysql-router-conf-options.html#option_mysqlrouter_unknown_config_option : """ A warning is default behavior, and bootstrapping defines it as error in the generated configuration file. MySQL Router versions before 8.0.29 ignore unknown configuration options. A warning logs a warning message but does not halt, whereas an error means Router fails to initialize and exits. """ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971565 Title: charm no longer works with latest mysql-router version To manage notifications about this bug go to: https://bugs.launchpad.net/charm-mysql-router/+bug/1971565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971565] Re: charm no longer works with latest mysql-router version
worth to mention that the [DEFAULT].name key is set by "mysqlrouter --bootstrap" and not by the charm, more details at https://bugs.launchpad.net/charm-mysql-router/+bug/1907250/comments/10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971565 Title: charm no longer works with latest mysql-router version To manage notifications about this bug go to: https://bugs.launchpad.net/charm-mysql-router/+bug/1971565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907250] Re: [focal] charm becomes blocked with workload-status "Failed to connect to MySQL"
I'm seeing this error: 2022-05-03 22:04:39 io INFO [7f91c2e53e00] starting 8 io-threads, using backend 'linux_epoll' 2022-05-03 22:04:39 main ERROR [7f91c2e53e00] Error: option 'DEFAULT.name' is not supported The error can be reproduced using this bundle http://paste.ubuntu.com/p/mdY9dJhktH/ + the patch recently merged at https://review.opendev.org/c/openstack/charm-mysql-router/+/834359 (probably at this point in time the change should be available in the latest/edge channel). When I try to generate the bootstrap files that the mysqlrouter creates we can find that the `name` key is added by it and it's not added by the charm, see below: root@juju-b70e35-0-lxd-6:/var/lib/mysql/vault-mysql-router# /usr/bin/mysqlrouter --user mysql --name keystone-mysql-router --bootstrap mysqlrouteruser:3f4m6w6r2HFjGkfXnbHP3Mr6mphcpxys@10.246.114.60 --direc tory /var/lib/mysql/keystone-mysql-router --conf-use-sockets --conf-bind-address 127.0.0.1 --conf-base-port 3306 --disable-rest --force # Bootstrapping MySQL Router instance at '/var/lib/mysql/keystone-mysql-router'... - Creating account(s) (only those that are needed, if any) - Verifying account (using it to run SQL queries that would be run by Router) - Storing account in keyring - Adjusting permissions of generated files - Creating configuration /var/lib/mysql/keystone-mysql-router/mysqlrouter.conf # MySQL Router 'keystone-mysql-router' configured for the InnoDB Cluster 'jujuCluster' After this MySQL Router has been started with the generated configuration $ /usr/bin/mysqlrouter -c /var/lib/mysql/keystone-mysql- router/mysqlrouter.conf InnoDB Cluster 'jujuCluster' can be reached by connecting to: ## MySQL Classic protocol - Read/Write Connections: localhost:3306, /var/lib/mysql/keystone-mysql-router/mysql.sock - Read/Only Connections: localhost:3307, /var/lib/mysql/keystone-mysql-router/mysqlro.sock ## MySQL X protocol - Read/Write Connections: localhost:3308, /var/lib/mysql/keystone-mysql-router/mysqlx.sock - Read/Only Connections: localhost:3309, /var/lib/mysql/keystone-mysql-router/mysqlxro.sock root@juju-b70e35-0-lxd-6:/var/lib/mysql/vault-mysql-router# less /var/lib/mysql/keystone-mysql-router/mysqlrouter.conf root@juju-b70e35-0-lxd-6:/var/lib/mysql/vault-mysql-router# grep -B1 name /var/lib/mysql/keystone-mysql-router/mysqlrouter.conf [DEFAULT] name=keystone-mysql-router ** Also affects: mysql-8.0 (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/1907250 Title: [focal] charm becomes blocked with workload-status "Failed to connect to MySQL" To manage notifications about this bug go to: https://bugs.launchpad.net/charm-mysql-router/+bug/1907250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970670] [NEW] package nvidia-driver-510 510.60.02-0ubuntu0.20.04.2 failed to install/upgrade: problemas de dependencias - se deja sin configurar
Public bug reported: idk, when i started the computer this was the rror ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-driver-510 510.60.02-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 AptOrdering: linux-signatures-nvidia-5.13.0-30-generic:amd64: Remove linux-modules-extra-5.13.0-30-generic:amd64: Remove linux-image-5.13.0-30-generic:amd64: Remove linux-modules-5.13.0-30-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 19 09:39:51 2022 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2022-04-04 (23 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-510 Title: package nvidia-driver-510 510.60.02-0ubuntu0.20.04.2 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970670 Title: package nvidia-driver-510 510.60.02-0ubuntu0.20.04.2 failed to install/upgrade: problemas de dependencias - se deja sin configurar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1970670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947127] Re: Some DNS extensions not working with OVN
** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: neutron (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/1947127 Title: Some DNS extensions not working with OVN To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1947127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962582] Re: [SRU] Xena stable releases
hello all, I was able to validate successfully the packages available in the -proposed pocket, specifically the following versions were installed in the cloud deployed: ~/sources/ubuntu/lp1962582 $ grep ceilometer-common *.dpkg machine-23.dpkg:ii ceilometer-common2:17.0.1-0ubuntu1 all ceilometer common files machine-24.dpkg:ii ceilometer-common2:17.0.1-0ubuntu1 all ceilometer common files machine-25.dpkg:ii ceilometer-common2:17.0.1-0ubuntu1 all ceilometer common files machine-2.dpkg:ii ceilometer-common2:17.0.1-0ubuntu1 all ceilometer common files ~/sources/ubuntu/lp1962582 $ grep heat-common *.dpkg machine-15.dpkg:ii heat-common 1:17.0.1-0ubuntu1 all OpenStack orchestration service - common files ~/sources/ubuntu/lp1962582 $ grep openstack-dashboard-common *.dpkg machine-27.dpkg:ii openstack-dashboard-common 4:20.1.1-0ubuntu1 all Django web interface for OpenStack - common files These packages were validated running tempest, specifically using the charmed-openstack-tester[0] and running "tox -e func-target -- impish- xena". For the case of Horizon, I logged in and launched a cirros instance that booted correctly, and navigated through all the panels available on the left. [0] https://github.com/openstack-charmers/charmed-openstack-tester ** Tags removed: verification-needed verification-needed-impish ** Tags added: verification-done verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962582 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1962582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904580] Re: Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open
I have a patch in this branch https://git.launchpad.net/~freyes/ubuntu/+source/nova/commit/?id=88c97dc9332b97edf06618b6d4d2c770153821a6 , although I haven't been able to test it, I'm removing myself from the bug since I won't have cycles to dedicate to this task in the short term. ** Changed in: nova (Ubuntu) Assignee: Felipe Reyes (freyes) => (unassigned) ** Changed in: nova (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904580 Title: Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1904580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952447] Re: Server group creation fails on Xena
** Also affects: heat (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/1952447 Title: Server group creation fails on Xena To manage notifications about this bug go to: https://bugs.launchpad.net/charm-heat/+bug/1952447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904580] Re: Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open
** Changed in: charm-nova-compute Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904580 Title: Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1904580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904580] Re: Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open
** Changed in: nova (Ubuntu) Assignee: (unassigned) => Felipe Reyes (freyes) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904580 Title: Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1904580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904745] Re: File permissions in /var/lib/nova/.ssh broken in upgrade
*** This bug is a duplicate of bug 1904580 *** https://bugs.launchpad.net/bugs/1904580 hello everyone, thanks for reporting this bug, I'm going to mark this bug as duplicate of https://bugs.launchpad.net/charm-nova- compute/+bug/1904580 since it tracked the analysis and workarounds. ** This bug has been marked a duplicate of bug 1904580 Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904745 Title: File permissions in /var/lib/nova/.ssh broken in upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1904745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966512] Re: FTBS in jammy: FAIL: magnumclient.tests.test_shell.ShellTest.test_help_on_subcommand
** Patch added: "lp1966512_jammy.patch" https://bugs.launchpad.net/ubuntu/+source/python-magnumclient/+bug/1966512/+attachment/5573002/+files/lp1966512_jammy.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966512 Title: FTBS in jammy: FAIL: magnumclient.tests.test_shell.ShellTest.test_help_on_subcommand To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-magnumclient/+bug/1966512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966512] [NEW] FTBS in jammy: FAIL: magnumclient.tests.test_shell.ShellTest.test_help_on_subcommand
Public bug reported: This failure is due to a change in python 3.10 where the string "optional arguments" was changed to "options", more info at https://docs.python.org/3/whatsnew/3.10.html#argparse and https://bugs.python.org/issue9694 . Upstream bug: https://storyboard.openstack.org/#!/story/2009946 Upstream fix: https://review.opendev.org/c/openstack/python-magnumclient/+/835217 Test failures: == FAIL: magnumclient.tests.test_shell.ShellTest.test_help_on_subcommand magnumclient.tests.test_shell.ShellTest.test_help_on_subcommand -- testtools.testresult.real._StringException: Traceback (most recent call last): File "/<>/magnumclient/tests/test_shell.py", line 127, in test_help_on_subcommand self.assertThat((stdout + stderr), File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 480, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: 'usage: magnum bay-create [--name ] --baymodel \n [--node-count ]\n [--master-count ]\n [--discovery-url ]\n [--timeout ]\n\nCreate a bay. (Deprecated in favor of cluster-create.)\n\nOptions:\n --name Name of the bay to create.\n --baymodel \nID or name of the baymodel.\n --node-count \nThe bay node count.\n --master-count \nThe number of master nodes for the bay.\n --discovery-url \n Specifies custom discovery url for node discovery.\n --timeout The timeout for bay creation in minutes. The default\n is 60 minutes.\n' does not match /.*?^Optional arguments:/ == FAIL: magnumclient.tests.test_shell.ShellTestKeystoneV3.test_help_on_subcommand magnumclient.tests.test_shell.ShellTestKeystoneV3.test_help_on_subcommand -- testtools.testresult.real._StringException: Traceback (most recent call last): File "/<>/magnumclient/tests/test_shell.py", line 127, in test_help_on_subcommand self.assertThat((stdout + stderr), File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 480, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: 'usage: magnum bay-create [--name ] --baymodel \n [--node-count ]\n [--master-count ]\n [--discovery-url ]\n [--timeout ]\n\nCreate a bay. (Deprecated in favor of cluster-create.)\n\nOptions:\n --name Name of the bay to create.\n --baymodel \nID or name of the baymodel.\n --node-count \nThe bay node count.\n --master-count \nThe number of master nodes for the bay.\n --discovery-url \n Specifies custom discovery url for node discovery.\n --timeout The timeout for bay creation in minutes. The default\n is 60 minutes.\n' does not match /.*?^Optional arguments:/ ** Affects: python-magnumclient (Ubuntu) Importance: Undecided Assignee: Felipe Reyes (freyes) Status: New ** Changed in: python-magnumclient (Ubuntu) Assignee: (unassigned) => Felipe Reyes (freyes) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966512 Title: FTBS in jammy: FAIL: magnumclient.tests.test_shell.ShellTest.test_help_on_subcommand To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-magnumclient/+bug/1966512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966442] Re: AttributeError: module 'collections' has no attribute 'Iterable'
** Patch added: "lp1966442_jammy.debdiff" https://bugs.launchpad.net/ubuntu/+source/python-os-win/+bug/1966442/+attachment/5572999/+files/lp1966442_jammy.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966442 Title: AttributeError: module 'collections' has no attribute 'Iterable' To manage notifications about this bug go to: https://bugs.launchpad.net/os-win/+bug/1966442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966442] Re: AttributeError: module 'collections' has no attribute 'Iterable'
** Also affects: python-os-win (Ubuntu) Importance: Undecided Status: New ** Changed in: python-os-win (Ubuntu) Assignee: (unassigned) => Felipe Reyes (freyes) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966442 Title: AttributeError: module 'collections' has no attribute 'Iterable' To manage notifications about this bug go to: https://bugs.launchpad.net/os-win/+bug/1966442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962582] [NEW] [SRU] Xena stable releases
Public bug reported: [Impact] Users will get the latest stable bug fixes for this release of OpenStack. Point releases included in this SRU: ceilometer 17.0.1, heat 17.0.1 horizon 20.1.1 [Test Case] Testing of point releases for OpenStack packages is covered by: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates [Regression Potential] Very low as this SRU is releasing stable point releases that upstream has already released. ** Affects: cloud-archive Importance: Undecided Status: Invalid ** Affects: cloud-archive/xena Importance: Undecided Status: New ** Affects: ceilometer (Ubuntu) Importance: Undecided Status: Invalid ** Affects: heat (Ubuntu) Importance: Undecided Status: Invalid ** Affects: horizon (Ubuntu) Importance: Undecided Status: Invalid ** Affects: ceilometer (Ubuntu Impish) Importance: Undecided Status: New ** Affects: heat (Ubuntu Impish) Importance: Undecided Status: New ** Affects: horizon (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: cloud-archive/xena Importance: Undecided Status: New ** Changed in: cloud-archive Status: New => Invalid ** Also affects: ceilometer (Ubuntu) Importance: Undecided Status: New ** Also affects: ceilometer (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: ceilometer (Ubuntu) Status: New => Invalid ** Also affects: heat (Ubuntu) Importance: Undecided Status: New ** Also affects: horizon (Ubuntu) Importance: Undecided Status: New ** Changed in: heat (Ubuntu) Status: New => Invalid ** Changed in: horizon (Ubuntu) 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/1962582 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1962582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943765] Re: ipmitool "timing" flags are not working as expected causing failure to manage power of baremetal nodes
** Changed in: charm-ironic-conductor Milestone: None => 22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943765 Title: ipmitool "timing" flags are not working as expected causing failure to manage power of baremetal nodes To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ironic-conductor/+bug/1943765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959847] Re: Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet]
Hi Frode, I went through the captures I have and effectively, if we filter out the packets where the srcport != 53 or dstport != 6081 , we end up only with valid dns traffic. I believe this explains what we are seeing, and the other findings you did regards the missing flows, we can say with certainty that the DNS issues we are seeing are only a symptom of instances losing North-South traffic. I'm closing the bug as Invalid. $ for PCAP in *.pcap; do echo -e "$PCAP\t$(tshark -r $PCAP | grep -i "unknown" | wc -l)\t$(tshark -r $PCAP 'udp.dstport ne 6081' | grep -i unknown | wc -l)\t$(tshark -r $PCAP 'udp.srcport ne 53' | grep -i unknown | wc -l)";done dns-port-machine-0.pcap 90 0 0 dns-port-machine-10.pcap104 0 0 dns-port-machine-11.pcap26 0 0 dns-port-machine-12.pcap0 0 0 dns-port-machine-13.pcap0 0 0 dns-port-machine-2.pcap 6 0 0 dns-port-machine-3.pcap 72 0 0 dns-port-machine-4.pcap 0 0 0 dns-port-machine-5.pcap 59 0 0 dns-port-machine-6.pcap 68 0 0 dns-port-machine-7.pcap 46 0 0 dns-port-machine-8.pcap 104 0 0 dns-port-machine-9.pcap 32 0 0 ** Changed in: ovn (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959847 Title: Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1959847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959847] Re: Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet]
I have a capture using `tshark -i bond0 port 53` and I have a couple of streams that exhibit this issue, I would like to highlight this one in particular: $ tshark -x -r dns-port-machine-10.pcap "udp.stream eq 9" | pastebinit https://paste.ubuntu.com/p/yS74KCG2bY/ $ tshark -Tfields -e udp.port -e ip.host -r dns-port-machine-10.pcap "udp.stream eq 9" 53,6081 10.245.160.3,10.245.160.5 53,6081 10.245.160.3,10.245.160.5 53,6081 10.245.160.3,10.245.160.5 53,6081 10.245.160.3,10.245.160.5 53,6081 10.245.160.3,10.245.160.5 the pcap can be found at https://private- fileshare.canonical.com/~freyes/dns-port-20220210_154629.tar.bz2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959847 Title: Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1959847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959847] Re: Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet]
An older capture: [...] .?.V...#[... 8.0.27-0ubuntu0.20.04.1...%..D/D).1[.[g=WEU(.K_.caching_sha2_password..@eX...$..>M'...>.t...E.@.@.KG...f..t .?.V...#[... 8.0.27-0ubuntu0.20.04.1...%..D/D).1[.[g=WEU(.K_.caching_sha2_password..@eX...$..>M'...>.t...E.@.@.KG...f..t .?.V...#[... 8.0.27-0ubuntu0.20.04.1...%..D/D).1[.[g=WEU(.K_.caching_sha2_password..@eX...$..>M'...>.t...E..4..@.@.LV...G...f...z..u .?.W...$.@eX...$..>M'...>.t...E..4..@.@.LV...G...f...z..u [...] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959847 Title: Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1959847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959847] Re: Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet]
Something I saw in a new data capture was when I made wireshark to display the conversation of the stream that was showing "Unknown operation (12)" packets, it displayed this: [...] ..O...p<...a_.q.U. ...@..J.[... 8.0.28-0ubuntu0.20.04.3.1i..jA.;.F_b...8#NEqB`U~H6..caching_sha2_password..@eX..O...>Z.B..>FE.@.@.1. ... [...] The 2 suspicious strings here are: "8.0.28-0ubuntu0.20.04.3" and "caching_sha2_password", the former being the version of ubuntu's mysql8 package and the latter is plugin auth of mysql, I have no idea how/why that data would be present in the capture of "tcpdump -i any port 53". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959847 Title: Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1959847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925233] Re: [bionic-ussuri] designate-mdns.service: Failed with result 'start-limit-hit'
here is an example on how to reuse config.rendered flag https://github.com/openstack/charm-manila/blob/b75e6ed3ce6b2c061105ac8226a778e1ec3685d4/src/reactive/manila_handlers.py#L178 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925233 Title: [bionic-ussuri] designate-mdns.service: Failed with result 'start- limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/charm-designate/+bug/1925233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925233] Re: [bionic-ussuri] designate-mdns.service: Failed with result 'start-limit-hit'
We discussed this issue with the team and the agreement is that the charm should disable/mask the service until the configuration has been rendered, this is a pattern already used in other charms. For the reactive charms there is a handler for this - https://github.com/openstack/charm-layer- openstack/blob/master/reactive/layer_openstack.py#L161-L167 ** Changed in: charm-designate Status: Incomplete => Triaged ** Changed in: designate (Ubuntu) Status: New => Invalid ** Changed in: charm-designate Importance: Undecided => High ** Tags added: good-first-bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925233 Title: [bionic-ussuri] designate-mdns.service: Failed with result 'start- limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/charm-designate/+bug/1925233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959847] Re: Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet]
** Bug watch added: github.com/systemd/systemd/issues #12841 https://github.com/systemd/systemd/issues/12841 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959847 Title: Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1959847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1959847] Re: Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet]
On Tue, 2022-02-08 at 15:11 +, Frode Nordahl wrote: > Thank you for your bug report, I wonder if this proposed fix [0] could > be related? I don't believe so, IIUC this would affect how the replies are assembled and passed to the guest. I was looking at a similar issue (RR counters) on the systemd-resolved side[0] and systemd would be logging "invalid reply" while we see ETIMEDOUT. > > Does tshark provide any detail about what exactly it finds malformed > about the packets? yes, the opcode is 12, where a query's opcode is 0 , opcode 12 is unassigned according to the spec - https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-5 [0] https://github.com/systemd/systemd/issues/12841 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959847 Title: Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1959847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925233] Re: [bionic-ussuri] next charm fails to start mdns service
Checking designate/2. ~/Downloads/f1badd08-a9a6-405a-b0be-d7f49ece023c/designate_2 $ tail var/log/designate/designate-mdns.log -n 2 2021-04-19 16:04:24.389 64928 ERROR designate oslo_db.exception.CantStartEngineError: No sql_connection parameter is established 2021-04-19 16:04:24.389 64928 ERROR designate The last line logged by designate-mdns was at 16:04. While the configuration files were rendered at 16:05:12 $ grep -C 2 base-config.rendered var/log/juju/unit-designate-2.log | head -n 5 2021-04-19 16:05:12 DEBUG jujuc server.go:211 running hook tool "juju- log" for designate/2-identity-service-relation-changed- 330171960584494981 2021-04-19 16:05:12 DEBUG juju-log identity-service:105: tracer> tracer: set flag base-config.rendered tracer: ++ queue handler reactive/designate_handlers.py:144:run_db_migration tracer: ++ queue handler reactive/designate_handlers.py:155:sync_pool_manager_cache designate-mdns failed to start because the systemd service hit start- limit-hit Apr 19 16:04:24 juju-9669d8-4-lxd-3 systemd[1]: designate-mdns.service: Failed with result 'exit-code'. Apr 19 16:04:24 juju-9669d8-4-lxd-3 systemd[1]: designate-mdns.service: Service hold-off time over, scheduling restart. Apr 19 16:04:24 juju-9669d8-4-lxd-3 systemd[1]: designate-mdns.service: Scheduled restart job, restart counter is at 481. Apr 19 16:04:24 juju-9669d8-4-lxd-3 systemd[1]: designate-mdns.service: Failed to reset devices.list: Operation not permitted Apr 19 16:04:24 juju-9669d8-4-lxd-3 systemd[1]: designate-mdns.service: Start request repeated too quickly. Apr 19 16:04:24 juju-9669d8-4-lxd-3 systemd[1]: designate-mdns.service: Failed with result 'start-limit-hit'. I think this is something that should be fixed in the package, since we may need to do adjustments to designate-mdns.service https://www.freedesktop.org/software/systemd/man/systemd.unit.html#StartLimitIntervalSec=interval ** Also affects: designate (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [bionic-ussuri] next charm fails to start mdns service + [bionic-ussuri] designate-mdns.service Failed with result 'start-limit-hit' ** Summary changed: - [bionic-ussuri] designate-mdns.service Failed with result 'start-limit-hit' + [bionic-ussuri] designate-mdns.service: Failed with result 'start-limit-hit' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925233 Title: [bionic-ussuri] designate-mdns.service: Failed with result 'start- limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/charm-designate/+bug/1925233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959847] Re: Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet]
syslog from a VM where some dns queries failed with ETIMEDOUT, e.g. Feb 2 15:56:08 juju-6c8a68-zaza-1e093df25cbd-7 systemd-resolved[1352]: Transaction 55701 for on scope dns on ens3/* now complete with from none (unsigned). ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1959847/+attachment/5558790/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959847 Title: Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1959847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959847] [NEW] Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet]
Public bug reported: There have been DNS issues while running CI jobs for the openstack charms, when I captured the dns traffic in one of the nova-compute units[0][1], it can be seen how certain queries are malformed: ~ $ tshark -r dns-port-53.pcap | grep -i malformed | tail -n 2 15403 3602.706021 10.245.160.32 → 10.245.160.114 DNS 126 Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet] 15404 3602.706023 10.245.160.32 → 10.245.160.114 DNS 126 Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet] ~ $ tshark -r dns-port-53.pcap | grep -i malformed | wc -l 408 ~ $ tshark -r dns-port-53.pcap | wc -l 15728 Another symptom found is within the VM's systemd-resolved, it logs queries timing out https://pastebin.ubuntu.com/p/pJnd9sprpF/ [2] Packages installed: # dpkg -l ovn-common 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 VersionArchitecture Description +++-==-==--= ii ovn-common 20.03.2-0ubuntu0.20.04.2.0 amd64OVN common components # apt policy ovn-common ovn-common: Installed: 20.03.2-0ubuntu0.20.04.2.0 Candidate: 21.12.0-0ubuntu1.0~20.04.0 Version table: 21.12.0-0ubuntu1.0~20.04.0 500 500 http://ppa.launchpad.net/fnordahl/serverstack/ubuntu focal/main amd64 Packages *** 20.03.2-0ubuntu0.20.04.2.0 500 500 http://ppa.launchpad.net/fnordahl/lp1857026/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 20.03.2-0ubuntu0.20.04.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 20.03.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages [0] tcpdump -i any -ln port 53 [1] https://private-fileshare.canonical.com/~freyes/dns-port-53.pcap [2] note: this is a different run from the tcpdump capture, so they could be different root causes ** Affects: ovn (Ubuntu) Importance: Undecided Status: New ** Description changed: There have been DNS issues while running CI jobs for the openstack charms, when I captured the dns traffic in one of the nova-compute units[0][1], it can be seen how certain queries are malformed: - ~ $ tshark -r dns-port-53.pcap | grep -i malformed | tail -n 2 + ~ $ tshark -r dns-port-53.pcap | grep -i malformed | tail -n 2 15403 3602.706021 10.245.160.32 → 10.245.160.114 DNS 126 Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet] 15404 3602.706023 10.245.160.32 → 10.245.160.114 DNS 126 Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet] - ~ $ tshark -r dns-port-53.pcap | grep -i malformed | wc -l + ~ $ tshark -r dns-port-53.pcap | grep -i malformed | wc -l 408 - ~ $ tshark -r dns-port-53.pcap | wc -l + ~ $ tshark -r dns-port-53.pcap | wc -l 15728 Another symptom found is within the VM's systemd-resolved, it logs queries timing out https://pastebin.ubuntu.com/p/pJnd9sprpF/ [2] + + Packages installed: + + # dpkg -l ovn-common + 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 VersionArchitecture Description + +++-==-==--= + ii ovn-common 20.03.2-0ubuntu0.20.04.2.0 amd64OVN common components + + # apt policy ovn-common + ovn-common: + Installed: 20.03.2-0ubuntu0.20.04.2.0 + Candidate: 21.12.0-0ubuntu1.0~20.04.0 + Version table: + 21.12.0-0ubuntu1.0~20.04.0 500 + 500 http://ppa.launchpad.net/fnordahl/serverstack/ubuntu focal/main amd64 Packages + *** 20.03.2-0ubuntu0.20.04.2.0 500 + 500 http://ppa.launchpad.net/fnordahl/lp1857026/ubuntu focal/main amd64 Packages + 100 /var/lib/dpkg/status + 20.03.2-0ubuntu0.20.04.2 500 + 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages + 20.03.0-0ubuntu1 500 + 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages + [0] tcpdump -i any -ln port 53 [1] https://private-fileshare.canonical.com/~freyes/dns-port-53.pcap [2] note: this is a different run from the tcpdump capture, so they could be different root causes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959847 Title: Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1959847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951841] Re: [SRU] ovn metadata agent randomly timing out
The fix for this bug will be available in neutron-19.1.0 which at the moment is available in the -proposed pockets for Impish and Xena, more details on the progress of the point release can be found at https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1956991 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951841 Title: [SRU] ovn metadata agent randomly timing out To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1951841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951841] Re: [SRU] ovn metadata agent randomly timing out
Marking jammy as fix committed since package neutron_19.0.0+git2022010514.7aba1bddab-0ubuntu1[0] contains the fix that was merged in upstream[1] [0] https://launchpad.net/ubuntu/+source/neutron/2:19.0.0+git2022010514.7aba1bddab-0ubuntu1 [1] https://opendev.org/openstack/neutron/commit/79037c951637dc06d47b6d354776d116a1d2a9ad ** Changed in: neutron (Ubuntu) Status: New => Fix Committed ** Changed in: cloud-archive Status: New => Fix Committed ** Changed in: cloud-archive/xena Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951841 Title: [SRU] ovn metadata agent randomly timing out To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-chassis/+bug/1951841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951841] Re: [SRU] ovn metadata agent randomly timing out
** Patch added: "lp1951841_impish.debdiff" https://bugs.launchpad.net/charm-ovn-chassis/+bug/1951841/+attachment/5552146/+files/lp1951841_impish.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951841 Title: [SRU] ovn metadata agent randomly timing out To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-chassis/+bug/1951841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951841] Re: [SRU] ovn metadata agent randomly timing out
** Description changed:
+ [Impact]
+
+ When the ovn-controller daemon elects a new leader is expected that
+ clients reconnect to that new instance, for the case of Xena the
+ reconnect attempt will also call register_metadata_agent()[0] and this
+ method enforces that OVS system-id is formatted as UUID which is not
+ true for Charmed OpenStack deployed with OVN, this produces that the
+ neutron-ovn-metadata-agent daemon stays running but disconnected and new
+ launched VMs won't have access to the metadata service.
+
+ [0]
+
https://github.com/openstack/neutron/blob/stable/xena/neutron/agent/ovn/metadata/agent.py#L157
+
+
+ [Test Plan]
+
+ 1. Deploy an OpenStack cloud using OVN
+
+ ```
+ git clone https://git.launchpad.net/stsstack-bundles
+ cd stsstack-bundles/openstack
+ ```
+
+ Focal Xena:
+ ./generate-bundle.sh --series focal --release xena --ovn --name focal-xena
--run
+
+ Impish:
+ ./generate-bundle.sh --series impish --ovn --name focal-xena --run
+
+ 2. Configure the cloud creating networks, subnets, etc.
+
+ ```
+ source ~/novarc
+ ./configure
+ ```
+
+ 3. Launch an instance
+
+ ```
+ source ./novarc
+ ./tools/instance_launch 1 focal
+ ```
+
+ 4. Check the net namespace was correctly provisioned
+
+ ```
+ juju ssh nova-compute/0 sudo ip netns
+ ```
+
+ Example output:
+
+ $ juju ssh nova-compute/0 sudo ip netns | grep ovnmeta
+ ovnmeta-0211506b-233e-4773-a034-3950dfefe23d (id: 0)
+
+ 5. Delete the instance: `openstack server delete focal-150930`
+
+ 6. Check the netns was removed.
+
+ $ juju ssh nova-compute/0 sudo ip netns | grep ovnmeta
+ Connection to 10.5.2.148 closed.
+
+ 7. Restart ovn controller leader unit to force a new leader.
+
+ juju ssh $(juju status ovn-central | grep leader | tail -n 1 | awk
+ '{print $1}' | tr -d '*') sudo reboot
+
+ 8. Wait a few minutes and then launch a new instance
+ ```
+ source ./novarc
+ ./tools/instance_launch 1 focal
+ ```
+
+ 9. Wait a few minutes (~5m) and check cloud-init's output and the
+ ovnmeta netns
+
+ ```
+ openstack console log show
+ juju ssh nova-compute/0 sudo ip netns | grep ovnmeta
+ ```
+
+ Expected result:
+ * The launched instance is able to read its configuration from the metadata
service and not timing out.
+ * The ovnmeta- namespace gets created.
+
+ Actual result:
+
+ * The instance launched can't be accessed via ssh, because cloud-init timed
out trying to access the metadata service.
+ * The ovnmeta- namespace is missing from the nova-compute unit.
+
+
+ [Where problems could occur]
+
+ * This patch changes the way the UUID used to identify the neutron-ovn-
+ metadata-agent service is generated, hence issues would manifest as the
+ daemon not starting (check `systemctl status neutron-ovn-metadata-
+ agent`) or starting but not being able to connect and provision the
+ datapath needed when launching new instances in the faulty compute unit
+ and those instances would have cloud-init timing out.
+
+ [Other Info]
+
+
+ [Original Description]
+
When creating VMs, they will randomly not get access to metadata
service.
Openstack focal/Xena, with stock OVN 21.09.0-0ubuntu1~cloud0.
For testing, I created 32 instances (at once), and 19 have access to
metadata service and the other 13 do not. The proportion will vary
depending on the iteration and tend to be about 50%.
Because of that, I cannot enter those machines via SSH (I can see in the
console logs they are not able to get anything from the agent). If I
create all of them using "ConfigDrive" option then all of them get SSH
keys. When entering them and trying to 'curl' the metadata ip address, I
get the correct response on some and timeout on others.
I don't see any correlation between the failures and specific compute
hosts.
I don't see any suspecting messages in {nova,ovn,neutron,openvswitch}
logs for the hypervisor that have a problematic vm or for the dedicated
gateway.
Note: this cloud has 2 extra nodes running ovn-dedicated-chassis and
those two are the only nodes that have a way out to provider-networks.
Network tests, except for the metadata problem, seem to be ok, including
routers and security groups.
This has been very consistent between batches of vm deploys and even
across redeploys of the cloud.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951841
Title:
[SRU] ovn metadata agent randomly timing out
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ovn-chassis/+bug/1951841/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951841] Re: ovn metadata agent randomly timing out
** Changed in: neutron (Ubuntu Impish) Assignee: (unassigned) => Felipe Reyes (freyes) ** Changed in: neutron (Ubuntu Impish) Status: New => Triaged ** Summary changed: - ovn metadata agent randomly timing out + [SRU] ovn metadata agent randomly timing out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951841 Title: [SRU] ovn metadata agent randomly timing out To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-chassis/+bug/1951841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951841] Re: ovn metadata agent randomly timing out
- Marking charm-ovn-chassis as invalid since the issue is in neutron itself and not the charm or how it drives the workload. - Adding tasks for Ubuntu/Impish and cloud-archive/xena. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951841 Title: ovn metadata agent randomly timing out To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-chassis/+bug/1951841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951841] Re: ovn metadata agent randomly timing out
This change[0] was merged in stable/xena, this relaxes the check that ovs system-id must be a uuid formatted string, now when it can't parse it as a uuid it will (re)generate a uuid using uuid.uuid5(), which will use as input a hardcoded UUID (as namespace) and the chassis name string. [0] https://opendev.org/openstack/neutron/commit/6da4432fed255f3bcf3831f5d0520ab389ce36e5 ** Also affects: neutron (Ubuntu) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/xena Importance: Undecided Status: New ** Changed in: charm-ovn-chassis 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/1951841 Title: ovn metadata agent randomly timing out To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-chassis/+bug/1951841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941988] Re: Designate DNS – Secondary zone is failed to be created and gets into the ERROR status
** Also affects: charm-designate 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/1941988 Title: Designate DNS – Secondary zone is failed to be created and gets into the ERROR status To manage notifications about this bug go to: https://bugs.launchpad.net/charm-designate/+bug/1941988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952495] [NEW] Trying to reinstall my Ubuntu in NVME SSD drive over some cloned files that came from an HDD installation
Public bug reported: The summary says it all. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.17 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 26 22:30:37 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: LANGUAGE=pt_BR.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.17 ubuntu ** Summary changed: - Trying to reinstall my Ubuntu in NVME SSD drive over some colned files that came from an HDD installation + Trying to reinstall my Ubuntu in NVME SSD drive over some cloned files that came from an HDD installation -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952495 Title: Trying to reinstall my Ubuntu in NVME SSD drive over some cloned files that came from an HDD installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1952495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949120] [NEW] Missing PPMTUD for ICMP and UDP when there are dedicated gateways
Public bug reported: According to this bug[0] and these patches[1][2][3] the support to emit a ICMP "need to fragment" packet was added in ovn-21.09, Wallaby UCA carries ovn-20.12 This limitation becomes a problem when the overlay network is configured to use jumbo frames and the external network uses a MTU of 1500 . [Environment] Focal Wallaby with a dedicated ovn-chassis application to act as gateway ovn-chassis-gw: bindings: ? '' : oam-space data: overlay-space charm: cs:ovn-dedicated-chassis options: source: cloud:focal-wallaby/proposed bridge-interface-mappings: br-data:bond0.3811 ovn-bridge-mappings: physnet1:br-data prefer-chassis-as-gw: true num_units: 2 to: - 1001 - 1002 [0] https://bugzilla.redhat.com/show_bug.cgi?id=1547074#c5 [1] https://github.com/ovn-org/ovn/commit/2c2f1802dcfc6f7d3e3a25a24e0b8f4c7c7f39d8 [2] https://github.com/ovn-org/ovn/commit/1c9e46ab5c05043a8cd6c47b5fec2e1ac4c962db [3] https://github.com/ovn-org/ovn/commit/947e8d450ebaa8ce4ab81cb480a419618f1508c7 ** 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/1949120 Title: Missing PPMTUD for ICMP and UDP when there are dedicated gateways To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1949120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944424] Re: AppArmor causing HA routers to be in backup state on wallaby-focal
** Changed in: charm-neutron-gateway Milestone: None => 21.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944424 Title: AppArmor causing HA routers to be in backup state on wallaby-focal To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-gateway/+bug/1944424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943765] Re: ipmitool "timing" flags are not working as expected causing failure to manage power of baremetal nodes
** Also affects: ironic (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943765 Title: ipmitool "timing" flags are not working as expected causing failure to manage power of baremetal nodes To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ironic-conductor/+bug/1943765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938477] Re: Screen brightness changing randomly with kernel 5.11.0-25
Since the -16 version of the kernel was not available anymore, the bug was back for me. I then downloaded and installed 5.11.1-051101-generic with mainline and the bug is NOT happening with this kernel version. Hope this info helps. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938477 Title: Screen brightness changing randomly with kernel 5.11.0-25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790979] Re: Unable to change disk decryption passphrase
*** This bug is a duplicate of bug 1837437 *** https://bugs.launchpad.net/bugs/1837437 I just got this error and there is no way to recover my data? It's lost? Such a critical bug and no solution?! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790979 Title: Unable to change disk decryption passphrase To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1790979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938477] Re: Screen brightness changing randomly
The above command didn't make any difference. My computer doesn't even have a light sensor. I have tried this before but I just tried again to make sure. I will have to keep holding the kernel version for now. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938477 Title: Screen brightness changing randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1938477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938477] Re: Screen brightness changing randomly
Hey thanks. If it's feature why it doesn't happen on this particular kernel version? Also my power settings does not show this option. I already tried changing it with dconf-editor. I still think it's a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938477 Title: Screen brightness changing randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1938477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938477] [NEW] Screen brightness changing randomly
Public bug reported: Hello guys! The brightness of the screen on my laptop (Dell 7573 with touch ips 1080 panel) slightly changes randomly when using the laptop builtin display. It feels the same as I changed the brightness one step using the keyboard keys. Here is a video: https://drive.google.com/file/d/1XQLXKLWu2TlOoGP-p8eaUGZR78713ErH/view?usp=sharing I suffer with this problem since a long time ago. I think since ubuntu 19. I tried everything you can imagine, I will make a list of things I've tried. I had gave up trying to fix this already but in a beautiful sunny day suddenly the bug stopped happening. So I decided to report this bug now because this bug does NOT happen with only this version of the kernel: Linux 5.11.0-16-generic. So that can probably e useful to help discovering the bug reason. I am choosing this version on grub every time I reboot so the bug doesn't happen. If I boot on 5.11.0-25 the bug is back. List of things I've tried: - Changing i915 parameters like enable_psr to false and many others. - Upgrading BIOS version. - Installing windows and applying all the patches on dell's website and installing ubuntu again. - Disabling "dynamic backlight control" on BIOS. Some maybe useful info: - I've tried other distros like Fedora and PopOS and the same bug happens. - The bug does not happen when using live ubuntu from usb. - When you fresh install ubuntu (I've tried with 20.04, 20.10 and 21.04) the bug doesn't happen when you have just installed the os but it starts again after the first update. The same applies to the other distro's mentioned above. - When you disable i915 driver with modeset parameter, it does not happen. - The bug does NOT happen only with this kernel version 5.11.0-16-generic, BUT it starts happening again if I lock screen and login again. So I am never locking my screen and holding this kernel version for now. Thanks guys! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 29 20:54:14 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-16-generic, x86_64: installed virtualbox, 6.1.18, 5.11.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07ec] InstallationDate: Installed on 2021-07-25 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Inspiron 7573 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=663d1a67-7acb-428f-a6c8-a9a259a5427c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2021 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.1 dmi.board.name: 023FRC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.1:bd05/06/2021:br1.18:svnDellInc.:pnInspiron7573:pvr:rvnDellInc.:rn023FRC:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7573 dmi.product.sku: 07EC dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938477 Title: Screen brightness changing randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1938477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
