[Bug 2067815] [NEW] dbmanage sync fails to run
Public bug reported: The SQLAlchemy scripts for Caracal watcher fails to run due to errors in the generated SQL migrations. This occurs when the `watcher db-manage sync` scripts are run to create the database or migrate the database. Patches have been merged recently upstream -https://review.opendev.org/c/openstack/watcher/+/918500 Example stack trace below: 2024-06-01 16:58:29.918774 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 INFO [alembic.runtime.migration] Context impl SQLiteImpl. 2024-06-01 16:58:29.918801 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 INFO [alembic.runtime.migration] Will assume non-transactional DDL. 2024-06-01 16:58:29.918830 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 INFO [alembic.runtime.migration] Running upgrade -> 001, ocata release 2024-06-01 16:58:29.918852 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 INFO [alembic.runtime.migration] Running upgrade 001 -> 0f6042416884, Add apscheduler_jobs table to store background jobs 2024-06-01 16:58:29.919273 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 INFO [alembic.runtime.migration] Running upgrade 0f6042416884 -> d098df6021e2, Add cron support for audit table 2024-06-01 16:58:29.919326 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 CRITI [python-watcher] Unhandled error 2024-06-01 16:58:29.919361 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 Traceback (most recent call last): 2024-06-01 16:58:29.919390 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1910, in _execute_context 2024-06-01 16:58:29.919416 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 self.dialect.do_execute( 2024-06-01 16:58:29.919837 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 736, in do_execute 2024-06-01 16:58:29.919866 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 cursor.execute(statement, parameters) 2024-06-01 16:58:29.919881 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 sqlite3.OperationalError: near "ALTER": syntax error 2024-06-01 16:58:29.919905 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 2024-06-01 16:58:29.919922 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 The above exception was the direct cause of the following exception: 2024-06-01 16:58:29.919936 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 2024-06-01 16:58:29.921865 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 Traceback (most recent call last): 2024-06-01 16:58:29.921930 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 File "/usr/bin/watcher-db-manage", line 10, in 2024-06-01 16:58:29.921963 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 sys.exit(main()) 2024-06-01 16:58:29.921984 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed logger.go:60 File "/usr/lib/python3/dist-packages/watcher/cmd/dbmanage.py", line 157, in main 2024-06-01 16:58:29.921998 | focal-medium | 2024-06-01 16:58:29 [ERROR] unit-watcher-0.log: 2024-06-01 16:58:17 WARNING unit.watcher/0.shared-db-relation-changed
Re: [gscan2pdf-help] Ubuntu 22.04.3 LTS and libtiff-tools {solved}
sound like a packaging error. Forwarding to Ubuntu packagers identified at
https://packages.ubuntu.com/noble/gscan2pdf
-- Forwarded message -
From: John Kerr
Date: Tue, Jan 16, 2024 at 11:52 AM
Subject: [gscan2pdf-help] Ubuntu 22.04.3 LTS and libtiff-tools {solved}
To:
Hello
This is a report on how I got gscan2pdf to work. I am using Ubuntu 22.04.3
LTS
When I installed gscan2pdf from Synaptic I got this message:
failed to fetch
http://security.ubuntu.com/ubuntu/pool/universe/t/tiff/libtiff-tools_4.3.0-6ubuntu0.3_amd64.deb
The program did not work.
I went to: http://security.ubuntu.com/ubuntu/pool/universe/t/tiff/
I noticed this file: libtiff-tools_4.3.0-6ubuntu0.7_amd64.deb
{libtiff-tools_4.3.0-6ubuntu0.3_amd64.deb was not listed}
In Synaptic I noticed that libtiff-dev has
libtiff-tools_4.3.0-6ubuntu0.7_amd64.deb in it
I tried *sudo apt-get install libtiff-dev*
Now gscan2 pdf works as it should.
Thank you for everything you do for us. I love gscan2pdf.
Best regards,
John
--
"Every time I see an adult on a bicycle I no longer despair for the human
race." -- H.G. Wells
___
gscan2pdf-help mailing list
gscan2pdf-h...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gscan2pdf-help
--
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
[ubuntu-studio-users] (no subject)
... BC was here -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
[Bug 1874719] Re: [SRU] Use the hostname as the node name instead of hardcoded 'node1'
** Changed in: charm-hacluster 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/1874719 Title: [SRU] Use the hostname as the node name instead of hardcoded 'node1' To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1874719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964802] Re: [SRU] ceph 15.2.16
The bionic port comes through the Ubuntu Cloud Archive, for which there is a task already raised. Once it is built and included in the focal sru queue, the package will then be eligible to be included into the proposed pocket for the bionic-ussuri Cloud Archive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964802 Title: [SRU] ceph 15.2.16 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1964802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888309] Re: [MIR] octavia
** Changed in: octavia (Ubuntu) Milestone: ubuntu-20.10 => ubuntu-22.04-feature-freeze ** Changed in: octavia (Ubuntu) Milestone: ubuntu-22.04-feature-freeze => ubuntu-22.04-beta -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888309 Title: [MIR] octavia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1888309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930446] Re: Wallaby ceilometer.compute.discovery fails to get domain metadata
** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/wallaby Importance: Undecided Status: New ** Also affects: cloud-archive/xena Importance: Undecided Status: New ** Changed in: cloud-archive/wallaby Status: New => Triaged ** Changed in: cloud-archive/xena Status: New => Triaged ** Changed in: cloud-archive 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/1930446 Title: Wallaby ceilometer.compute.discovery fails to get domain metadata To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1930446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955015] [NEW] package mysql-common 5.8+1.0.5ubuntu2 failed to install/upgrade: installed mysql-common package post-removal script subprocess returned error exit status 2
Public bug reported: its preventing me from installing the server ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-common 5.8+1.0.5ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: mysql-common:amd64: Purge NULL: ConfigurePending NULL: PurgePending NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 16 12:37:45 2021 Dependencies: DpkgTerminalLog: Purging configuration files for mysql-common (8.0.27-1ubuntu20.04) ... update-alternatives: error: no alternatives for my.cnf dpkg: error processing package mysql-common (--purge): installed mysql-common package post-removal script subprocess returned error exit status 2 DuplicateSignature: package:mysql-common:5.8+1.0.5ubuntu2 Purging configuration files for mysql-common (8.0.27-1ubuntu20.04) ... update-alternatives: error: no alternatives for my.cnf dpkg: error processing package mysql-common (--purge): installed mysql-common package post-removal script subprocess returned error exit status 2 ErrorMessage: installed mysql-common package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2021-10-20 (56 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all 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: mysql-defaults Title: package mysql-common 5.8+1.0.5ubuntu2 failed to install/upgrade: installed mysql-common package post-removal script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955015 Title: package mysql-common 5.8+1.0.5ubuntu2 failed to install/upgrade: installed mysql-common package post-removal script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-defaults/+bug/1955015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904730] Re: neutron-agent-sriov fails to create port
** Tags removed: verification-needed-victoria -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904730 Title: neutron-agent-sriov fails to create port To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1904730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950350] Re: octavia LBs always offline in Xena
Can you please provide various "show" outputs for the loadbalancers, members, listeners, etc? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950350 Title: octavia LBs always offline in Xena To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1950350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949108] Re: turning on debug results in exception when deleting stacks
It looks like this is fixed in upstream heat with this commit https://opendev.org/openstack/heat/commit/a78ddafdece30d259d59c0bba04714e36a8d6c25 ** Changed in: heat (Ubuntu) Status: New => Triaged ** Changed in: heat (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949108 Title: turning on debug results in exception when deleting stacks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heat/+bug/1949108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904730] Re: neutron-agent-sriov fails to create port
Verified for focal-victoria using the test script in comment #33
ubuntu@node-lepaute:~$ dpkg -l | grep pyroute2
ii python3-pyroute2 0.5.14-0ubuntu1~cloud0
all Python3 Netlink library
ubuntu@node-lepaute:~$ echo 63 | sudo tee
/sys/class/net/enp3s0f0/device/sriov_numvfs
63
ubuntu@node-lepaute:~$ ./test-lp1904730.sh
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line
1345, in _ft_decode_generic
self.decode_nlas(offset)
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line
1469, in decode_nlas
(length, base_msg_type) = struct.unpack_from('HH', self.data,
struct.error: unpack_from requires a buffer of at least 19212 bytes for
unpacking 4 bytes at offset 19208 (actual buffer size is 16384)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./test-lp1904730.sh", line 7, in
link = ip.link('get', index=link_idx, ext_mask=1)[0]
File "/usr/lib/python3/dist-packages/pyroute2/iproute/linux.py", line 1358,
in link
ret = self.nlm_request(msg,
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 376,
in nlm_request
return tuple(self._genlm_request(*argv, **kwarg))
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 867,
in nlm_request
for msg in self.get(msg_seq=msg_seq,
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 379,
in get
return tuple(self._genlm_get(*argv, **kwarg))
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 704,
in get
raise msg['header']['error']
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 177,
in parse
msg.decode()
File
"/usr/lib/python3/dist-packages/pyroute2/netlink/rtnl/ifinfmsg/__init__.py",
line 1092, in decode
nlmsg.decode(self)
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line
1016, in decode
self._ft_decode(self, offset)
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line
1348, in _ft_decode_generic
raise NetlinkNLADecodeError(e)
pyroute2.netlink.exceptions.NetlinkNLADecodeError: unpack_from requires a
buffer of at least 19212 bytes for unpacking 4 bytes at offset 19208 (actual
buffer size is 16384)
ubuntu@node-lepaute:~$ sudo add-apt-repository cloud-archive:victoria-proposed
Ubuntu Cloud Archive for OpenStack Victoria [proposed]
More info: https://wiki.ubuntu.com/OpenStack/CloudArchive
Press [ENTER] to continue or Ctrl-c to cancel adding it.
...
ubuntu@node-lepaute:~$ sudo apt-get upgrade python3-pyroute2
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
alsa-ucm-conf apport cloud-init distro-info-data libnetplan0 netplan.io
open-vm-tools python3-apport python3-cryptography python3-importlib-metadata
python3-openssl python3-problem-report python3-pyroute2
python3-requests squashfs-tools
15 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
5 standard security updates
Need to get 2287 kB of archives.
After this operation, 977 kB of additional disk space will be used.
...
ubuntu@node-lepaute:~$ dpkg -l | grep pyroute2
ii python3-pyroute2 0.5.14-0ubuntu1~cloud1
all Python3 Netlink library
ubuntu@node-lepaute:~$ ./test-lp1904730.sh
63
ubuntu@node-lepaute:~$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904730
Title:
neutron-agent-sriov fails to create port
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1904730/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904730] Re: neutron-agent-sriov fails to create port
Verified for bionic-ussuri using the test script in comment #33
ubuntu@node-lepaute:~$ dpkg -l | grep pyroute2
ii python3-pyroute2 0.5.9-0ubuntu1~cloud0
all Python3 Netlink library
ubuntu@node-lepaute:~$ echo 63 | sudo tee
/sys/class/net/enp3s0f0/device/sriov_numvfs
63
ubuntu@node-lepaute:~$ ./test-lp1904730.sh
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line
1311, in _ft_decode_generic
self.decode_nlas(offset)
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line
1436, in decode_nlas
offset)
struct.error: unpack_from requires a buffer of at least 4 bytes
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./test-lp1904730.sh", line 7, in
link = ip.link('get', index=link_idx, ext_mask=1)[0]
File "/usr/lib/python3/dist-packages/pyroute2/iproute/linux.py", line 1332,
in link
msg_flags=msg_flags)
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 373,
in nlm_request
return tuple(self._genlm_request(*argv, **kwarg))
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 864,
in nlm_request
callback=callback):
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 376,
in get
return tuple(self._genlm_get(*argv, **kwarg))
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 701,
in get
raise msg['header']['error']
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 177,
in parse
msg.decode()
File
"/usr/lib/python3/dist-packages/pyroute2/netlink/rtnl/ifinfmsg/__init__.py",
line 1087, in decode
nlmsg.decode(self)
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line 982,
in decode
self._ft_decode(self, offset)
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line
1314, in _ft_decode_generic
raise NetlinkNLADecodeError(e)
pyroute2.netlink.exceptions.NetlinkNLADecodeError: unpack_from requires a
buffer of at least 4 bytes
ubuntu@node-lepaute:~$ sudo add-apt-repository cloud-archive:ussuri-proposed
Ubuntu Cloud Archive for OpenStack Ussuri [proposed]
More info: https://wiki.ubuntu.com/OpenStack/CloudArchive
Press [ENTER] to continue or Ctrl-c to cancel adding it.
...
ubuntu@node-lepaute:~$ sudo apt-get upgrade python3-pyroute2
...
ubuntu@node-lepaute:~$ dpkg -l | grep pyroute2
ii python3-pyroute2 0.5.9-0ubuntu2~cloud0
all Python3 Netlink library
ubuntu@node-lepaute:~$ ./test-lp1904730.sh
63
** Tags added: verification-done-bionic-ussuri
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904730
Title:
neutron-agent-sriov fails to create port
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1904730/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904730] Re: neutron-agent-sriov fails to create port
Verified for focal-wallaby using test script in comment #33.
ubuntu@node-lepaute:~$ dpkg -l | grep pyroute2
ii python3-pyroute2 0.5.14-0ubuntu1~cloud0
all Python3 Netlink library
ubuntu@node-lepaute:~$ echo 63 | sudo tee
/sys/class/net/enp3s0f0/device/sriov_numvfs
63
ubuntu@node-lepaute:~$ ./test-lp1904730.sh
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line
1345, in _ft_decode_generic
self.decode_nlas(offset)
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line
1469, in decode_nlas
(length, base_msg_type) = struct.unpack_from('HH', self.data,
struct.error: unpack_from requires a buffer of at least 19212 bytes for
unpacking 4 bytes at offset 19208 (actual buffer size is 16384)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./test-lp1904730.sh", line 7, in
link = ip.link('get', index=link_idx, ext_mask=1)[0]
File "/usr/lib/python3/dist-packages/pyroute2/iproute/linux.py", line 1358,
in link
ret = self.nlm_request(msg,
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 376,
in nlm_request
return tuple(self._genlm_request(*argv, **kwarg))
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 867,
in nlm_request
for msg in self.get(msg_seq=msg_seq,
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 379,
in get
return tuple(self._genlm_get(*argv, **kwarg))
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 704,
in get
raise msg['header']['error']
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 177,
in parse
msg.decode()
File
"/usr/lib/python3/dist-packages/pyroute2/netlink/rtnl/ifinfmsg/__init__.py",
line 1092, in decode
nlmsg.decode(self)
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line
1016, in decode
self._ft_decode(self, offset)
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line
1348, in _ft_decode_generic
raise NetlinkNLADecodeError(e)
pyroute2.netlink.exceptions.NetlinkNLADecodeError: unpack_from requires a
buffer of at least 19212 bytes for unpacking 4 bytes at offset 19208 (actual
buffer size is 16384)
ubuntu@node-lepaute:~$ sudo add-apt-repository cloud-archive:wallaby-proposed
Ubuntu Cloud Archive for OpenStack Wallaby [proposed]
More info: https://wiki.ubuntu.com/OpenStack/CloudArchive
Press [ENTER] to continue or Ctrl-c to cancel adding it.
Reading package lists...
Building dependency tree...
Reading state information...
ubuntu-cloud-keyring is already the newest version (2020.02.11.4).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Get:1 http://ubuntu-cloud.archive.canonical.com/ubuntu focal-proposed/wallaby
InRelease [8771 B]
Hit:2 http://ubuntu-cloud.archive.canonical.com/ubuntu focal-updates/wallaby
InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal InRelease
Get:4 http://ubuntu-cloud.archive.canonical.com/ubuntu
focal-proposed/wallaby/main amd64 Packages [155 kB]
Get:5 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:6 http://archive.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Get:7 http://archive.ubuntu.com/ubuntu focal-backports InRelease [101 kB]
Fetched 492 kB in 1s (522 kB/s)
Reading package lists... Done
ubuntu@node-lepaute:~$ sudo apt-get upgrade python3-pyroute2
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
python3-pyroute2
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 269 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ubuntu-cloud.archive.canonical.com/ubuntu
focal-proposed/wallaby/main amd64 python3-pyroute2 all 0.5.14-0ubuntu1.1~cloud0
[269 kB]
Fetched 269 kB in 0s (9234 kB/s)
(Reading database ... 71815 files and directories currently installed.)
Preparing to unpack .../python3-pyroute2_0.5.14-0ubuntu1.1~cloud0_all.deb ...
Unpacking python3-pyroute2 (0.5.14-0ubuntu1.1~cloud0) over
(0.5.14-0ubuntu1~cloud0) ...
Setting up python3-pyroute2 (0.5.14-0ubuntu1.1~cloud0) ...
ubuntu@node-lepaute:~$
ubuntu@node-lepaute:~$ dpkg -l | grep pyroute2
ii python3-pyroute2 0.5.14-0ubuntu1.1~cloud0
all Python3 Netlink library
ubuntu@node-lepaute:~$ ./test-lp1904730.sh
63
ubuntu@node-lepaute:~$
** Tags added: verification-done-focal-wallaby
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904730
Title:
neutron-agent-sriov fails to create port
To manage notifications about this bug go to:
[Bug 1904730] Re: neutron-agent-sriov fails to create port
For bionic, the provided test case needs some tweaks as the neutron
version on bionic does not have the provided functions. Instead, I've
written a quick test script that will exercise the pyroute2 code path to
exercise the errors. Still requires enabling vfs as James did.
Simple script is:
#!/usr/bin/python3
import pyroute2
ip = pyroute2.IPRoute()
devname = 'enp3s0f0'
link_idx = ip.link_lookup(ifname=devname)[0]
link = ip.link('get', index=link_idx, ext_mask=1)[0]
num_vfs = link.get_attr('IFLA_NUM_VF')
print(num_vfs)
Running test on bionic without this fix to prove its enough to show the error:
$ dpkg -l | grep python3-pyroute2
ii python3-pyroute2 0.4.21-0.1ubuntu2
all Python3 Netlink library
$ sudo ./lp1904730-test.py
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line
1232, in _ft_decode_generic
self.decode_nlas(offset)
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line
1357, in decode_nlas
offset)
struct.error: unpack_from requires a buffer of at least 4 bytes
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./lp1904730-test.py", line 7, in
link = ip.link('get', index=link_idx, ext_mask=1)[0]
File "/usr/lib/python3/dist-packages/pyroute2/iproute.py", line 1310, in link
msg_flags=msg_flags)
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 804,
in nlm_request
return do_try()
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 783,
in do_try
callback=callback)
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 648,
in get
raise msg['header']['error']
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 171,
in parse
msg.decode()
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line 941,
in decode
self._ft_decode(self, offset)
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line
1235, in _ft_decode_generic
raise NetlinkNLADecodeError(e)
pyroute2.netlink.exceptions.NetlinkNLADecodeError: unpack_from requires a
buffer of at least 4 bytes
Running with the proposed patch:
$ dpkg -l | grep python3-pyroute2
ii python3-pyroute2 0.4.21-0.1ubuntu2.1
all Python3 Netlink library
$ sudo ./lp1904730-test.py
63
** Tags removed: verification-needed
** Tags added: verification-done verification-done-bionic
** Tags removed: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904730
Title:
neutron-agent-sriov fails to create port
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1904730/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892361] Re: SRIOV instance gets type-PF interface, libvirt kvm fails
Queens and Rocky are both extended maintenance and have had the proposed patches merged. Updating tasks to mark as fix released. ** Changed in: nova/rocky Status: New => Fix Released ** Changed in: nova/queens 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/1892361 Title: SRIOV instance gets type-PF interface, libvirt kvm fails To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1892361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885169] Re: Some arping version only accept integer number as -w argument
With the package now in -proposed, dropping field-critical and moving to field-high as workaround is available. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885169 Title: Some arping version only accept integer number as -w argument To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1885169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865037] Re: make the service fail gracefully if unable to load modules
Verified this package for focal. First, create focal container Second, apt-get install python3-rtslib-fb Fails with: dpkg: error processing package python3-rtslib-fb (--configure): installed python3-rtslib-fb package post-installation script subprocess returned error exit status 1 dmesg: read kernel buffer failed: Operation not permitted Errors were encountered while processing: python3-rtslib-fb E: Sub-process /usr/bin/dpkg returned an error code (1) Next, install proposed pocket, apt-get update. sudo apt-get install python3-rtslib-fb completes successfully: ... Unpacking python3-rtslib-fb (2.1.71-0ubuntu1.1) ... Setting up python3-rtslib-fb (2.1.71-0ubuntu1.1) ... Processing triggers for systemd (245.4-4ubuntu3.6) ... ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865037 Title: make the service fail gracefully if unable to load modules To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1865037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792880] Re: totalGigabytesUsed in openstack limits show indicate wrong info
Per upstream bug comment: This issue is caused by lack of microversion support for Volume service by python-openstack client. It also is unable to negotiate API microversions with server. As a result, python-openstackclient will always use cinder v3.0 API and will not be able to properly poll the server. Workaround: cinder --os-volume-api-version 3.40 absolute-limits PROJECT-ID -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792880 Title: totalGigabytesUsed in openstack limits show indicate wrong info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-openstackclient/+bug/1792880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865037] Re: make the service fail gracefully if unable to load modules
Hi Utkarsh - it is indeed more clear. Thanks for the links. I'm deleting the previous patch and providing a new one with updated versioning. ** Patch removed: "Debdiff for focal" https://bugs.launchpad.net/ubuntu/+source/python-rtslib-fb/+bug/1865037/+attachment/5506777/+files/lp1865037-focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865037 Title: make the service fail gracefully if unable to load modules To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1865037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865037] Re: make the service fail gracefully if unable to load modules
** Patch added: "focal patch" https://bugs.launchpad.net/ubuntu/+source/python-rtslib-fb/+bug/1865037/+attachment/5507137/+files/lp1865037-focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865037 Title: make the service fail gracefully if unable to load modules To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1865037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865037] Re: make the service fail gracefully if unable to load modules
ah thanks for the tip there Christian (that the version number is wrong). Is this because of where the change lies or ? Wanting to make sure I understand for future patches. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865037 Title: make the service fail gracefully if unable to load modules To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1865037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865037] Re: make the service fail gracefully if unable to load modules
Thanks Utkarsh! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865037 Title: make the service fail gracefully if unable to load modules To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1865037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865037] Re: make the service fail gracefully if unable to load modules
** Patch added: "Debdiff for focal" https://bugs.launchpad.net/cloud-archive/+bug/1865037/+attachment/5506777/+files/lp1865037-focal.debdiff ** Changed in: cloud-archive/ussuri 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/1865037 Title: make the service fail gracefully if unable to load modules To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1865037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865037] Re: make the service fail gracefully if unable to load modules
This bug is also a problem on focal. When trying to install in a
container, the service fails to start with:
invoke-rc.d: initscript rtslib-fb-targetctl, action "start" failed.
● rtslib-fb-targetctl.service - Restore LIO kernel target configuration
Loaded: loaded (/lib/systemd/system/rtslib-fb-targetctl.service; disabled;
vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2021-06-24 18:08:27 UTC; 13ms
ago
Process: 1232 ExecStart=/usr/bin/mkdir -p /etc/rtslib-fb-target
(code=exited, status=0/SUCCESS)
Process: 1233 ExecStart=/usr/bin/targetctl restore (code=exited,
status=1/FAILURE)
Main PID: 1233 (code=exited, status=1/FAILURE)
Jun 24 18:08:27 closing-anemone target[1233]: File "/usr/bin/targetctl", line
47, in restore
Jun 24 18:08:27 closing-anemone target[1233]: errors =
RTSRoot().restore_from_file(restore_file=from_file)
Jun 24 18:08:27 closing-anemone target[1233]: File
"/usr/lib/python3/dist-packages/rtslib_fb/root.py", line 85, in __init__
Jun 24 18:08:27 closing-anemone target[1233]: modprobe('target_core_mod')
Jun 24 18:08:27 closing-anemone target[1233]: File
"/usr/lib/python3/dist-packages/rtslib_fb/utils.py", line 428, in modprobe
Jun 24 18:08:27 closing-anemone target[1233]: raise RTSLibError(stderrdata)
Jun 24 18:08:27 closing-anemone target[1233]: rtslib_fb.utils.RTSLibError:
b'modprobe: FATAL: Module target_core_mod not found in directory
/lib/modules/5.8.0-55-generic\n'
Jun 24 18:08:27 closing-anemone systemd[1]: rtslib-fb-targetctl.service: Main
process exited, code=exited, status=1/FAILURE
Jun 24 18:08:27 closing-anemone systemd[1]: rtslib-fb-targetctl.service: Failed
with result 'exit-code'.
Jun 24 18:08:27 closing-anemone systemd[1]: Failed to start Restore LIO kernel
target configuration.
dpkg: error processing package python3-rtslib-fb (--configure):
installed python3-rtslib-fb package post-installation script subprocess
returned error exit status 1
Processing triggers for systemd (2dmesg: read kernel buffer failed: Operation
not permitted
I can confirm that the ConditionVirtualization=!container directive
added to the service file addresses the issue.
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/ussuri
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New => Triaged
** Changed in: cloud-archive
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865037
Title:
make the service fail gracefully if unable to load modules
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1865037/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916715] Re: fails on install due to systemd-service/sysv-service mismatch and lack of mkdir
** Changed in: python-rtslib-fb (Ubuntu Focal) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916715 Title: fails on install due to systemd-service/sysv-service mismatch and lack of mkdir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-rtslib-fb/+bug/1916715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930455] Re: Upgrade from bionic-train to bionic-ussuri fails for cinder due to sys-kernel-config.mount not existing in unprivileged container
*** This bug is a duplicate of bug 1865037 *** https://bugs.launchpad.net/bugs/1865037 Updated to be a duplicate of the correct bug - bug #1865037 ** This bug is no longer a duplicate of bug 1916715 fails on install due to systemd-service/sysv-service mismatch and lack of mkdir ** This bug has been marked a duplicate of bug 1865037 make the service fail gracefully if unable to load modules -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930455 Title: Upgrade from bionic-train to bionic-ussuri fails for cinder due to sys-kernel-config.mount not existing in unprivileged container To manage notifications about this bug go to: https://bugs.launchpad.net/charm-cinder/+bug/1930455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865037] Re: make the service fail gracefully if unable to load modules
** Also affects: python-rtslib-fb (Ubuntu Focal) 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/1865037 Title: make the service fail gracefully if unable to load modules To manage notifications about this bug go to: https://bugs.launchpad.net/rtslib-fb/+bug/1865037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916715] Re: fails on install due to systemd-service/sysv-service mismatch and lack of mkdir
Hi Christian, Thanks for the feedback, I see the error I made here. I confused this bug with bug #1865037, which actually adds the ConditionVirtualization=!container directive to the service file but was wrapped in the changelog. That's the change that needs to be made for focal so I'll do some bug tidying here. The recreate is simple - launch a new focal container and try to install python3-rtslib-fb inside it, but I'll move this over to the proper bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916715 Title: fails on install due to systemd-service/sysv-service mismatch and lack of mkdir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-rtslib-fb/+bug/1916715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930455] Re: Upgrade from bionic-train to bionic-ussuri fails for cinder due to sys-kernel-config.mount not existing in unprivileged container
*** This bug is a duplicate of bug 1916715 *** https://bugs.launchpad.net/bugs/1916715 I'm marking this as a duplicate of bug #1916715 per previous comment. ** Also affects: python-rtslib-fb (Ubuntu) Importance: Undecided Status: New ** Changed in: charm-cinder Status: New => Invalid ** This bug has been marked a duplicate of bug 1916715 fails on install due to systemd-service/sysv-service mismatch and lack of mkdir -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930455 Title: Upgrade from bionic-train to bionic-ussuri fails for cinder due to sys-kernel-config.mount not existing in unprivileged container To manage notifications about this bug go to: https://bugs.launchpad.net/charm-cinder/+bug/1930455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916715] Re: fails on install due to systemd-service/sysv-service mismatch and lack of mkdir
This also affects Focal installs and it affects openstack upgrades where the cinder services are running in a container (see bug #1930455), and I think we should backport this patch to Focal as well. I'm going to nominate the series as such. ** Also affects: python-rtslib-fb (Ubuntu Focal) 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/1916715 Title: fails on install due to systemd-service/sysv-service mismatch and lack of mkdir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-rtslib-fb/+bug/1916715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923668] Re: Upgrade from Queens to Rocky results in dead ovs-vswitchd services
This is a problem with openvswitch packages so adding Ubuntu/openvswitch and cloud-archive for some bug tracking. Corresponding Ubuntu release is well out of support and so is cloud-archive, but users could run into this on upgrade from Queens->Rocky ** Also affects: openvswitch (Ubuntu) Importance: Undecided Status: New ** Also affects: openvswitch (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: openvswitch (Ubuntu Focal) Status: New => Fix Released ** Changed in: openvswitch (Ubuntu) Status: New => Fix Released ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/rocky Importance: Undecided Status: New ** Changed in: cloud-archive Status: New => Triaged ** Changed in: cloud-archive/rocky Status: New => Triaged ** Changed in: charm-neutron-openvswitch Status: New => Invalid ** Changed in: cloud-archive/rocky Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923668 Title: Upgrade from Queens to Rocky results in dead ovs-vswitchd services To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1923668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
FWIW, I don't believe that the commit referenced in comment #9 is related to the problem, unless there's a race condition introduced by the added delay. Looking at that commit, the code will try harder to make sure that the device in the namespace exists before proceeding on as it did before. The log shows the error messages because the referenced change introduced a log message for the condition that the device doesn't exist in the namespace. The code in that code path continues as it did previously even when the error is logged. As a result, that change primarily waits up to 3 seconds longer for the device to exist and will then log the error for awareness, but still continues in the same code path. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925322] Re: [SRU] ceph 16.2.1
** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/xena Importance: Undecided Status: New ** Also affects: cloud-archive/wallaby 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/1925322 Title: [SRU] ceph 16.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1925322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925347] Re: ceph-osd fails to start with ProtectClock=true
** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/xena Importance: Undecided Status: New ** Also affects: cloud-archive/wallaby 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/1925347 Title: ceph-osd fails to start with ProtectClock=true To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1925347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902731] Re: iSCSI Gateway does not survive node reboot
This looks to be a ceph-iscsi bug and will need the relevant commit into Ceph for this, which is linked in the description. It's not, however, a charm bug at this point so I'll remove the charm. ** No longer affects: charm-ceph-iscsi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902731 Title: iSCSI Gateway does not survive node reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1902731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782517] Re: Failed to recover stopped instance
** Also affects: cloud-archive/ussuri Importance: Undecided Status: New ** Also affects: cloud-archive/stein Importance: Undecided Status: New ** Also affects: cloud-archive/victoria Importance: Undecided Status: New ** Also affects: cloud-archive/train Importance: Undecided Status: New ** Also affects: cloud-archive/wallaby 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/1782517 Title: Failed to recover stopped instance To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1782517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782517] Re: Failed to recover stopped instance
** Changed in: masakari (Ubuntu Hirsute) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782517 Title: Failed to recover stopped instance To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1782517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782517] Re: Failed to recover stopped instance
** Also affects: masakari (Ubuntu) Importance: Undecided Status: New ** Also affects: masakari (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: masakari (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: masakari (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: cloud-archive 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/1782517 Title: Failed to recover stopped instance To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1782517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900775] Re: Cinder fails to create image-based volume if mirroring is enabled
Xenial is nearing ESM and this isn't critical enough to backport at this time. ** Changed in: cinder (Ubuntu Xenial) Status: Triaged => 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/1900775 Title: Cinder fails to create image-based volume if mirroring is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-rbd-mirror/+bug/1900775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900775] Re: Cinder fails to create image-based volume if mirroring is enabled
trusty-mitaka is EOL ** Changed in: cloud-archive/mitaka Status: Triaged => 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/1900775 Title: Cinder fails to create image-based volume if mirroring is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-rbd-mirror/+bug/1900775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906727] Re: focal iscsiadm and blockdev location is wrongly mention in apparmor profi; le
** Tags removed: field high -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906727 Title: focal iscsiadm and blockdev location is wrongly mention in apparmor profi;le To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1906727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888395] Re: live migration of a vm using the single port binding work flow is broken in train as a result of the introduction of sriov live migration
** Description changed:
- it was working in queens but fails in train. nova compute at the target
- aborts with the exception:
+ [Impact]
+
+ Live migration of instances in an environment that uses neutron backends
+ that do not support multiple port bindings will fail with error
+ 'NotImplemented', effectively rendering live-migration inoperable in
+ these environments.
+
+ This is fixed by first checking to ensure the backend supports the
+ multiple port bindings before providing the port bindings.
+
+ [Test Plan]
+
+ 1. deploy a Train/Ussuri OpenStack cloud w/ at least 2 compute nodes
+ using an SDN that does not support multiple port bindings (e.g.
+ opencontrail).
+
+ 2. Attempt to perform a live migration of an instance.
+
+ 3. Observe that the live migration will fail without this fix due to the
+ trace below (NotImplementedError: Cannot load 'vif_type' in the base
+ class), and should succeed with this fix.
+
+
+ [Where problems could occur]
+
+ This affects the live migration code, so likely problems would arise in
+ this area. Specifically, the check introduced is guarding information
+ provided for instances using SR-IOV indirect migration.
+
+ Regressions would likely occur in the form of live migration errors
+ around features that rely on the multiple port bindings (e.g. the SR-
+ IOV) and not the more generic/common use case. Errors may be seen in
+ standard network providers that are included with distro packaging, but
+ may also be seen in scenarios where proprietary SDNs are used.
+
+
+ [Original Description]
+ it was working in queens but fails in train. nova compute at the target
aborts with the exception:
Traceback (most recent call last):
- File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line
165, in _process_incoming
- res = self.dispatcher.dispatch(message)
- File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py",
line 274, in dispatch
- return self._do_dispatch(endpoint, method, ctxt, args)
- File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py",
line 194, in _do_dispatch
- result = func(ctxt, **new_args)
- File "/usr/lib/python2.7/site-packages/nova/exception_wrapper.py", line 79,
in wrapped
- function_name, call_dict, binary, tb)
- File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220,
in __exit__
- self.force_reraise()
- File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196,
in force_reraise
- six.reraise(self.type_, self.value, self.tb)
- File "/usr/lib/python2.7/site-packages/nova/exception_wrapper.py", line 69,
in wrapped
- return f(self, context, *args, **kw)
- File "/usr/lib/python2.7/site-packages/nova/compute/utils.py", line 1372,
in decorated_function
- return function(self, context, *args, **kwargs)
- File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 219,
in decorated_function
- kwargs['instance'], e, sys.exc_info())
- File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220,
in __exit__self.force_reraise()
- File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196,
in force_reraise
- six.reraise(self.type_, self.value, self.tb) File
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 207, in
decorated_function
- return function(self, context, *args, **kwargs)
- File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 7007,
in pre_live_migration
- bdm.save()
- File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220,
in __exit__
- self.force_reraise()
- File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196,
in force_reraise
- six.reraise(self.type_, self.value, self.tb)
- File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6972,
in pre_live_migration
- migrate_data)
- File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line
9190, in pre_live_migration
- instance, network_info, migrate_data)
- File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line
9071, in _pre_live_migration_plug_vifs
- vif_plug_nw_info.append(migrate_vif.get_dest_vif())
- File "/usr/lib/python2.7/site-packages/nova/objects/migrate_data.py", line
90, in get_dest_vif
- vif['type'] = self.vif_type
- File "/usr/lib/python2.7/site-packages/oslo_versionedobjects/base.py", line
67, in getter
- self.obj_load_attr(name)
- File "/usr/lib/python2.7/site-packages/oslo_versionedobjects/base.py", line
603, in obj_load_attr
- _("Cannot load '%s' in the base class") % attrname)
+ File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line
165, in _process_incoming
+ res = self.dispatcher.dispatch(message)
+ File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py",
line 274, in dispatch
+ return self._do_dispatch(endpoint, method, ctxt, args)
+
[Bug 1888395] Re: live migration of a vm using the single port binding work flow is broken in train as a result of the introduction of sriov live migration
Corey - they are, and I've been working on them here and there to get them into shape. The Train version might slightly differ in the functional tests that are being added, but the actual code change is the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888395 Title: live migration of a vm using the single port binding work flow is broken in train as a result of the introduction of sriov live migration To manage notifications about this bug go to: https://bugs.launchpad.net/networking-opencontrail/+bug/1888395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818260] Re: forget cluster node failed during cluster-relation-changed hook
** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818260 Title: forget cluster node failed during cluster-relation-changed hook To manage notifications about this bug go to: https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1818260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903745] Re: pacemaker left stopped after unattended-upgrade of pacemaker (1.1.14-2ubuntu1.8 -> 1.1.14-2ubuntu1.9)
Charm fix was released in the 21.01 release with this patch https://review.opendev.org/c/openstack/charm-hacluster/+/763077 ** Changed in: charm-hacluster Milestone: None => 21.01 ** Changed in: charm-hacluster 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/1903745 Title: pacemaker left stopped after unattended-upgrade of pacemaker (1.1.14-2ubuntu1.8 -> 1.1.14-2ubuntu1.9) To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1903745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912647] [NEW] The touchpad of the ASUS Vivobook F407U does not work at all.
Public bug reported: The touchpad of my laptop is not working and when performing a xinput list, it is not even detected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-40-generic 5.8.0-40.45~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 18:53:19 2021 InstallationDate: Installed on 2021-01-21 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912647 Title: The touchpad of the ASUS Vivobook F407U does not work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1912647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823295] Re: openvswitch-switch package upgrades restart daemons multiple times
Dropping field-high designation as this is pending another SRU. No point in releasing this until a functional change against the openvswitch package for bionic is needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823295 Title: openvswitch-switch package upgrades restart daemons multiple times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1823295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840348] Re: Sharded OpWQ drops suicide_grace after waiting for work
** Changed in: cloud-archive/rocky Status: Invalid => 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/1840348 Title: Sharded OpWQ drops suicide_grace after waiting for work To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1840348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840348] Re: Sharded OpWQ drops suicide_grace after waiting for work
** Also affects: cloud-archive/train Importance: Undecided Status: New ** Also affects: cloud-archive/rocky Importance: Undecided Status: New ** Also affects: cloud-archive/queens Importance: Undecided Status: New ** Also affects: cloud-archive/stein 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/1840348 Title: Sharded OpWQ drops suicide_grace after waiting for work To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1840348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906725] Re: [SRU] ceph 15.2.7
** Description changed: [Impact] - This release fixes a serious bug in RGW that can cause data loss and also fixes CVE 2020-25660. We would like to make sure all of our supported customers have access to these improvements. + This release fixes a serious bug in RGW that can cause data loss and also fixes CVE 2020-25660. We would like to make sure all of our users have access to these improvements. The update contains the following package updates: -* ceph 15.2.7 + * ceph 15.2.7 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStackUpdates - 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 + In order to avoid regression of existing users, 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906725 Title: [SRU] ceph 15.2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1906725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903745] Re: pacemaker left stopped after unattended-upgrade of pacemaker (1.1.14-2ubuntu1.8 -> 1.1.14-2ubuntu1.9)
Based on discussion with Trent, who has access to more logs and data than I currently do for this, all signs are indeed pointing to the override timeouts provided by the charm itself. A viable work-around to prevent this is to tweak the service_stop_timeout config on the hacluster charm to be higher than the 60 second default. Setting it to 1800 would restore this to package's default. I am also going to invalidate the pacemaker task as it wasn't caused by the change to pacemaker and a more targeted bug to tweak the behavior of whether the service starts/stops should be raised instead. An investigation on possible alternatives for dealing with the upgrades and maintenance mode of the cluster should be pursued outside the bounds of this particular bug. As a work-around is available, I'll reduce subscribe field-high/remove field-critical while working on a patch to change the service timeout defaults. ** Changed in: pacemaker (Ubuntu) Status: Confirmed => Invalid ** Changed in: charm-hacluster Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903745 Title: pacemaker left stopped after unattended-upgrade of pacemaker (1.1.14-2ubuntu1.8 -> 1.1.14-2ubuntu1.9) To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1903745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903745] Re: pacemaker left stopped after unattended-upgrade of pacemaker (1.1.14-2ubuntu1.8 -> 1.1.14-2ubuntu1.9)
I should note that one of the reasons I do not suspect the charm is at fault here is that in the bionic sosreport linked in the bug, I do not see the delay that I would expect in a timeout scenario. If the stop timeout were coming into play, I would expect to see a long duration on the restart. However, we can see the package was upgraded at 06:17:34 : ... Start-Date: 2020-11-10 06:17:34 Commandline: /usr/bin/unattended-upgrade Upgrade: pacemaker:amd64 (1.1.18-0ubuntu1.1, 1.1.18-0ubuntu1.3) End-Date: 2020-11-10 06:17:36 ... Pacemaker service is restarted at 06:17:34 with a SIGTERM: Nov 10 06:17:34 [51765] juju-caae6f-19-lxd-6 pacemakerd: notice: crm_signal_dispatch: Caught 'Terminated' signal | 15 (invoking handler) and is restarted at 06:17:35 Nov 10 06:17:36 [41195] juju-caae6f-19-lxd-6 pacemakerd: info: crm_log_init:Changed active directory to /var/lib/pacemaker/cores Nov 10 06:17:36 [41195] juju-caae6f-19-lxd-6 pacemakerd: info: get_cluster_type:Detected an active 'corosync' cluster Nov 10 06:17:36 [41195] juju-caae6f-19-lxd-6 pacemakerd:error: sysrq_init: Cannot write to /proc/sys/kernel/sysrq: Permission denied (13) This doesn't look like its hindered by the timeout configuration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903745 Title: pacemaker left stopped after unattended-upgrade of pacemaker (1.1.14-2ubuntu1.8 -> 1.1.14-2ubuntu1.9) To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1903745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903745] Re: pacemaker left stopped after unattended-upgrade of pacemaker (1.1.14-2ubuntu1.8 -> 1.1.14-2ubuntu1.9)
I'm not sure why the pacemaker task was marked as invalid. The issues that Trent identified in comment #15 are a problem, but I'm not entirely convinced that its *the* problem that was encountered here (as also evidenced by Pedro in comment #16). While packages do typically restart services automatically, not all package upgrades will trigger this particular behavior. For example, the ceph packages will upgrade the services but not actually restart services as that could be very disruptive to the storage provided. I agree with Ante in comment #9 that the packages aren't doing all of the necessary steps to properly manage the upgrade. While, I'm not necessarily convinced this is something that should be handled by unattended-upgrades I'm also not convinced that it will be easy to add this logic to the packages. For example pacemaker depends on corosync, but so does dlm-controld and it is not reasonable for the corosync package to make assumptions on how to treat software built on top of it. Rather, I think it should be considered to change the behavior of the corosync/pacemaker packages to not automatically restart the services, or to provide an option in which the operator can control this behavior. ** Changed in: pacemaker (Ubuntu) Status: Invalid => Confirmed ** Changed in: charm-hacluster Assignee: (unassigned) => Billy Olsen (billy-olsen) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903745 Title: pacemaker left stopped after unattended-upgrade of pacemaker (1.1.14-2ubuntu1.8 -> 1.1.14-2ubuntu1.9) To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1903745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792978] Re: initscript avahi-daemon, action "start" failed
Avahi is not covered by field sla, so unsubscribing field-high -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792978 Title: initscript avahi-daemon, action "start" failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1792978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] Re: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5
Hi Jeff, here is outputs from my maas server, root@lab-virtual-machine:~# root@lab-virtual-machine:~# ls -l /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/daily/ total 460488 -rw-r--r-- 3 maas maas 86260608 十 6 11:23 boot-initrd -rw-r--r-- 3 maas maas 11678464 十 6 11:23 boot-kernel -rw-r--r-- 4 maas maas 373587968 十 6 11:22 squashfs root@lab-virtual-machine:~# root@lab-virtual-machine:~# sha256sum /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/daily/* 273212b1858bc4441b392900123f1433733023986d542e8d2caf458fbb48edb2 /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/daily/boot-initrd 1a8aec22331f411cdbc61c367b7397cf0d6cda7a85afc94c7ebb64ec478c32b8 /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/daily/boot-kernel 0caa3059361ab22a75f9797834ff7bcce372621919122a7d8289b66a1a9c8084 /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/daily/squashfs root@lab-virtual-machine:~# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880749] Re: python3 virtualenvs include (broken) bundled pip deps
** Also affects: python-virtualenv (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: python-virtualenv (Ubuntu Groovy) Importance: Undecided Status: 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/1880749 Title: python3 virtualenvs include (broken) bundled pip deps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1880749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773765] Re: There is a possibility that 'running' notification will remain
** Changed in: charm-masakari Assignee: (unassigned) => Billy Olsen (billy-olsen) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773765 Title: There is a possibility that 'running' notification will remain To manage notifications about this bug go to: https://bugs.launchpad.net/charm-masakari/+bug/1773765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773765] Re: There is a possibility that 'running' notification will remain
** Also affects: charm-masakari 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/1773765 Title: There is a possibility that 'running' notification will remain To manage notifications about this bug go to: https://bugs.launchpad.net/charm-masakari/+bug/1773765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899197] Re: nfs-ganesha fails to start due to Cannot bind RQUOTA udp6 socket
Added the charm-manila-ganesha here as well, though I'm not sure yet which project is at fault. The charm will restart the nfs-ganesha systemd service when config changes. ** Also affects: charm-manila-ganesha 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/1899197 Title: nfs-ganesha fails to start due to Cannot bind RQUOTA udp6 socket To manage notifications about this bug go to: https://bugs.launchpad.net/charm-manila-ganesha/+bug/1899197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899197] [NEW] nfs-ganesha fails to start due to Cannot bind RQUOTA udp6 socket
Public bug reported: Seen in a CI run for manila-ganesha testing, the nfs-ganesha.service daemon fails to start due to inability to bind RQUOTA udp6 socket. Ganesha logs are as below: 07/10/2020 12:45:52 : epoch 5f7db880 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-14269[main] main :MAIN :EVENT :ganesha.nfsd Starting: Ganesha Version 3.0.3 07/10/2020 12:45:52 : epoch 5f7db880 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-14270[main] nfs_set_param_from_conf :NFS STARTUP :EVENT :Configuration file successfully parsed 07/10/2020 12:45:52 : epoch 5f7db880 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-14270[main] init_server_pkgs :NFS STARTUP :EVENT :Initializing ID Mapper. 07/10/2020 12:45:52 : epoch 5f7db880 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-14270[main] init_server_pkgs :NFS STARTUP :EVENT :ID Mapper successfully initialized. 07/10/2020 12:45:52 : epoch 5f7db880 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-14270[main] nfs_start_grace :STATE :EVENT :NFS Server Now IN GRACE, duration 90 07/10/2020 12:45:52 : epoch 5f7db880 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-14270[main] main :NFS STARTUP :WARN :No export entries found in configuration file !!! 07/10/2020 12:45:52 : epoch 5f7db880 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-14270[main] config_errs_to_log :CONFIG :WARN :Config File ((null):0): Empty configuration file 07/10/2020 12:45:52 : epoch 5f7db880 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-14270[main] lower_my_caps :NFS STARTUP :EVENT :CAP_SYS_RESOURCE was successfully removed for proper quota management in FSAL 07/10/2020 12:45:52 : epoch 5f7db880 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-14270[main] lower_my_caps :NFS STARTUP :EVENT :currenty set capabilities are: =ep cap_sys_resource-ep 07/10/2020 12:45:52 : epoch 5f7db880 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-14270[main] Bind_sockets_V6 :DISP :WARN :Cannot bind RQUOTA udp6 socket, error 98 (Address already in use) 07/10/2020 12:45:52 : epoch 5f7db880 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-14270[main] Bind_sockets :DISP :FATAL :Error binding to V6 interface. Cannot continue. 07/10/2020 13:01:26 : epoch 5f7dbc26 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-30592[main] main :MAIN :EVENT :ganesha.nfsd Starting: Ganesha Version 3.0.3 07/10/2020 13:01:26 : epoch 5f7dbc26 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-30595[main] nfs_set_param_from_conf :NFS STARTUP :EVENT :Configuration file successfully parsed 07/10/2020 13:01:26 : epoch 5f7dbc26 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-30595[main] init_server_pkgs :NFS STARTUP :EVENT :Initializing ID Mapper. 07/10/2020 13:01:26 : epoch 5f7dbc26 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-30595[main] init_server_pkgs :NFS STARTUP :EVENT :ID Mapper successfully initialized. 07/10/2020 13:01:26 : epoch 5f7dbc26 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-30595[main] nfs_start_grace :STATE :EVENT :NFS Server Now IN GRACE, duration 90 07/10/2020 13:01:26 : epoch 5f7dbc26 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-30595[main] main :NFS STARTUP :WARN :No export entries found in configuration file !!! 07/10/2020 13:01:26 : epoch 5f7dbc26 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-30595[main] config_errs_to_log :CONFIG :WARN :Config File ((null):0): Empty configuration file 07/10/2020 13:01:26 : epoch 5f7dbc26 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-30595[main] lower_my_caps :NFS STARTUP :EVENT :CAP_SYS_RESOURCE was successfully removed for proper quota management in FSAL 07/10/2020 13:01:26 : epoch 5f7dbc26 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-30595[main] lower_my_caps :NFS STARTUP :EVENT :currenty set capabilities are: =ep cap_sys_resource-ep 07/10/2020 13:01:26 : epoch 5f7dbc26 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-30595[main] Bind_sockets_V6 :DISP :WARN :Cannot bind RQUOTA udp6 socket, error 98 (Address already in use) 07/10/2020 13:01:26 : epoch 5f7dbc26 : juju-d1945d-zaza-3191691493c3-3 : ganesha.nfsd-30595[main] Bind_sockets :DISP :FATAL :Error binding to V6 interface. Cannot continue. ** Affects: nfs-ganesha (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/1899197 Title: nfs-ganesha fails to start due to Cannot bind RQUOTA udp6 socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/1899197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418662/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418659/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418663/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418658/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418660/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418661/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418657/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418655/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418654/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418649/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418644/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418653/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418646/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418652/+files/WifiSyslog.txt ** Description changed: 1. maas:2.4.2 (7034-g2f5deb8b8-0ubuntu1) 2. 18.04(bionic) is good to deploy on the same sut/env. 3. deployment failed on SUT pxe boot stage w/ error below, "Booting under MAAS direction... error: timeout reading 'ubuntu/amd64/ga-20.04/focal/daily/boot-initrd'. press any key to continue..." 4.cross check for 'boot-initrd' file had been found on MAAS sever(ref attachment) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.17 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-10-06 (0 days ago) + InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) + IwConfig: + lono wireless extensions. + + eno1np0 no wireless extensions. + + eno2np1 no wireless extensions. + MachineType: Supermicro Super Server + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 astdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro + ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.15.0-118-generic N/A + linux-backports-modules-4.15.0-118-generic N/A + linux-firmware 1.173.19 + RfKill: + + Tags: bionic uec-images + Uname: Linux 4.15.0-118-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 11/15/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1.0b + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: H12SSW-NT/iN + dmi.board.vendor: Supermicro + dmi.board.version: 0123456789 + dmi.chassis.asset.tag: To be filled by O.E.M. + dmi.chassis.type: 17 + dmi.chassis.vendor: Supermicro + dmi.chassis.version: 0123456789 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: Super Server + dmi.product.version: 0123456789 + dmi.sys.vendor: Supermicro -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/
[Bug 1898808] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418647/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418656/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418650/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418648/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418651/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418643/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] Re: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut
apport information ** Tags added: apport-collected bionic uec-images ** Description changed: 1. maas:2.4.2 (7034-g2f5deb8b8-0ubuntu1) 2. 18.04(bionic) is good to deploy on the same sut/env. 3. deployment failed on SUT pxe boot stage w/ error below, "Booting under MAAS direction... error: timeout reading 'ubuntu/amd64/ga-20.04/focal/daily/boot-initrd'. press any key to continue..." - 4.cross check for 'boot-initrd' file had been found on MAAS sever(ref - attachment) + 4.cross check for 'boot-initrd' file had been found on MAAS sever(ref attachment) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.17 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-10-06 (0 days ago) + InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) + IwConfig: + lono wireless extensions. + + eno1np0 no wireless extensions. + + eno2np1 no wireless extensions. + MachineType: Supermicro Super Server + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 astdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro + ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.15.0-118-generic N/A + linux-backports-modules-4.15.0-118-generic N/A + linux-firmware 1.173.19 + RfKill: + + Tags: bionic uec-images + Uname: Linux 4.15.0-118-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 11/15/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1.0b + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: H12SSW-NT/iN + dmi.board.vendor: Supermicro + dmi.board.version: 0123456789 + dmi.chassis.asset.tag: To be filled by O.E.M. + dmi.chassis.type: 17 + dmi.chassis.vendor: Supermicro + dmi.chassis.version: 0123456789 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: Super Server + dmi.product.version: 0123456789 + dmi.sys.vendor: Supermicro ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418642/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1898808/+attachment/5418645/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898808] [NEW] [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut
Public bug reported: 1. maas:2.4.2 (7034-g2f5deb8b8-0ubuntu1) 2. 18.04(bionic) is good to deploy on the same sut/env. 3. deployment failed on SUT pxe boot stage w/ error below, "Booting under MAAS direction... error: timeout reading 'ubuntu/amd64/ga-20.04/focal/daily/boot-initrd'. press any key to continue..." 4.cross check for 'boot-initrd' file had been found on MAAS sever(ref attachment) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "focal boot-initrd" https://bugs.launchpad.net/bugs/1898808/+attachment/5418641/+files/focal_boot_initrd.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773765] Re: There is a possibility that 'running' notification will remain
Agreed that Groovy should just use the newly-released RC1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773765 Title: There is a possibility that 'running' notification will remain To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1773765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773765] Re: There is a possibility that 'running' notification will remain
** Patch added: "bionic stein patch" https://bugs.launchpad.net/masakari/+bug/1773765/+attachment/5415491/+files/lp1773765-bionic-stein.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773765 Title: There is a possibility that 'running' notification will remain To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1773765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773765] Re: There is a possibility that 'running' notification will remain
** Patch added: "focal patch" https://bugs.launchpad.net/masakari/+bug/1773765/+attachment/5415489/+files/lp1773765-focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773765 Title: There is a possibility that 'running' notification will remain To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1773765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773765] Re: There is a possibility that 'running' notification will remain
** Patch added: "bionic train patch" https://bugs.launchpad.net/masakari/+bug/1773765/+attachment/5415490/+files/lp1773765-bionic-train.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773765 Title: There is a possibility that 'running' notification will remain To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1773765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773765] Re: There is a possibility that 'running' notification will remain
** Patch added: "groovy patch" https://bugs.launchpad.net/masakari/+bug/1773765/+attachment/5415488/+files/lp1773765-groovy.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773765 Title: There is a possibility that 'running' notification will remain To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1773765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773765] Re: There is a possibility that 'running' notification will remain
** Also affects: masakari (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: masakari (Ubuntu Focal) 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/1773765 Title: There is a possibility that 'running' notification will remain To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1773765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773765] Re: There is a possibility that 'running' notification will remain
** Also affects: cloud-archive/victoria
Importance: Undecided
Status: New
** Also affects: cloud-archive/ussuri
Importance: Undecided
Status: New
** Also affects: cloud-archive/stein
Importance: Undecided
Status: New
** Also affects: cloud-archive/train
Importance: Undecided
Status: New
** Changed in: cloud-archive/stein
Importance: Undecided => Medium
** Changed in: cloud-archive/stein
Status: New => In Progress
** Changed in: cloud-archive/stein
Assignee: (unassigned) => Billy Olsen (billy-olsen)
** Changed in: cloud-archive/train
Importance: Undecided => Medium
** Changed in: cloud-archive/train
Status: New => In Progress
** Changed in: cloud-archive/train
Assignee: (unassigned) => Billy Olsen (billy-olsen)
** Changed in: cloud-archive/ussuri
Importance: Undecided => Medium
** Changed in: cloud-archive/ussuri
Status: New => In Progress
** Changed in: cloud-archive/ussuri
Assignee: (unassigned) => Billy Olsen (billy-olsen)
** Changed in: cloud-archive/victoria
Importance: Undecided => Medium
** Changed in: cloud-archive/victoria
Status: New => In Progress
** Changed in: cloud-archive/victoria
Assignee: (unassigned) => Billy Olsen (billy-olsen)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773765
Title:
There is a possibility that 'running' notification will remain
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1773765/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773765] Re: There is a possibility that 'running' notification will remain
** Also affects: cloud-archive 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/1773765 Title: There is a possibility that 'running' notification will remain To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1773765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891567] Re: [SRU] ceph_osd crash in _committed_osd_maps when failed to encode first inc map
** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/ussuri Importance: Undecided Status: New ** Also affects: cloud-archive/victoria Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891567 Title: [SRU] ceph_osd crash in _committed_osd_maps when failed to encode first inc map To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1891567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later
Comment #24 is right. After i reboot to Kernel 5.3.0-51 the problem solved -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873325] Re: update-initramfs complains of missing amdgpu firmware files
Confirm affecting Ubuntu 20.04: --- Processing triggers for initramfs-tools (0.136ubuntu6) ... update-initramfs: Generating /boot/initrd.img-5.4.0-33-generic W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module amdgpu --- OS: Ubuntu 20.04 LTS x86_64 Host: NUC8i7HVK J71485-504 Kernel: 5.4.0-29-generic CPU: Intel i7-8809G (8) @ 4.200GHz GPU: AMD ATI Radeon RX Vega M GH Memory: 5031MiB / 64282MiB -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873325 Title: update-initramfs complains of missing amdgpu firmware files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later
Ubuntu 18.04.4 AMD 3400G 5.3.0-53-generic same problem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737428] Re: VRF support to solve routing problems associated with multi-homing
@bjornt Are you going to copy it over to the MAAS discourse feature set then? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737428 Title: VRF support to solve routing problems associated with multi-homing To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875759] [NEW] keeps crashing
Public bug reported: not sure it's a bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-96.97~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Apr 28 18:10:36 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems RS880M [Mobility Radeon HD 4225/4250] [1179:ff1f] InstallationDate: Installed on 2020-04-19 (9 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: TOSHIBA Satellite L505D ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=4e2c2708-04af-4c97-ae5b-247752b16fe1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2009 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.00 dmi.board.asset.tag: No Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnInsydeCorp.:bvr1.00:bd09/07/2009:svnTOSHIBA:pnSatelliteL505D:pvrPSLV6U-01F009:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone: dmi.product.family: Type1Family dmi.product.name: Satellite L505D dmi.product.version: PSLV6U-01F009 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Apr 28 17:50:45 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875759 Title: keeps crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844455] Re: Memory leak of struct _virPCIDeviceAddress on libvirt
** Also affects: cloud-archive/queens Importance: Undecided Status: New ** Changed in: cloud-archive/queens Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Changed in: cloud-archive/queens Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844455 Title: Memory leak of struct _virPCIDeviceAddress on libvirt To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1844455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835024] Re: Links triggered within most snap apps open in a separate browser session
Setting the default profile to `default-release` fixed the problem for me as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835024 Title: Links triggered within most snap apps open in a separate browser session To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1835024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
