[Touch-packages] [Bug 2086844] [NEW] [SRU] Enable support for Epoxy Cloud Archive
Public bug reported: Please add support for: cloud-archive:epoxy cloud-archive:epoxy-proposed This will also need to be SRU'd back to noble. [Impact] End users have to manually enable the epoxy cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:epoxy sudo add-apt-repository cloud-archive:epoxy-proposed apt policy openstack-release Verify that the expected version is available to "apt policy", and report that version in the SRU verification bug comment. [Regression potential] Limited - just a data item addition ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Noble) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu Plucky) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Plucky) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2086844 Title: [SRU] Enable support for Epoxy Cloud Archive Status in software-properties package in Ubuntu: New Status in software-properties source package in Noble: New Status in software-properties source package in Plucky: New Bug description: Please add support for: cloud-archive:epoxy cloud-archive:epoxy-proposed This will also need to be SRU'd back to noble. [Impact] End users have to manually enable the epoxy cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:epoxy sudo add-apt-repository cloud-archive:epoxy-proposed apt policy openstack-release Verify that the expected version is available to "apt policy", and report that version in the SRU verification bug comment. [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2086844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2069433] Re: Enabling new pockets does not enable deb-src for them, even if source code is enabled
sorry - I don't only have an oracular desktop right now :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2069433 Title: Enabling new pockets does not enable deb-src for them, even if source code is enabled Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Noble: Fix Committed Bug description: [Impact] If you have Source Code enabled, and you change the pockets configuration to "all pockets", it will add -backports without source code. The Source Code flag will still be set in the UI, but after a reload, you can see it is in a mixed state. This is more notable now, because this splits up the deb822 paragraph into two: One for the deb, and one for deb-src, whereas it should remain one. [Test plan] 1. Turn on source code, save and refresh sources, close app 2. Start again, observe the flag is on. 3. Turn "recommended updates" to "all updates", observe that -backports got added with deb-src, to the existing paragraph. 4. Restart the app and observe that the flag is still on. [Where problems could occur] This incurs a performance regression, as we need to check the state of the source code flag after reloading sources. That said, this is of course necessary for the source code flag to be correct after reloading modified sources (it gets reset to False when reloading). And since we run in a dbus service, we may just be reloading without having made the changes ourselves, so we can't just cache the old value and restore it. That said, software-properties already times out on my oracular system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2069433/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2073742] Re: [SRU] Enable support for Dalmation Cloud Archive
@martinx I'm chasing on getting this released - in the meantime I've just promoted all of the release packages to the updates pocket for dalmatian: ppa:ubuntu-cloud-archive/dalmatian-updates these are the packages that feed the official cloud archive repositories that add-apt-repository will setup usually. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2073742 Title: [SRU] Enable support for Dalmation Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Noble: Fix Committed Status in software-properties source package in Oracular: Fix Released Bug description: Please add support for: cloud-archive:dalmation cloud-archive:dalmation-proposed This will also need to be SRU'd back to noble. [Impact] End users have to manually enable the dalmation cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:dalmation sudo add-apt-repository cloud-archive:dalmation-proposed apt policy openstack-release Verify that the expected version is available to "apt policy", and report that version in the SRU verification bug comment. [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2073742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2069433] Re: Enabling new pockets does not enable deb-src for them, even if source code is enabled
@juliank what's the status on this part of the SRU? its blocking the release for the OpenStack Dalmatian enablement which I'd like to get out in the next week or so alongside the release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2069433 Title: Enabling new pockets does not enable deb-src for them, even if source code is enabled Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Noble: Fix Committed Bug description: [Impact] If you have Source Code enabled, and you change the pockets configuration to "all pockets", it will add -backports without source code. The Source Code flag will still be set in the UI, but after a reload, you can see it is in a mixed state. This is more notable now, because this splits up the deb822 paragraph into two: One for the deb, and one for deb-src, whereas it should remain one. [Test plan] 1. Turn on source code, save and refresh sources, close app 2. Start again, observe the flag is on. 3. Turn "recommended updates" to "all updates", observe that -backports got added with deb-src, to the existing paragraph. 4. Restart the app and observe that the flag is still on. [Where problems could occur] This incurs a performance regression, as we need to check the state of the source code flag after reloading sources. That said, this is of course necessary for the source code flag to be correct after reloading modified sources (it gets reset to False when reloading). And since we run in a dbus service, we may just be reloading without having made the changes ourselves, so we can't just cache the old value and restore it. That said, software-properties already times out on my oracular system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2069433/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2073742] Re: [SRU] Enable support for Dalmation Cloud Archive
I tweaked the test plan a little to use the openstack-release package which is the first package we place into the cloud-archive. # apt policy openstack-release openstack-release: Installed: (none) Candidate: 8.0ubuntu1~cloud0 Version table: 8.0ubuntu1~cloud0 500 500 http://ubuntu-cloud.archive.canonical.com/ubuntu noble-updates/dalmatian/main amd64 Packages 7.0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages ** Description changed: Please add support for: cloud-archive:dalmation cloud-archive:dalmation-proposed This will also need to be SRU'd back to noble. [Impact] End users have to manually enable the dalmation cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:dalmation sudo add-apt-repository cloud-archive:dalmation-proposed - apt policy python3-openstackclient + apt policy openstack-release Verify that the expected version is available to "apt policy", and report that version in the SRU verification bug comment. [Regression potential] Limited - just a data item addition ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2073742 Title: [SRU] Enable support for Dalmation Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Noble: Fix Committed Status in software-properties source package in Oracular: Fix Released Bug description: Please add support for: cloud-archive:dalmation cloud-archive:dalmation-proposed This will also need to be SRU'd back to noble. [Impact] End users have to manually enable the dalmation cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:dalmation sudo add-apt-repository cloud-archive:dalmation-proposed apt policy openstack-release Verify that the expected version is available to "apt policy", and report that version in the SRU verification bug comment. [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2073742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2026757] Re: dnsmasq on Ubuntu Jammy crashes on neutron-dhcp-agent updates
dnsmasq in Jammy was updated to a 2.90 based to resolve some security issues. As a result this bug may have been fixed by the rollforward to a new version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2026757 Title: dnsmasq on Ubuntu Jammy crashes on neutron-dhcp-agent updates Status in Ironic: Triaged Status in neutron: New Status in dnsmasq package in Ubuntu: Invalid Status in dnsmasq source package in Jammy: Incomplete Status in dnsmasq source package in Kinetic: Won't Fix Status in dnsmasq source package in Lunar: Invalid Status in dnsmasq source package in Mantic: Invalid Bug description: The Ironic project's CI has been having major blocking issues moving to utilizing Ubuntu Jammy and with some investigation we were able to isolate the issues down to the dhcp updates causing dnsmasq to crash on Ubuntu Jammy, which ships with dnsmasq 2.86. This issue sounds similar to an issue known about to the dnsmasq maintainers, where dnsmasq would crash with updates occurring due to configuration refresh[0]. This resulted in us upgrading dnsmasq to the version which ships with Ubuntu Lunar. Which was no better. Dnsmasq still crashed upon record updates for addresses and ports getting configuration added/changed/removed. We later downgraded to the version of dnsmasq shipped in Ubuntu Focal, and dnsmasq stopped crashing and appeared stable enough to utilize for CI purposes. ** Kernel log from Ubuntu Jammy Package ** [229798.876726] dnsmasq[81586]: segfault at 7c28 ip 7f6e8313147e sp 7fffb3d6f830 error 4 in libc.so.6[7f6e830b4000+195000] [229798.876745] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [229805.444912] dnsmasq[401428]: segfault at dce8 ip 7fe63bf6a47e sp 7ffdb105b440 error 4 in libc.so.6[7fe63beed000+195000] [229805.444933] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [230414.213448] dnsmasq[401538]: segfault at 78b8 ip 7f12160e447e sp 7ffed6ef2190 error 4 in libc.so.6[7f1216067000+195000] [230414.213467] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [230465.098989] dnsmasq[402665]: segfault at c378 ip 7f81458f047e sp 7fff0db334a0 error 4 in libc.so.6[7f8145873000+195000] [230465.099005] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [231787.247374] dnsmasq[402863]: segfault at 7318 ip 7f3940b9147e sp 7ffc8df4f010 error 4 in libc.so.6[7f3940b14000+195000] [231787.247392] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [231844.886399] dnsmasq[405182]: segfault at dc58 ip 7f32a29e147e sp 7ffddedd7480 error 4 in libc.so.6[7f32a2964000+195000] [231844.886420] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [234692.482154] dnsmasq[405289]: segfault at 67d8 ip 7fab0c5c447e sp 7fffd6fd8fa0 error 4 in libc.so.6[7fab0c547000+195000] [234692.482173] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a ** Kernel log entries from Ubuntu Lunar package ** [234724.842339] dnsmasq[409843]: segfault at fffd ip 7f35a147647e sp 7ffd536038c0 error 5 in libc.so.6[7f35a13f9000+195000] [234724.842368] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [234784.918116] dnsmasq[410019]: segfault at fffd ip 7f634233947e sp 7fff33877f20 error 5 in libc.so.6[7f63422bc000+195000] [234784.918133] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [235022.163339] dnsmasq[410151]: segfault at fffd ip 7f21dd37f47e sp 7fff9bf416d0 error 5
[Touch-packages] [Bug 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12
Merged version uploaded which should unblock the autopkgtest. ** Changed in: python-oslo.versionedobjects (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2049369 Title: autopkg tests ignored for migration of python3-defaults adding 3.12 Status in cython package in Ubuntu: New Status in cython-legacy package in Ubuntu: New Status in ipykernel package in Ubuntu: New Status in ironic-python-agent package in Ubuntu: New Status in jupyter-client package in Ubuntu: New Status in numpy package in Ubuntu: New Status in python-memory-profiler package in Ubuntu: New Status in python-oslo.versionedobjects package in Ubuntu: Fix Committed Status in python-urllib3 package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in rich package in Ubuntu: New Status in sphinx-autoapi package in Ubuntu: New Status in vcr.py package in Ubuntu: New Status in cython package in Debian: Unknown Status in cython-legacy package in Debian: New Status in ipykernel package in Debian: New Status in jupyter-client package in Debian: New Status in numpy package in Debian: New Status in python-memory-profiler package in Debian: New Status in python-urllib3 package in Debian: New Status in rich package in Debian: Confirmed Status in sphinx-autoapi package in Debian: Unknown Status in vcr.py package in Debian: Unknown Bug description: autopkg tests ignored for migration of python3-defaults adding 3.12: These are the autopkg tests for packages, which we'll ignore for the initial migration of python3-defaults adding 3.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cython/+bug/2049369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12
The oslo.versionedobjects autopkgtests appear to be broken in Debian (but working in the 0ubuntu1 version we had before); I'll untangle this and upload a merged version to fix this. ** Changed in: python-oslo.versionedobjects (Ubuntu) Importance: Undecided => High ** Changed in: python-oslo.versionedobjects (Ubuntu) Status: New => In Progress ** Changed in: python-oslo.versionedobjects (Ubuntu) Assignee: (unassigned) => James Page (james-page) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2049369 Title: autopkg tests ignored for migration of python3-defaults adding 3.12 Status in cython package in Ubuntu: New Status in cython-legacy package in Ubuntu: New Status in ipykernel package in Ubuntu: New Status in ironic-python-agent package in Ubuntu: New Status in jupyter-client package in Ubuntu: New Status in numpy package in Ubuntu: New Status in python-memory-profiler package in Ubuntu: New Status in python-oslo.versionedobjects package in Ubuntu: In Progress Status in python-urllib3 package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in rich package in Ubuntu: New Status in sphinx-autoapi package in Ubuntu: New Status in vcr.py package in Ubuntu: New Status in cython package in Debian: Unknown Status in cython-legacy package in Debian: New Status in ipykernel package in Debian: New Status in jupyter-client package in Debian: New Status in numpy package in Debian: New Status in python-memory-profiler package in Debian: New Status in python-urllib3 package in Debian: New Status in rich package in Debian: Confirmed Status in sphinx-autoapi package in Debian: Unknown Status in vcr.py package in Debian: Unknown Bug description: autopkg tests ignored for migration of python3-defaults adding 3.12: These are the autopkg tests for packages, which we'll ignore for the initial migration of python3-defaults adding 3.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cython/+bug/2049369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848237] Re: amd64-only test running on i386
Fixed generally in 1.6.0-5
** Changed in: python-pyeclib (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to six in Ubuntu.
https://bugs.launchpad.net/bugs/1848237
Title:
amd64-only test running on i386
Status in python-pyeclib package in Ubuntu:
Fix Released
Status in six package in Ubuntu:
Invalid
Bug description:
Some tests in d/t/control are not meant to be run on non-amd64 architectures.
The test script tries to detect this and skip them:
arch = platform.machine()
if sys.argv[1].startswith('isa_') and arch == 'x86_64':
print("Skipping {} test for {} architecture".format(sys.argv[1], arch))
else:
...
In eoan, at some point during the development cycle, the VM running i386
tests is actually on an amd64 kernel:
"""
...
-name adt-eoan-i386-python-pyeclib-20191014-091043 --image
adt/ubuntu-eoan-i386-server
...
Get:5 http://ftpmaster.internal/ubuntu eoan-proposed/universe Sources [127 kB]
Get:6 http://ftpmaster.internal/ubuntu eoan-proposed/main amd64 Packages
[18.0 kB]
Get:7 http://ftpmaster.internal/ubuntu eoan-proposed/main i386 Packages [12.9
kB]
...
linux-generic:amd64 is already the newest version (5.3.0.18.21).
...
utopkgtest [09:11:51]: testbed running kernel: Linux 5.3.0-18-generic
#19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019
autopkgtest [09:11:51]: testbed dpkg architecture: i386
"""
In such an environment, platform.machine() will return "x86_64", and the test
will be run, but fail:
autopkgtest [09:22:26]: test command7: python debian/tests/encode-decode.py
isa_l_rs_vand
autopkgtest [09:22:26]: test command7: [---
Traceback (most recent call last):
File "debian/tests/encode-decode.py", line 15, in
ec = ECDriver(k=3, m=3, hd=3, ec_type=sys.argv[1])
File "/usr/lib/python2.7/dist-packages/pyeclib/ec_iface.py", line 212, in
__init__
validate=int(self.validate)
File "/usr/lib/python2.7/dist-packages/pyeclib/utils.py", line 73, in
create_instance
instance = object_class(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/pyeclib/core.py", line 61, in
__init__
validate)
pyeclib.ec_iface.ECBackendInstanceNotAvailable: pyeclib_c_init ERROR: Backend
instance not found. Please inspect syslog for liberasurecode error report.
init: autopkgtest [09:22:26]: test command7: ---]
It's probably best to use "dpkg --architecture" for this check.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pyeclib/+bug/1848237/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 889889] Re: Use PNG or SVG instead of GIF
Marking the charset task as invalid - 4.0.0 does not appear to have any gif files. ** Changed in: chardet (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to chardet in Ubuntu. https://bugs.launchpad.net/bugs/889889 Title: Use PNG or SVG instead of GIF Status in Adium Theme Ubuntu: Fix Released Status in OpenSSL: New Status in ace package in Ubuntu: New Status in app-install-data-ubuntu package in Ubuntu: Confirmed Status in blender package in Ubuntu: Fix Released Status in chardet package in Ubuntu: Invalid Status in cups package in Ubuntu: New Status in dvd+rw-tools package in Ubuntu: New Status in foo2zjs package in Ubuntu: New Status in libcgi-pm-perl package in Ubuntu: New Status in openssl package in Ubuntu: Won't Fix Status in python3.4 package in Ubuntu: Won't Fix Status in software-center package in Ubuntu: Invalid Bug description: Use modern file formats such as PNG or SVG instead of the legacy GIF file formats. $ find /usr -name "*.gif" To manage notifications about this bug go to: https://bugs.launchpad.net/adium-theme-ubuntu/+bug/889889/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443527] Re: package python-chardet 2.0.1-2build1 failed to install/upgrade: package python-chardet is already installed and configured
Closing this bug as it related to a Ubuntu release with is EOL - please re-open if its still a problem. ** Changed in: chardet (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to chardet in Ubuntu. https://bugs.launchpad.net/bugs/1443527 Title: package python-chardet 2.0.1-2build1 failed to install/upgrade: package python-chardet is already installed and configured Status in chardet package in Ubuntu: Won't Fix Bug description: no information ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-chardet ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic i686 ApportVersion: 2.14.1-0ubuntu3.8 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: i386 Date: Mon Apr 13 21:40:48 2015 DuplicateSignature: package:python-chardet:2.0.1-2build1:package python-chardet is already installed and configured ErrorMessage: package python-chardet is already installed and configured InstallationDate: Installed on 2015-04-13 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) PackageArchitecture: all SourcePackage: chardet Title: package python-chardet 2.0.1-2build1 failed to install/upgrade: package python-chardet is already installed and configured UpgradeStatus: Upgraded to trusty on 2015-04-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chardet/+bug/1443527/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648263] Re: package python-chardet 2.3.0-2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
Closing this bug as it related to a Ubuntu release with is EOL - please re-open if its still a problem. ** Changed in: chardet (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to chardet in Ubuntu. https://bugs.launchpad.net/bugs/1648263 Title: package python-chardet 2.3.0-2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 Status in chardet package in Ubuntu: Won't Fix Bug description: What i do? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-chardet 2.3.0-2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Wed Dec 7 21:27:50 2016 Dependencies: python-pkg-resources 20.7.0-1 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2016-12-07 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: chardet Title: package python-chardet 2.3.0-2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chardet/+bug/1648263/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 421073] Re: package python-chardet 1.0.1-1.1 failed to install/upgrade: subprocess post-installation script returned errorcode 1
Closing this bug as it related to a Ubuntu release with is EOL - please re-open if its still a problem. ** Changed in: chardet (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to chardet in Ubuntu. https://bugs.launchpad.net/bugs/421073 Title: package python-chardet 1.0.1-1.1 failed to install/upgrade: subprocess post-installation script returned errorcode 1 Status in chardet package in Ubuntu: Invalid Bug description: Tried to install screenlets and installed python-chardet at same time. Anyway that failed with this error: Compiling /usr/lib/python2.5/site-packages/chardet/gb2312freq.py ... File "/usr/lib/python2.5/site-packages/chardet/gb2312freq.py", line 471 ^ SyntaxError: invalid syntax pycentral: pycentral pkginstall: error byte-compiling files (36) pycentral pkginstall: error byte-compiling files (36) ProblemType: Package Architecture: i386 DistroRelease: Ubuntu 9.04 ErrorMessage: aliprosessi post-installation script palautti virhetilakoodin 1 NonfreeKernelModules: nvidia Package: python-chardet 1.0.1-1.1 PackageArchitecture: all SourcePackage: chardet Title: package python-chardet 1.0.1-1.1 failed to install/upgrade: aliprosessi post-installation script palautti virhetilakoodin 1 Uname: Linux 2.6.28-15-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chardet/+bug/421073/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 623026] Re: package python-chardet 1.0.1-1.1 failed to install/upgrade: ErrorMessage: Package is in a very bad inconsistent state - you should reinstall it before attempting conf
Closing this bug as it related to a Ubuntu release with is EOL - please re-open if its still a problem. ** Changed in: chardet (Ubuntu) Status: New => Opinion ** Changed in: chardet (Ubuntu) Status: Opinion => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to chardet in Ubuntu. https://bugs.launchpad.net/bugs/623026 Title: package python-chardet 1.0.1-1.1 failed to install/upgrade: ErrorMessage: Package is in a very bad inconsistent state - you should reinstall it before attempting configuration. Status in chardet package in Ubuntu: Invalid Bug description: seems to be important- i'#m not sure whi this is happening. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: python-chardet 1.0.1-1.1 ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Aug 23 22:03:36 2010 ErrorMessage: ErrorMessage: Package is in a very bad inconsistent state - you should reinstall it before attempting configuration. InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) PackageArchitecture: all SourcePackage: chardet Title: package python-chardet 1.0.1-1.1 failed to install/upgrade: ErrorMessage: Package is in a very bad inconsistent state - you should reinstall it before attempting configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chardet/+bug/623026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 353560] Re: Using synaptic package manager crashes
As this bug related to a release which is no longer supported (8.10) closing - please re-open if this is still a problem on supported Ubuntu releases. ** Changed in: chardet (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to chardet in Ubuntu. https://bugs.launchpad.net/bugs/353560 Title: Using synaptic package manager crashes Status in chardet package in Ubuntu: Invalid Bug description: chardet (python) installation led to synaptic package installation error ProblemType: Package Architecture: i386 DistroRelease: Ubuntu 8.10 ErrorMessage: subprocess post-installation script returned error exit status 1 Package: python-chardet 1.0.1-1 PackageArchitecture: all SourcePackage: chardet Title: package python-chardet 1.0.1-1 failed to install/upgrade: subprocess post-installation script returned error exit status 1 Uname: Linux 2.6.27-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chardet/+bug/353560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878752] Re: vgcreate fails on /dev/disk/by-dname block devices
** Changed in: charm-ceph-osd
Status: New => Invalid
** Changed in: lvm2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1878752
Title:
vgcreate fails on /dev/disk/by-dname block devices
Status in OpenStack ceph-osd charm:
Invalid
Status in curtin package in Ubuntu:
Invalid
Status in lvm2 package in Ubuntu:
Invalid
Bug description:
Ubuntu Focal, OpenStack Charmers Next Charms.
juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
dname/bcache2
unit-ceph-osd-0:
UnitId: ceph-osd/0
id: "5"
message: exit status 1
results:
ReturnCode: 1
Stderr: |
partx: /dev/disk/by-dname/bcache2: failed to read partition table
Failed to find physical volume "/dev/bcache1".
Failed to find physical volume "/dev/bcache1".
Device /dev/disk/by-dname/bcache2 not found.
Traceback (most recent call last):
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 79, in
request = add_device(request=request,
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 34, in add_device
charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
File "lib/charms_ceph/utils.py", line 1497, in osdize
osdize_dev(dev, osd_format, osd_journal,
File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
cmd = _ceph_volume(dev,
File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
cmd.append(_allocate_logical_volume(dev=dev,
File "lib/charms_ceph/utils.py", line 1965, in
_allocate_logical_volume
lvm.create_lvm_volume_group(vg_name, pv_dev)
File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in
create_lvm_volume_group
check_call(['vgcreate', volume_group, block_device])
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['vgcreate',
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']'
returned non-zero exit status 5.
Stdout: |2
Physical volume "/dev/disk/by-dname/bcache2" successfully created.
status: failed
timing:
completed: 2020-05-15 06:04:41 + UTC
enqueued: 2020-05-15 06:04:30 + UTC
started: 2020-05-15 06:04:39 + UTC
The same action on the /dev/bcacheX device succeeds - looks like some
sort of behaviour break in Ubuntu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1898547] Re: neutron-linuxbridge-agent fails to start with iptables 1.8.5
** Changed in: iptables (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: iptables (Ubuntu Groovy) Importance: Undecided => High ** Changed in: iptables (Ubuntu Groovy) Status: New => Triaged ** Changed in: iptables (Ubuntu Hirsute) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1898547 Title: neutron-linuxbridge-agent fails to start with iptables 1.8.5 Status in iptables package in Ubuntu: Triaged Status in neutron package in Ubuntu: Invalid Status in iptables source package in Groovy: Triaged Status in neutron source package in Groovy: Invalid Status in iptables source package in Hirsute: Triaged Status in neutron source package in Hirsute: Invalid Bug description: Ubuntu Groovy (20.10) kernel 5.8.0-20-generic neutron-linuxbridge-agent: 2:17.0.0~git2020091014.215a541bd4-0ubuntu1 iptables: 1.8.5-3ubuntu1 (nf_tables) iptables-restore points to xtables-nft-multi After upgrading iptables from 1.8.4 to 1.8.5 and rebooting the neutron network node, neutron-linuxbridge-agent didn't properly start anymore. The log file shows many errors like: 2020-10-05 10:20:37.998 551 ERROR neutron.plugins.ml2.drivers.agent._common_agent ; Stdout: ; Stderr: iptables-restore: line 29 failed Downgrading iptables to 1.8.4 solves the problem. Trying to do what the linuxbridge agent does: 2020-10-05 10:20:37.998 551 ERROR neutron.plugins.ml2.drivers.agent._common_agent *filter 2020-10-05 10:20:37.998 551 ERROR neutron.plugins.ml2.drivers.agent._common_agent :FORWARD - [0:0] shows that iptables-restore
[Touch-packages] [Bug 1898547] Re: neutron-linuxbridge-agent fails to start with iptables 1.8.5
Link to upstream commit - https://git.netfilter.org/iptables/commit/?id=0bd7a8eaf3582159490ab355b1217a4e42ed021f ** Also affects: iptables (Ubuntu Hirsute) Importance: Undecided Status: Confirmed ** Also affects: neutron (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Also affects: iptables (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: neutron (Ubuntu Groovy) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1898547 Title: neutron-linuxbridge-agent fails to start with iptables 1.8.5 Status in iptables package in Ubuntu: Confirmed Status in neutron package in Ubuntu: Invalid Status in iptables source package in Groovy: New Status in neutron source package in Groovy: Invalid Status in iptables source package in Hirsute: Confirmed Status in neutron source package in Hirsute: Invalid Bug description: Ubuntu Groovy (20.10) kernel 5.8.0-20-generic neutron-linuxbridge-agent: 2:17.0.0~git2020091014.215a541bd4-0ubuntu1 iptables: 1.8.5-3ubuntu1 (nf_tables) iptables-restore points to xtables-nft-multi After upgrading iptables from 1.8.4 to 1.8.5 and rebooting the neutron network node, neutron-linuxbridge-agent didn't properly start anymore. The log file shows many errors like: 2020-10-05 10:20:37.998 551 ERROR neutron.plugins.ml2.drivers.agent._common_agent ; Stdout: ; Stderr: iptables-restore: line 29 failed Downgrading iptables to 1.8.4 solves the problem. Trying to do what the linuxbridge agent does: 2020-10-05 10:20:37.998 551 ERROR neutron.plugins.ml2.drivers.agent._common_agent *filter 2020-10-05 10:20:37.998 551 ERROR neutron.plugins.ml2.drivers.agent._common_agent :FORWARD - [0:0] shows that iptables-restore
[Touch-packages] [Bug 1878752] Re: vgcreate fails on /dev/disk/by-dname block devices
** Attachment added: "lib-udev.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1878752/+attachment/5372124/+files/lib-udev.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1878752
Title:
vgcreate fails on /dev/disk/by-dname block devices
Status in OpenStack ceph-osd charm:
New
Status in curtin package in Ubuntu:
New
Status in lvm2 package in Ubuntu:
New
Bug description:
Ubuntu Focal, OpenStack Charmers Next Charms.
juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
dname/bcache2
unit-ceph-osd-0:
UnitId: ceph-osd/0
id: "5"
message: exit status 1
results:
ReturnCode: 1
Stderr: |
partx: /dev/disk/by-dname/bcache2: failed to read partition table
Failed to find physical volume "/dev/bcache1".
Failed to find physical volume "/dev/bcache1".
Device /dev/disk/by-dname/bcache2 not found.
Traceback (most recent call last):
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 79, in
request = add_device(request=request,
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 34, in add_device
charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
File "lib/charms_ceph/utils.py", line 1497, in osdize
osdize_dev(dev, osd_format, osd_journal,
File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
cmd = _ceph_volume(dev,
File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
cmd.append(_allocate_logical_volume(dev=dev,
File "lib/charms_ceph/utils.py", line 1965, in
_allocate_logical_volume
lvm.create_lvm_volume_group(vg_name, pv_dev)
File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in
create_lvm_volume_group
check_call(['vgcreate', volume_group, block_device])
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['vgcreate',
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']'
returned non-zero exit status 5.
Stdout: |2
Physical volume "/dev/disk/by-dname/bcache2" successfully created.
status: failed
timing:
completed: 2020-05-15 06:04:41 + UTC
enqueued: 2020-05-15 06:04:30 + UTC
started: 2020-05-15 06:04:39 + UTC
The same action on the /dev/bcacheX device succeeds - looks like some
sort of behaviour break in Ubuntu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878752] Re: vgcreate fails on /dev/disk/by-dname block devices
** Attachment added: "etc-udev.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1878752/+attachment/5372125/+files/etc-udev.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1878752
Title:
vgcreate fails on /dev/disk/by-dname block devices
Status in OpenStack ceph-osd charm:
New
Status in curtin package in Ubuntu:
New
Status in lvm2 package in Ubuntu:
New
Bug description:
Ubuntu Focal, OpenStack Charmers Next Charms.
juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
dname/bcache2
unit-ceph-osd-0:
UnitId: ceph-osd/0
id: "5"
message: exit status 1
results:
ReturnCode: 1
Stderr: |
partx: /dev/disk/by-dname/bcache2: failed to read partition table
Failed to find physical volume "/dev/bcache1".
Failed to find physical volume "/dev/bcache1".
Device /dev/disk/by-dname/bcache2 not found.
Traceback (most recent call last):
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 79, in
request = add_device(request=request,
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 34, in add_device
charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
File "lib/charms_ceph/utils.py", line 1497, in osdize
osdize_dev(dev, osd_format, osd_journal,
File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
cmd = _ceph_volume(dev,
File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
cmd.append(_allocate_logical_volume(dev=dev,
File "lib/charms_ceph/utils.py", line 1965, in
_allocate_logical_volume
lvm.create_lvm_volume_group(vg_name, pv_dev)
File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in
create_lvm_volume_group
check_call(['vgcreate', volume_group, block_device])
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['vgcreate',
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']'
returned non-zero exit status 5.
Stdout: |2
Physical volume "/dev/disk/by-dname/bcache2" successfully created.
status: failed
timing:
completed: 2020-05-15 06:04:41 + UTC
enqueued: 2020-05-15 06:04:30 + UTC
started: 2020-05-15 06:04:39 + UTC
The same action on the /dev/bcacheX device succeeds - looks like some
sort of behaviour break in Ubuntu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878752] Re: vgcreate fails on /dev/disk/by-dname block devices
OK so it sees the pv* commands have a side-effect of dropping the by-
dname entries, so when the charm creates the PV and then tries to use it
for the VG its disappeared.
ubuntu@node-licetus:~$ sudo pvcreate /dev/disk/by-dname/bcache3
Physical volume "/dev/disk/by-dname/bcache3" successfully created.
ubuntu@node-licetus:~$ ls -l /dev/disk/by-dname/
total 0
lrwxrwxrwx 1 root root 13 May 15 06:18 bcache1 -> ../../bcache2
lrwxrwxrwx 1 root root 13 May 15 06:18 bcache2 -> ../../bcache1
lrwxrwxrwx 1 root root 13 May 15 06:18 bcache43 -> ../../bcache3
lrwxrwxrwx 1 root root 13 May 15 06:18 nvme0n1 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 May 15 06:18 nvme0n1-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 May 15 06:18 nvme0n1-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 9 May 15 06:18 sda -> ../../sda
lrwxrwxrwx 1 root root 10 May 15 06:18 sda-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 May 15 06:18 sda-part2 -> ../../sda2
lrwxrwxrwx 1 root root 9 May 15 06:18 sdb -> ../../sdb
lrwxrwxrwx 1 root root 9 May 15 06:18 sdc -> ../../sdc
lrwxrwxrwx 1 root root 9 May 15 06:18 sdd -> ../../sdd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1878752
Title:
vgcreate fails on /dev/disk/by-dname block devices
Status in OpenStack ceph-osd charm:
New
Status in lvm2 package in Ubuntu:
New
Bug description:
Ubuntu Focal, OpenStack Charmers Next Charms.
juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
dname/bcache2
unit-ceph-osd-0:
UnitId: ceph-osd/0
id: "5"
message: exit status 1
results:
ReturnCode: 1
Stderr: |
partx: /dev/disk/by-dname/bcache2: failed to read partition table
Failed to find physical volume "/dev/bcache1".
Failed to find physical volume "/dev/bcache1".
Device /dev/disk/by-dname/bcache2 not found.
Traceback (most recent call last):
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 79, in
request = add_device(request=request,
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 34, in add_device
charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
File "lib/charms_ceph/utils.py", line 1497, in osdize
osdize_dev(dev, osd_format, osd_journal,
File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
cmd = _ceph_volume(dev,
File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
cmd.append(_allocate_logical_volume(dev=dev,
File "lib/charms_ceph/utils.py", line 1965, in
_allocate_logical_volume
lvm.create_lvm_volume_group(vg_name, pv_dev)
File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in
create_lvm_volume_group
check_call(['vgcreate', volume_group, block_device])
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['vgcreate',
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']'
returned non-zero exit status 5.
Stdout: |2
Physical volume "/dev/disk/by-dname/bcache2" successfully created.
status: failed
timing:
completed: 2020-05-15 06:04:41 + UTC
enqueued: 2020-05-15 06:04:30 + UTC
started: 2020-05-15 06:04:39 + UTC
The same action on the /dev/bcacheX device succeeds - looks like some
sort of behaviour break in Ubuntu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878752] Re: vgcreate fails on /dev/disk/by-dname block devices
ubuntu@node-licetus:~$ sudo vgcreate ceph-911bc34b-4634-4ebd-a055-876b978d0b0a
/dev/disk/by-dname/bcache2
Physical volume "/dev/disk/by-dname/bcache2" successfully created.
Volume group "ceph-911bc34b-4634-4ebd-a055-876b978d0b0a" successfully created
ubuntu@node-licetus:~$ ls -l /dev/disk/by-dname/
total 0
lrwxrwxrwx 1 root root 13 May 15 06:12 bcache1 -> ../../bcache2
lrwxrwxrwx 1 root root 13 May 15 06:12 bcache3 -> ../../bcache0
lrwxrwxrwx 1 root root 13 May 15 06:12 bcache43 -> ../../bcache3
lrwxrwxrwx 1 root root 13 May 15 06:12 nvme0n1 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 May 15 06:12 nvme0n1-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 May 15 06:12 nvme0n1-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 9 May 15 06:12 sda -> ../../sda
lrwxrwxrwx 1 root root 10 May 15 06:12 sda-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 May 15 06:12 sda-part2 -> ../../sda2
lrwxrwxrwx 1 root root 9 May 15 06:12 sdb -> ../../sdb
lrwxrwxrwx 1 root root 9 May 15 06:12 sdc -> ../../sdc
lrwxrwxrwx 1 root root 9 May 15 06:12 sdd -> ../../sdd
ubuntu@node-licetus:~$ sudo udevadm trigger --subsystem-match=block --action=add
ubuntu@node-licetus:~$ ls -l /dev/disk/by-dname/
total 0
lrwxrwxrwx 1 root root 13 May 15 06:14 bcache1 -> ../../bcache2
lrwxrwxrwx 1 root root 13 May 15 06:14 bcache2 -> ../../bcache1
lrwxrwxrwx 1 root root 13 May 15 06:14 bcache3 -> ../../bcache0
lrwxrwxrwx 1 root root 13 May 15 06:14 bcache43 -> ../../bcache3
lrwxrwxrwx 1 root root 13 May 15 06:14 nvme0n1 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 May 15 06:14 nvme0n1-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 May 15 06:14 nvme0n1-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 9 May 15 06:14 sda -> ../../sda
lrwxrwxrwx 1 root root 10 May 15 06:14 sda-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 May 15 06:14 sda-part2 -> ../../sda2
lrwxrwxrwx 1 root root 9 May 15 06:14 sdb -> ../../sdb
lrwxrwxrwx 1 root root 9 May 15 06:14 sdc -> ../../sdc
lrwxrwxrwx 1 root root 9 May 15 06:14 sdd -> ../../sdd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1878752
Title:
vgcreate fails on /dev/disk/by-dname block devices
Status in OpenStack ceph-osd charm:
New
Status in lvm2 package in Ubuntu:
New
Bug description:
Ubuntu Focal, OpenStack Charmers Next Charms.
juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
dname/bcache2
unit-ceph-osd-0:
UnitId: ceph-osd/0
id: "5"
message: exit status 1
results:
ReturnCode: 1
Stderr: |
partx: /dev/disk/by-dname/bcache2: failed to read partition table
Failed to find physical volume "/dev/bcache1".
Failed to find physical volume "/dev/bcache1".
Device /dev/disk/by-dname/bcache2 not found.
Traceback (most recent call last):
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 79, in
request = add_device(request=request,
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 34, in add_device
charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
File "lib/charms_ceph/utils.py", line 1497, in osdize
osdize_dev(dev, osd_format, osd_journal,
File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
cmd = _ceph_volume(dev,
File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
cmd.append(_allocate_logical_volume(dev=dev,
File "lib/charms_ceph/utils.py", line 1965, in
_allocate_logical_volume
lvm.create_lvm_volume_group(vg_name, pv_dev)
File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in
create_lvm_volume_group
check_call(['vgcreate', volume_group, block_device])
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['vgcreate',
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']'
returned non-zero exit status 5.
Stdout: |2
Physical volume "/dev/disk/by-dname/bcache2" successfully created.
status: failed
timing:
completed: 2020-05-15 06:04:41 + UTC
enqueued: 2020-05-15 06:04:30 + UTC
started: 2020-05-15 06:04:39 + UTC
The same action on the /dev/bcacheX device succeeds - looks like some
sort of behaviour break in Ubuntu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878752] Re: vgcreate fails on /dev/disk/by-dname block devices
Removing the pv from the device also removes the by-dname entry
** Also affects: lvm2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1878752
Title:
vgcreate fails on /dev/disk/by-dname block devices
Status in OpenStack ceph-osd charm:
New
Status in lvm2 package in Ubuntu:
New
Bug description:
Ubuntu Focal, OpenStack Charmers Next Charms.
juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
dname/bcache2
unit-ceph-osd-0:
UnitId: ceph-osd/0
id: "5"
message: exit status 1
results:
ReturnCode: 1
Stderr: |
partx: /dev/disk/by-dname/bcache2: failed to read partition table
Failed to find physical volume "/dev/bcache1".
Failed to find physical volume "/dev/bcache1".
Device /dev/disk/by-dname/bcache2 not found.
Traceback (most recent call last):
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 79, in
request = add_device(request=request,
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 34, in add_device
charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
File "lib/charms_ceph/utils.py", line 1497, in osdize
osdize_dev(dev, osd_format, osd_journal,
File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
cmd = _ceph_volume(dev,
File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
cmd.append(_allocate_logical_volume(dev=dev,
File "lib/charms_ceph/utils.py", line 1965, in
_allocate_logical_volume
lvm.create_lvm_volume_group(vg_name, pv_dev)
File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in
create_lvm_volume_group
check_call(['vgcreate', volume_group, block_device])
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['vgcreate',
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']'
returned non-zero exit status 5.
Stdout: |2
Physical volume "/dev/disk/by-dname/bcache2" successfully created.
status: failed
timing:
completed: 2020-05-15 06:04:41 + UTC
enqueued: 2020-05-15 06:04:30 + UTC
started: 2020-05-15 06:04:39 + UTC
The same action on the /dev/bcacheX device succeeds - looks like some
sort of behaviour break in Ubuntu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870074] Re: python-glanceclient ftbfs in focal
Uploaded to focal for release team review.
Also submitted upstream - https://review.opendev.org/718093
** Changed in: python-glanceclient (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1870074
Title:
python-glanceclient ftbfs in focal
Status in openssl package in Ubuntu:
Invalid
Status in python-glanceclient package in Ubuntu:
Fix Committed
Bug description:
seen in the second focal test rebuild
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963677/+files/buildlog_ubuntu-focal-amd64.python-glanceclient_1%3A2.17.0-0ubuntu2_BUILDING.txt.gz
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
665, in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
376, in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
996, in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 352,
in connect
self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 383,
in ssl_wrap_socket
return context.wrap_socket(sock)
File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py",
line 491, in wrap_socket
raise ssl.SSLError("bad handshake: %r" % e)
ssl.SSLError: ("bad handshake: SysCallError(-1, 'Unexpected
EOF')",)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439,
in send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
719, in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 436,
in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError:
HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
handshake: SysCallError(-1, 'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/glanceclient/common/http.py", line 269, in
_request
resp = self.session.request(method,
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533,
in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646,
in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514,
in send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='0.0.0.0',
port=45175): Max retries exceeded with url: /v2/images/image123
(Caused by SSLError(SSLError("bad handshake: SysCallError(-1,
'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/glanceclient/tests/unit/test_ssl.py", line 124,
in test_v2_requests_cert_verification
gc.images.get('image123')
File "/<>/glanceclient/v2/images.py", line 198, in get
return self._get(image_id)
File "/<>/glanceclient/common/utils.py", line 598, in inner
return RequestIdProxy(wrapped(*args, **kwargs))
File "/<>/glanceclient/v2/images.py", line 191, in _get
resp, body = self.http_client.get(url, headers=header)
File "/<>/glanceclient/common/http.py", line 315, in get
return self._request('GET', url, **kwargs)
File "/<>/glanceclient/common/http.py", line 282, in
_request
raise exc.CommunicationError(message=message)
glanceclient.exc.CommunicationError: Error finding address for
https://0.0.0.0:45175/v2/images/image123:
HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
handshake: SysCallError(-1, 'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in
patched
return func(*args, **keywargs)
File "/<>/glanceclient/tests/unit/test_ssl.py", line 128,
in test_v2_requests_cert_verification
self.fail('No certificate failure message is received')
File "/usr/lib/python3/dist-pac
[Touch-packages] [Bug 1870074] Re: python-glanceclient ftbfs in focal
Actually this resolved to be due to use of older algs in the certs which
are no longer considered strong.
** Changed in: openssl (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1870074
Title:
python-glanceclient ftbfs in focal
Status in openssl package in Ubuntu:
Invalid
Status in python-glanceclient package in Ubuntu:
In Progress
Bug description:
seen in the second focal test rebuild
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963677/+files/buildlog_ubuntu-focal-amd64.python-glanceclient_1%3A2.17.0-0ubuntu2_BUILDING.txt.gz
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
665, in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
376, in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
996, in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 352,
in connect
self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 383,
in ssl_wrap_socket
return context.wrap_socket(sock)
File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py",
line 491, in wrap_socket
raise ssl.SSLError("bad handshake: %r" % e)
ssl.SSLError: ("bad handshake: SysCallError(-1, 'Unexpected
EOF')",)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439,
in send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
719, in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 436,
in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError:
HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
handshake: SysCallError(-1, 'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/glanceclient/common/http.py", line 269, in
_request
resp = self.session.request(method,
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533,
in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646,
in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514,
in send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='0.0.0.0',
port=45175): Max retries exceeded with url: /v2/images/image123
(Caused by SSLError(SSLError("bad handshake: SysCallError(-1,
'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/glanceclient/tests/unit/test_ssl.py", line 124,
in test_v2_requests_cert_verification
gc.images.get('image123')
File "/<>/glanceclient/v2/images.py", line 198, in get
return self._get(image_id)
File "/<>/glanceclient/common/utils.py", line 598, in inner
return RequestIdProxy(wrapped(*args, **kwargs))
File "/<>/glanceclient/v2/images.py", line 191, in _get
resp, body = self.http_client.get(url, headers=header)
File "/<>/glanceclient/common/http.py", line 315, in get
return self._request('GET', url, **kwargs)
File "/<>/glanceclient/common/http.py", line 282, in
_request
raise exc.CommunicationError(message=message)
glanceclient.exc.CommunicationError: Error finding address for
https://0.0.0.0:45175/v2/images/image123:
HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
handshake: SysCallError(-1, 'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in
patched
return func(*args, **keywargs)
File "/<>/glanceclient/tests/unit/test_ssl.py", line 128,
in test_v2_requests_cert_verification
self.fail('No certificate failure message is received')
File "/usr/lib/python3/dist-packages/unittest2/case.py",
[Touch-packages] [Bug 1870074] Re: python-glanceclient ftbfs in focal
Or this might be related to the default security level we set in Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1870074
Title:
python-glanceclient ftbfs in focal
Status in openssl package in Ubuntu:
New
Status in python-glanceclient package in Ubuntu:
In Progress
Bug description:
seen in the second focal test rebuild
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963677/+files/buildlog_ubuntu-focal-amd64.python-glanceclient_1%3A2.17.0-0ubuntu2_BUILDING.txt.gz
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
665, in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
376, in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
996, in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 352,
in connect
self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 383,
in ssl_wrap_socket
return context.wrap_socket(sock)
File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py",
line 491, in wrap_socket
raise ssl.SSLError("bad handshake: %r" % e)
ssl.SSLError: ("bad handshake: SysCallError(-1, 'Unexpected
EOF')",)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439,
in send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
719, in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 436,
in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError:
HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
handshake: SysCallError(-1, 'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/glanceclient/common/http.py", line 269, in
_request
resp = self.session.request(method,
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533,
in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646,
in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514,
in send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='0.0.0.0',
port=45175): Max retries exceeded with url: /v2/images/image123
(Caused by SSLError(SSLError("bad handshake: SysCallError(-1,
'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/glanceclient/tests/unit/test_ssl.py", line 124,
in test_v2_requests_cert_verification
gc.images.get('image123')
File "/<>/glanceclient/v2/images.py", line 198, in get
return self._get(image_id)
File "/<>/glanceclient/common/utils.py", line 598, in inner
return RequestIdProxy(wrapped(*args, **kwargs))
File "/<>/glanceclient/v2/images.py", line 191, in _get
resp, body = self.http_client.get(url, headers=header)
File "/<>/glanceclient/common/http.py", line 315, in get
return self._request('GET', url, **kwargs)
File "/<>/glanceclient/common/http.py", line 282, in
_request
raise exc.CommunicationError(message=message)
glanceclient.exc.CommunicationError: Error finding address for
https://0.0.0.0:45175/v2/images/image123:
HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
handshake: SysCallError(-1, 'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in
patched
return func(*args, **keywargs)
File "/<>/glanceclient/tests/unit/test_ssl.py", line 128,
in test_v2_requests_cert_verification
self.fail('No certificate failure message is received')
File "/usr/lib/python3/dist-packages/unittest2/case.py", line 690, in
fail
raise self.failureException(msg)
AssertionError: No certificate failu
[Touch-packages] [Bug 1870074] Re: python-glanceclient ftbfs in focal
and
https://github.com/openssl/openssl/issues/11378
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1870074
Title:
python-glanceclient ftbfs in focal
Status in openssl package in Ubuntu:
New
Status in python-glanceclient package in Ubuntu:
In Progress
Bug description:
seen in the second focal test rebuild
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963677/+files/buildlog_ubuntu-focal-amd64.python-glanceclient_1%3A2.17.0-0ubuntu2_BUILDING.txt.gz
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
665, in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
376, in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
996, in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 352,
in connect
self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 383,
in ssl_wrap_socket
return context.wrap_socket(sock)
File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py",
line 491, in wrap_socket
raise ssl.SSLError("bad handshake: %r" % e)
ssl.SSLError: ("bad handshake: SysCallError(-1, 'Unexpected
EOF')",)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439,
in send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
719, in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 436,
in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError:
HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
handshake: SysCallError(-1, 'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/glanceclient/common/http.py", line 269, in
_request
resp = self.session.request(method,
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533,
in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646,
in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514,
in send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='0.0.0.0',
port=45175): Max retries exceeded with url: /v2/images/image123
(Caused by SSLError(SSLError("bad handshake: SysCallError(-1,
'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/glanceclient/tests/unit/test_ssl.py", line 124,
in test_v2_requests_cert_verification
gc.images.get('image123')
File "/<>/glanceclient/v2/images.py", line 198, in get
return self._get(image_id)
File "/<>/glanceclient/common/utils.py", line 598, in inner
return RequestIdProxy(wrapped(*args, **kwargs))
File "/<>/glanceclient/v2/images.py", line 191, in _get
resp, body = self.http_client.get(url, headers=header)
File "/<>/glanceclient/common/http.py", line 315, in get
return self._request('GET', url, **kwargs)
File "/<>/glanceclient/common/http.py", line 282, in
_request
raise exc.CommunicationError(message=message)
glanceclient.exc.CommunicationError: Error finding address for
https://0.0.0.0:45175/v2/images/image123:
HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
handshake: SysCallError(-1, 'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in
patched
return func(*args, **keywargs)
File "/<>/glanceclient/tests/unit/test_ssl.py", line 128,
in test_v2_requests_cert_verification
self.fail('No certificate failure message is received')
File "/usr/lib/python3/dist-packages/unittest2/case.py", line 690, in
fail
raise self.failureException(msg)
AssertionError: No certificate failure message is recei
[Touch-packages] [Bug 1870074] Re: python-glanceclient ftbfs in focal
https://github.com/urllib3/urllib3/issues/1825
** Bug watch added: github.com/urllib3/urllib3/issues #1825
https://github.com/urllib3/urllib3/issues/1825
** Bug watch added: github.com/openssl/openssl/issues #11378
https://github.com/openssl/openssl/issues/11378
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1870074
Title:
python-glanceclient ftbfs in focal
Status in openssl package in Ubuntu:
New
Status in python-glanceclient package in Ubuntu:
In Progress
Bug description:
seen in the second focal test rebuild
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963677/+files/buildlog_ubuntu-focal-amd64.python-glanceclient_1%3A2.17.0-0ubuntu2_BUILDING.txt.gz
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
665, in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
376, in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
996, in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 352,
in connect
self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 383,
in ssl_wrap_socket
return context.wrap_socket(sock)
File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py",
line 491, in wrap_socket
raise ssl.SSLError("bad handshake: %r" % e)
ssl.SSLError: ("bad handshake: SysCallError(-1, 'Unexpected
EOF')",)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439,
in send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
719, in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 436,
in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError:
HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
handshake: SysCallError(-1, 'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/glanceclient/common/http.py", line 269, in
_request
resp = self.session.request(method,
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533,
in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646,
in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514,
in send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='0.0.0.0',
port=45175): Max retries exceeded with url: /v2/images/image123
(Caused by SSLError(SSLError("bad handshake: SysCallError(-1,
'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/glanceclient/tests/unit/test_ssl.py", line 124,
in test_v2_requests_cert_verification
gc.images.get('image123')
File "/<>/glanceclient/v2/images.py", line 198, in get
return self._get(image_id)
File "/<>/glanceclient/common/utils.py", line 598, in inner
return RequestIdProxy(wrapped(*args, **kwargs))
File "/<>/glanceclient/v2/images.py", line 191, in _get
resp, body = self.http_client.get(url, headers=header)
File "/<>/glanceclient/common/http.py", line 315, in get
return self._request('GET', url, **kwargs)
File "/<>/glanceclient/common/http.py", line 282, in
_request
raise exc.CommunicationError(message=message)
glanceclient.exc.CommunicationError: Error finding address for
https://0.0.0.0:45175/v2/images/image123:
HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
handshake: SysCallError(-1, 'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in
patched
return func(*args, **keywargs)
File "/<>/glanceclient/tests/unit/test_ssl.py", line 128,
in test_v2_requests_cert_verification
self.fail('No certificat
[Touch-packages] [Bug 1870074] Re: python-glanceclient ftbfs in focal
Boiling those down from the package build log:
glanceclient.tests.unit.test_ssl.TestHTTPSVerifyCert.test_v2_requests_valid_cert_no_key
OpenSSL.SSL.Error: [('SSL routines', 'SSL_CTX_use_certificate', 'ca md
too weak')]
glanceclient.tests.unit.test_ssl.TestHTTPSVerifyCert.test_v1_requests_cert_verification
OpenSSL.SSL.SysCallError: (104, 'ECONNRESET')
glanceclient.tests.unit.test_ssl.TestHTTPSVerifyCert.test_v2_requests_cert_verification_no_compression
glanceclient.tests.unit.test_ssl.TestHTTPSVerifyCert.test_v1_requests_cert_verification_no_compression
OpenSSL.SSL.SysCallError: (-1, 'Unexpected EOF')
glanceclient.tests.unit.test_ssl.TestHTTPSVerifyCert.test_v2_requests_cert_verification
OpenSSL.SSL.SysCallError: (-1, 'Unexpected EOF')
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1870074
Title:
python-glanceclient ftbfs in focal
Status in openssl package in Ubuntu:
New
Status in python-glanceclient package in Ubuntu:
In Progress
Bug description:
seen in the second focal test rebuild
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963677/+files/buildlog_ubuntu-focal-amd64.python-glanceclient_1%3A2.17.0-0ubuntu2_BUILDING.txt.gz
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
665, in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
376, in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
996, in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 352,
in connect
self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 383,
in ssl_wrap_socket
return context.wrap_socket(sock)
File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py",
line 491, in wrap_socket
raise ssl.SSLError("bad handshake: %r" % e)
ssl.SSLError: ("bad handshake: SysCallError(-1, 'Unexpected
EOF')",)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439,
in send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
719, in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 436,
in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError:
HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
handshake: SysCallError(-1, 'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/glanceclient/common/http.py", line 269, in
_request
resp = self.session.request(method,
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533,
in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646,
in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514,
in send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='0.0.0.0',
port=45175): Max retries exceeded with url: /v2/images/image123
(Caused by SSLError(SSLError("bad handshake: SysCallError(-1,
'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/glanceclient/tests/unit/test_ssl.py", line 124,
in test_v2_requests_cert_verification
gc.images.get('image123')
File "/<>/glanceclient/v2/images.py", line 198, in get
return self._get(image_id)
File "/<>/glanceclient/common/utils.py", line 598, in inner
return RequestIdProxy(wrapped(*args, **kwargs))
File "/<>/glanceclient/v2/images.py", line 191, in _get
resp, body = self.http_client.get(url, headers=header)
File "/<>/glanceclient/common/http.py", line 315, in get
return self._request('GET', url, **kwargs)
File "/<>/glanceclient/common/http.py", line 282, in
_request
raise exc.CommunicationError(message=message)
glanceclient.exc.CommunicationError: Error finding address for
https://0.0.0.0:45175/v2/images/image123:
HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
with url: /v2/
[Touch-packages] [Bug 1870074] Re: python-glanceclient ftbfs in focal
'ca md too weak' would indicate the signing alg is not good enough on
the ca.crt any longer:
Signature Algorithm: sha1WithRSAEncryption
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1870074
Title:
python-glanceclient ftbfs in focal
Status in openssl package in Ubuntu:
New
Status in python-glanceclient package in Ubuntu:
In Progress
Bug description:
seen in the second focal test rebuild
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963677/+files/buildlog_ubuntu-focal-amd64.python-glanceclient_1%3A2.17.0-0ubuntu2_BUILDING.txt.gz
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
665, in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
376, in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
996, in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 352,
in connect
self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 383,
in ssl_wrap_socket
return context.wrap_socket(sock)
File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py",
line 491, in wrap_socket
raise ssl.SSLError("bad handshake: %r" % e)
ssl.SSLError: ("bad handshake: SysCallError(-1, 'Unexpected
EOF')",)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439,
in send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
719, in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 436,
in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError:
HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
handshake: SysCallError(-1, 'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/glanceclient/common/http.py", line 269, in
_request
resp = self.session.request(method,
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533,
in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646,
in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514,
in send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='0.0.0.0',
port=45175): Max retries exceeded with url: /v2/images/image123
(Caused by SSLError(SSLError("bad handshake: SysCallError(-1,
'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/glanceclient/tests/unit/test_ssl.py", line 124,
in test_v2_requests_cert_verification
gc.images.get('image123')
File "/<>/glanceclient/v2/images.py", line 198, in get
return self._get(image_id)
File "/<>/glanceclient/common/utils.py", line 598, in inner
return RequestIdProxy(wrapped(*args, **kwargs))
File "/<>/glanceclient/v2/images.py", line 191, in _get
resp, body = self.http_client.get(url, headers=header)
File "/<>/glanceclient/common/http.py", line 315, in get
return self._request('GET', url, **kwargs)
File "/<>/glanceclient/common/http.py", line 282, in
_request
raise exc.CommunicationError(message=message)
glanceclient.exc.CommunicationError: Error finding address for
https://0.0.0.0:45175/v2/images/image123:
HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
handshake: SysCallError(-1, 'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in
patched
return func(*args, **keywargs)
File "/<>/glanceclient/tests/unit/test_ssl.py", line 128,
in test_v2_requests_cert_verification
self.fail('No certificate failure message is received')
File "/usr/lib/python3/dist-packages/unittest2/case.py", line 690, in
fail
raise self.
[Touch-packages] [Bug 1870074] Re: python-glanceclient ftbfs in focal
glanceclient.tests.unit.test_ssl.TestHTTPSVerifyCert.test_v2_requests_valid_cert_no_key
glanceclient.exc.CommunicationError: SSL Error communicating with
https://0.0.0.0:58534/v2/images/image123: [('SSL routines',
'SSL_CTX_use_certificate', 'ca md too weak')]
** Also affects: openssl (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1870074
Title:
python-glanceclient ftbfs in focal
Status in openssl package in Ubuntu:
New
Status in python-glanceclient package in Ubuntu:
In Progress
Bug description:
seen in the second focal test rebuild
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963677/+files/buildlog_ubuntu-focal-amd64.python-glanceclient_1%3A2.17.0-0ubuntu2_BUILDING.txt.gz
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
665, in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
376, in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
996, in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 352,
in connect
self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 383,
in ssl_wrap_socket
return context.wrap_socket(sock)
File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py",
line 491, in wrap_socket
raise ssl.SSLError("bad handshake: %r" % e)
ssl.SSLError: ("bad handshake: SysCallError(-1, 'Unexpected
EOF')",)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439,
in send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line
719, in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 436,
in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError:
HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
handshake: SysCallError(-1, 'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/glanceclient/common/http.py", line 269, in
_request
resp = self.session.request(method,
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533,
in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646,
in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514,
in send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='0.0.0.0',
port=45175): Max retries exceeded with url: /v2/images/image123
(Caused by SSLError(SSLError("bad handshake: SysCallError(-1,
'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/glanceclient/tests/unit/test_ssl.py", line 124,
in test_v2_requests_cert_verification
gc.images.get('image123')
File "/<>/glanceclient/v2/images.py", line 198, in get
return self._get(image_id)
File "/<>/glanceclient/common/utils.py", line 598, in inner
return RequestIdProxy(wrapped(*args, **kwargs))
File "/<>/glanceclient/v2/images.py", line 191, in _get
resp, body = self.http_client.get(url, headers=header)
File "/<>/glanceclient/common/http.py", line 315, in get
return self._request('GET', url, **kwargs)
File "/<>/glanceclient/common/http.py", line 282, in
_request
raise exc.CommunicationError(message=message)
glanceclient.exc.CommunicationError: Error finding address for
https://0.0.0.0:45175/v2/images/image123:
HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
handshake: SysCallError(-1, 'Unexpected EOF')")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in
patched
return func(*args, **keywargs)
File "/<>/glanceclient/tests/unit/test_ssl.py", line 128,
[Touch-packages] [Bug 1849856] Re: ip commands error with mellanox devices in switchdev mode
FWIW same is seem with the 5.3.0 kernel that's just appeared in HWE edge. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1849856 Title: ip commands error with mellanox devices in switchdev mode Status in iproute2 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Kernel: using 5.0.0-23-generic from hwe-edge Configuring a mellanox connectx device with configured VF's into switchdev (rather than legacy) mode result in the ip cli tool erroring when trying to query the interface state: $ sudo ip link Error: Buffer too small for object. Dump terminated ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Fri Oct 25 14:55:36 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849856] Re: ip commands error with mellanox devices in switchdev mode
@terrykrudd - I think there is a bug here somewhere as the card should support 127 VF's (and 1 PF) per port - setting the firmware to this limit results in this error. I'm not sure whether this problem is in the kernel driver code or in the underlying firmware. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1849856 Title: ip commands error with mellanox devices in switchdev mode Status in iproute2 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Kernel: using 5.0.0-23-generic from hwe-edge Configuring a mellanox connectx device with configured VF's into switchdev (rather than legacy) mode result in the ip cli tool erroring when trying to query the interface state: $ sudo ip link Error: Buffer too small for object. Dump terminated ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Fri Oct 25 14:55:36 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849856] Re: ip commands error with mellanox devices in switchdev mode
Managed to figure out why this was happening - I had the NUM_VFS in the card firmware configured to 127 (the maximum value) - reducing this to a lower number allowed me to successfully switch the cards into switchdev mode at which point the ip tools all worked again. The clue that pointed to this appeared when using the proposed 5.3 hwe edge kernel: [ 694.027106] infiniband (null): mlx5_ib_alloc_counters:5452:(pid 47479): couldn't allocate queue counter for port 128, err -12 (128 being the pertinent value) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1849856 Title: ip commands error with mellanox devices in switchdev mode Status in iproute2 package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Kernel: using 5.0.0-23-generic from hwe-edge Configuring a mellanox connectx device with configured VF's into switchdev (rather than legacy) mode result in the ip cli tool erroring when trying to query the interface state: $ sudo ip link Error: Buffer too small for object. Dump terminated ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Fri Oct 25 14:55:36 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849856] Re: ip commands error with mellanox devices in switchdev mode
strace from failing command ** Attachment added: "strace-iplink.txt" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+attachment/5300860/+files/strace-iplink.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1849856 Title: ip commands error with mellanox devices in switchdev mode Status in iproute2 package in Ubuntu: New Bug description: Kernel: using 5.0.0-23-generic from hwe-edge Configuring a mellanox connectx device with configured VF's into switchdev (rather than legacy) mode result in the ip cli tool erroring when trying to query the interface state: $ sudo ip link Error: Buffer too small for object. Dump terminated ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Fri Oct 25 14:55:36 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849856] Re: ip commands error with mellanox devices in switchdev mode
Also tried with the iproute2 in bionic-backports - same result -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1849856 Title: ip commands error with mellanox devices in switchdev mode Status in iproute2 package in Ubuntu: New Bug description: Kernel: using 5.0.0-23-generic from hwe-edge Configuring a mellanox connectx device with configured VF's into switchdev (rather than legacy) mode result in the ip cli tool erroring when trying to query the interface state: $ sudo ip link Error: Buffer too small for object. Dump terminated ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Fri Oct 25 14:55:36 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849856] [NEW] ip commands error with mellanox devices in switchdev mode
Public bug reported: Kernel: using 5.0.0-23-generic from hwe-edge Configuring a mellanox connectx device with configured VF's into switchdev (rather than legacy) mode result in the ip cli tool erroring when trying to query the interface state: $ sudo ip link Error: Buffer too small for object. Dump terminated ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Fri Oct 25 14:55:36 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1849856 Title: ip commands error with mellanox devices in switchdev mode Status in iproute2 package in Ubuntu: New Bug description: Kernel: using 5.0.0-23-generic from hwe-edge Configuring a mellanox connectx device with configured VF's into switchdev (rather than legacy) mode result in the ip cli tool erroring when trying to query the interface state: $ sudo ip link Error: Buffer too small for object. Dump terminated ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Fri Oct 25 14:55:36 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828617] Re: Hosts randomly 'losing' disks, breaking ceph-osd service enumeration
Please can you confirm which version of the ceph-osd package you have installed; older versions rely on a charm shipped udev ruleset, rather than it being provided by the packaging. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1828617 Title: Hosts randomly 'losing' disks, breaking ceph-osd service enumeration Status in systemd package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.2 Ceph deployment. Ceph OSD devices utilizing LVM volumes pointing to udev-based physical devices. LVM module is supposed to create PVs from devices using the links in /dev/disk/by-dname/ folder that are created by udev. However on reboot it happens (not always, rather like race condition) that Ceph services cannot start, and pvdisplay doesn't show any volumes created. The folder /dev/disk/by-dname/ however has all necessary device created by the end of boot process. The behaviour can be fixed manually by running "#/sbin/lvm pvscan --cache --activate ay /dev/nvme0n1" command for re-activating the LVM components and then the services can be started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828617/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828617] Re: Hosts randomly 'losing' disks, breaking ceph-osd service enumeration
The ceph-osd package provide udev rules which should switch the owner
for all ceph related LVM VG's to ceph:ceph.
# OSD LVM layout example
# VG prefix: ceph-
# LV prefix: osd-
ACTION=="add", SUBSYSTEM=="block", \
ENV{DEVTYPE}=="disk", \
ENV{DM_LV_NAME}=="osd-*", \
ENV{DM_VG_NAME}=="ceph-*", \
OWNER:="ceph", GROUP:="ceph", MODE:="660"
ACTION=="change", SUBSYSTEM=="block", \
ENV{DEVTYPE}=="disk", \
ENV{DM_LV_NAME}=="osd-*", \
ENV{DM_VG_NAME}=="ceph-*", \
OWNER="ceph", GROUP="ceph", MODE="660"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1828617
Title:
Hosts randomly 'losing' disks, breaking ceph-osd service enumeration
Status in systemd package in Ubuntu:
Incomplete
Bug description:
Ubuntu 18.04.2 Ceph deployment.
Ceph OSD devices utilizing LVM volumes pointing to udev-based physical
devices.
LVM module is supposed to create PVs from devices using the links in
/dev/disk/by-dname/ folder that are created by udev.
However on reboot it happens (not always, rather like race condition) that
Ceph services cannot start, and pvdisplay doesn't show any volumes created. The
folder /dev/disk/by-dname/ however has all necessary device created by the end
of boot process.
The behaviour can be fixed manually by running "#/sbin/lvm pvscan
--cache --activate ay /dev/nvme0n1" command for re-activating the LVM
components and then the services can be started.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828617/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828617] Re: Hosts randomly 'losing' disks, breaking ceph-osd service enumeration
by-dname udev rules are created by MAAS/curtin as part of the server install I think. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1828617 Title: Hosts randomly 'losing' disks, breaking ceph-osd service enumeration Status in systemd package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.2 Ceph deployment. Ceph OSD devices utilizing LVM volumes pointing to udev-based physical devices. LVM module is supposed to create PVs from devices using the links in /dev/disk/by-dname/ folder that are created by udev. However on reboot it happens (not always, rather like race condition) that Ceph services cannot start, and pvdisplay doesn't show any volumes created. The folder /dev/disk/by-dname/ however has all necessary device created by the end of boot process. The behaviour can be fixed manually by running "#/sbin/lvm pvscan --cache --activate ay /dev/nvme0n1" command for re-activating the LVM components and then the services can be started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828617/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823862] Re: disco: unable to use iptables/enable ufw under -virtual kernel
Tested with the kernel+modules linked in #22 I can confirm I was able to enable ufw and query the installed iptables rules: $ uname -a Linux juju-0f0cbd-disco-testing-38 5.0.0-10-generic #11+lp1823862v201904100938 SMP Wed Apr 10 14:40:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y Firewall is active and enabled on system startup $ sudo iptables-save # Generated by iptables-save v1.6.1 on Wed Apr 10 16:15:01 2019 *filter :INPUT DROP [0:0] :FORWARD DROP [0:0] :OUTPUT ACCEPT [0:0] :ufw-after-forward - [0:0] :ufw-after-input - [0:0] :ufw-after-logging-forward - [0:0] :ufw-after-logging-input - [0:0] :ufw-after-logging-output - [0:0] :ufw-after-output - [0:0] :ufw-before-forward - [0:0] :ufw-before-input - [0:0] :ufw-before-logging-forward - [0:0] :ufw-before-logging-input - [0:0] :ufw-before-logging-output - [0:0] :ufw-before-output - [0:0] :ufw-logging-allow - [0:0] :ufw-logging-deny - [0:0] :ufw-not-local - [0:0] :ufw-reject-forward - [0:0] :ufw-reject-input - [0:0] :ufw-reject-output - [0:0] :ufw-skip-to-policy-forward - [0:0] :ufw-skip-to-policy-input - [0:0] :ufw-skip-to-policy-output - [0:0] :ufw-track-forward - [0:0] :ufw-track-input - [0:0] :ufw-track-output - [0:0] :ufw-user-forward - [0:0] :ufw-user-input - [0:0] :ufw-user-limit - [0:0] :ufw-user-limit-accept - [0:0] :ufw-user-logging-forward - [0:0] :ufw-user-logging-input - [0:0] :ufw-user-logging-output - [0:0] :ufw-user-output - [0:0] -A INPUT -j ufw-before-logging-input -A INPUT -j ufw-before-input -A INPUT -j ufw-after-input -A INPUT -j ufw-after-logging-input -A INPUT -j ufw-reject-input -A INPUT -j ufw-track-input -A FORWARD -j ufw-before-logging-forward -A FORWARD -j ufw-before-forward -A FORWARD -j ufw-after-forward -A FORWARD -j ufw-after-logging-forward -A FORWARD -j ufw-reject-forward -A FORWARD -j ufw-track-forward -A OUTPUT -j ufw-before-logging-output -A OUTPUT -j ufw-before-output -A OUTPUT -j ufw-after-output -A OUTPUT -j ufw-after-logging-output -A OUTPUT -j ufw-reject-output -A OUTPUT -j ufw-track-output -A ufw-after-input -p udp -m udp --dport 137 -j ufw-skip-to-policy-input -A ufw-after-input -p udp -m udp --dport 138 -j ufw-skip-to-policy-input -A ufw-after-input -p tcp -m tcp --dport 139 -j ufw-skip-to-policy-input -A ufw-after-input -p tcp -m tcp --dport 445 -j ufw-skip-to-policy-input -A ufw-after-input -p udp -m udp --dport 67 -j ufw-skip-to-policy-input -A ufw-after-input -p udp -m udp --dport 68 -j ufw-skip-to-policy-input -A ufw-after-input -m addrtype --dst-type BROADCAST -j ufw-skip-to-policy-input -A ufw-after-logging-forward -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix "[UFW BLOCK] " -A ufw-after-logging-input -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix "[UFW BLOCK] " -A ufw-before-forward -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A ufw-before-forward -p icmp -m icmp --icmp-type 3 -j ACCEPT -A ufw-before-forward -p icmp -m icmp --icmp-type 11 -j ACCEPT -A ufw-before-forward -p icmp -m icmp --icmp-type 12 -j ACCEPT -A ufw-before-forward -p icmp -m icmp --icmp-type 8 -j ACCEPT -A ufw-before-forward -j ufw-user-forward -A ufw-before-input -i lo -j ACCEPT -A ufw-before-input -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A ufw-before-input -m conntrack --ctstate INVALID -j ufw-logging-deny -A ufw-before-input -m conntrack --ctstate INVALID -j DROP -A ufw-before-input -p icmp -m icmp --icmp-type 3 -j ACCEPT -A ufw-before-input -p icmp -m icmp --icmp-type 11 -j ACCEPT -A ufw-before-input -p icmp -m icmp --icmp-type 12 -j ACCEPT -A ufw-before-input -p icmp -m icmp --icmp-type 8 -j ACCEPT -A ufw-before-input -p udp -m udp --sport 67 --dport 68 -j ACCEPT -A ufw-before-input -j ufw-not-local -A ufw-before-input -d 224.0.0.251/32 -p udp -m udp --dport 5353 -j ACCEPT -A ufw-before-input -d 239.255.255.250/32 -p udp -m udp --dport 1900 -j ACCEPT -A ufw-before-input -j ufw-user-input -A ufw-before-output -o lo -j ACCEPT -A ufw-before-output -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A ufw-before-output -j ufw-user-output -A ufw-logging-allow -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix "[UFW ALLOW] " -A ufw-logging-deny -m conntrack --ctstate INVALID -m limit --limit 3/min --limit-burst 10 -j RETURN -A ufw-logging-deny -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix "[UFW BLOCK] " -A ufw-not-local -m addrtype --dst-type LOCAL -j RETURN -A ufw-not-local -m addrtype --dst-type MULTICAST -j RETURN -A ufw-not-local -m addrtype --dst-type BROADCAST -j RETURN -A ufw-not-local -m limit --limit 3/min --limit-burst 10 -j ufw-logging-deny -A ufw-not-local -j DROP -A ufw-skip-to-policy-forward -j DROP -A ufw-skip-to-policy-input -j DROP -A ufw-skip-to-policy-output -j ACCEPT -A ufw-track-output -p tcp -m conntrack --ctstate NEW -j ACCEPT -A ufw-track-output -p udp -m conntrack --ctstate NEW -j ACCEPT -A ufw-user-limit -m limit --limit 3/min -j LOG --log-p
[Touch-packages] [Bug 1823862] Re: disco: unable to enable ufw under -virtual kernel
This might have some implications for fan usage on cloud instances as I see some fan-* rules post switch to generic kernel. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1823862 Title: disco: unable to enable ufw under -virtual kernel Status in linux package in Ubuntu: Incomplete Status in ufw package in Ubuntu: New Bug description: Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823862] Re: disco: unable to enable ufw under -virtual kernel
Dropping ufw from the test case - just running sudo iptables-save against the virtual kernel produces no output. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1823862 Title: disco: unable to enable ufw under -virtual kernel Status in linux package in Ubuntu: Incomplete Status in ufw package in Ubuntu: New Bug description: Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823862] Re: disco: unable to enable ufw under -virtual kernel
Diff between two identical instances, one with -generic and one with -virtual. iptables* commands working find with -generic. ** Attachment added: "kernel-diff.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862/+attachment/5254621/+files/kernel-diff.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1823862 Title: disco: unable to enable ufw under -virtual kernel Status in linux package in Ubuntu: Incomplete Status in ufw package in Ubuntu: New Bug description: Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823862] Re: disco: unable to enable ufw
OK I think I've figured it out; the cloud images use the -virtual kernel, which does not install linux-modules-extra-*. If I install the -generic kernel or just the extra modules and reboot, then iptables commands start working again. ** Changed in: ufw (Ubuntu) Status: Incomplete => New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - disco: unable to enable ufw + disco: unable to enable ufw under -virtual kernel -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1823862 Title: disco: unable to enable ufw under -virtual kernel Status in linux package in Ubuntu: New Status in ufw package in Ubuntu: New Bug description: Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823862] Re: disco: unable to enable ufw
main diff there is py2.7 vs py3 (but that's cause swift still uses python2) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1823862 Title: disco: unable to enable ufw Status in ufw package in Ubuntu: Incomplete Bug description: Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823862] Re: disco: unable to enable ufw
I also tested on a pristine machine: $ sudo /usr/share/ufw/check-requirements Has python: pass (binary: python3.7, version: 3.7.3, py3) Has iptables: pass Has ip6tables: pass Has /proc/net/dev: pass Has /proc/net/if_inet6: pass This script will now attempt to create various rules using the iptables and ip6tables commands. This may result in module autoloading (eg, for IPv6). Proceed with checks (Y/n)? yes == IPv4 == Creating 'ufw-check-requirements'... done Inserting RETURN at top of 'ufw-check-requirements'... iptables: No chain/target/match by that name. ERROR: could insert RETURN rule into 'ufw-check-requirements'. Aborting FAIL: check your kernel and that you have iptables >= 1.4.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1823862 Title: disco: unable to enable ufw Status in ufw package in Ubuntu: Incomplete Bug description: Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823862] Re: disco: unable to enable ufw
check-requirements from failing swift unit: $ sudo /usr/share/ufw/check-requirements Has python: pass (binary: python2.7, version: 2.7.16, py2) Has iptables: pass Has ip6tables: pass Has /proc/net/dev: pass Has /proc/net/if_inet6: pass This script will now attempt to create various rules using the iptables and ip6tables commands. This may result in module autoloading (eg, for IPv6). Proceed with checks (Y/n)? y == IPv4 == Creating 'ufw-check-requirements'... done Inserting RETURN at top of 'ufw-check-requirements'... iptables: No chain/target/match by that name. ERROR: could insert RETURN rule into 'ufw-check-requirements'. Aborting FAIL: check your kernel and that you have iptables >= 1.4.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1823862 Title: disco: unable to enable ufw Status in ufw package in Ubuntu: Incomplete Bug description: Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823862] Re: disco: unable to enable ufw
I can only think this is something cloud-image specific. FTR the policy is initially configured wide open (as the server may be doing a number of other things the charm deploying does not know about) and then the ports for swift/rsync are restricted to peers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1823862 Title: disco: unable to enable ufw Status in ufw package in Ubuntu: Incomplete Bug description: Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823862] Re: disco: unable to enable ufw
this translates into:
ufw default allow incoming
ufw default allow outgoing
ufw default allow routed
ufw allow rsync
ufw allow ssh
ufw enable
which gets us to the:
ufw.enable(soft_fail=config('allow-ufw-ip6-softfail'))
which is where the failure to enable occurs.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1823862
Title:
disco: unable to enable ufw
Status in ufw package in Ubuntu:
Incomplete
Bug description:
Fresh install of disco:
$ sudo ufw enable
Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
ERROR: problem running ufw-init
iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad
built-in chain name
iptables-restore: line 22 failed
iptables-restore: line 2 failed
iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file
or directory
Error occurred at line: 30
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No
such file or directory
Error occurred at line: 19
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file
or directory
Error occurred at line: 2
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
Problem running '/etc/ufw/before.rules'
Problem running '/etc/ufw/after.rules'
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ufw 0.36-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu26
Architecture: amd64
Date: Tue Apr 9 08:49:59 2019
Ec2AMI: ami-04cf
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.blue
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ufw
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1823862/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823862] Re: disco: unable to enable ufw
OK so there is a little modification of the policy prior to enablement:
def initialize_ufw():
"""Initialize the UFW firewall
Ensure critical ports have explicit allows
:return: None
"""
if not config('enable-firewall'):
log("Firewall has been administratively disabled", "DEBUG")
return
# this charm will monitor exclusively the ports used, using 'allow' as
# default policy enables sharing the machine with other services
ufw.default_policy('allow', 'incoming')
ufw.default_policy('allow', 'outgoing')
ufw.default_policy('allow', 'routed')
# Rsync manages its own ACLs
ufw.service('rsync', 'open')
# Guarantee SSH access
ufw.service('ssh', 'open')
# Enable
ufw.enable(soft_fail=config('allow-ufw-ip6-softfail'))
# Allow GRE traffic
add_ufw_gre_rule(os.path.join(UFW_DIR, 'before.rules'))
ufw.reload()
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1823862
Title:
disco: unable to enable ufw
Status in ufw package in Ubuntu:
Incomplete
Bug description:
Fresh install of disco:
$ sudo ufw enable
Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
ERROR: problem running ufw-init
iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad
built-in chain name
iptables-restore: line 22 failed
iptables-restore: line 2 failed
iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file
or directory
Error occurred at line: 30
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No
such file or directory
Error occurred at line: 19
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file
or directory
Error occurred at line: 2
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
Problem running '/etc/ufw/before.rules'
Problem running '/etc/ufw/after.rules'
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ufw 0.36-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu26
Architecture: amd64
Date: Tue Apr 9 08:49:59 2019
Ec2AMI: ami-04cf
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.blue
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ufw
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1823862/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823862] Re: disco: unable to enable ufw
I'm trying to figure out what is modifying /etc/default/ufw - the swift- storage charm does but it just disables IPv6 in some situations. I reported this from a different cloud instance - so probably worth mentioning that this is a disco image running on openstack from the daily image stream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1823862 Title: disco: unable to enable ufw Status in ufw package in Ubuntu: Incomplete Bug description: Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823862] [NEW] disco: unable to enable ufw
Public bug reported: Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 ** Affects: ufw (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ec2-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1823862 Title: disco: unable to enable ufw Status in ufw package in Ubuntu: New Bug description: Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806012] Re: set-cpufreq: 'powersave' governor configuration sanity on ubuntu server
TBH it was probably whatever the default mode was in the BIOS - we saw the same issue on Dell and HP servers. This one >> "You mean that you let systemd ondemand service do whatever it does by default" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1806012 Title: set-cpufreq: 'powersave' governor configuration sanity on ubuntu server Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Bug description: Whilst debugging 'slow instance performance' on a Ubuntu Bionic based cloud, I observed that the default cpu governor configuration was set to 'powersave'; toggling this to 'performance' (while in not anyway a particularly green thing todo) resulted in the instance slowness disappearing and the cloud performance being as expected (based on a prior version of the deploy on Ubuntu Xenial). AFAICT Xenial does the same thing albeit in a slight different way, but we definitely did not see the same performance laggy-ness under a Xenial based cloud. Raising against systemd (as this package sets the governor to 'powersave') - I feel that the switch to 'performance' although appropriate then obscures what might be a performance/behavioural difference in the underlying kernel when a machine is under load. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.9 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Nov 30 10:05:46 2018 Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=UUID=a361a524-47eb-46c3-8a04-e5eaa65188c9 ro hugepages=103117 iommu=pt intel_iommu=on SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1806012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806012] Re: set-cpufreq: 'powersave' governor configuration sanity on ubuntu server
Just to add some more detail to this bug; for the impacted deployment we actually ended up re-configuring the power regulator settings via the BIOS to delegate to the OS for control; after a reboot we've just stuck with the default ondemand behaviour and performance has been consistent/better than before. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1806012 Title: set-cpufreq: 'powersave' governor configuration sanity on ubuntu server Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Bug description: Whilst debugging 'slow instance performance' on a Ubuntu Bionic based cloud, I observed that the default cpu governor configuration was set to 'powersave'; toggling this to 'performance' (while in not anyway a particularly green thing todo) resulted in the instance slowness disappearing and the cloud performance being as expected (based on a prior version of the deploy on Ubuntu Xenial). AFAICT Xenial does the same thing albeit in a slight different way, but we definitely did not see the same performance laggy-ness under a Xenial based cloud. Raising against systemd (as this package sets the governor to 'powersave') - I feel that the switch to 'performance' although appropriate then obscures what might be a performance/behavioural difference in the underlying kernel when a machine is under load. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.9 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Nov 30 10:05:46 2018 Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=UUID=a361a524-47eb-46c3-8a04-e5eaa65188c9 ro hugepages=103117 iommu=pt intel_iommu=on SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1806012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806012] [NEW] set-cpufreq: 'powersave' governor configuration sanity on ubuntu server
Public bug reported: Whilst debugging 'slow instance performance' on a Ubuntu Bionic based cloud, I observed that the default cpu governor configuration was set to 'powersave'; toggling this to 'performance' (while in not anyway a particularly green thing todo) resulted in the instance slowness disappearing and the cloud performance being as expected (based on a prior version of the deploy on Ubuntu Xenial). AFAICT Xenial does the same thing albeit in a slight different way, but we definitely did not see the same performance laggy-ness under a Xenial based cloud. Raising against systemd (as this package sets the governor to 'powersave') - I feel that the switch to 'performance' although appropriate then obscures what might be a performance/behavioural difference in the underlying kernel when a machine is under load. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.9 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Nov 30 10:05:46 2018 Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=UUID=a361a524-47eb-46c3-8a04-e5eaa65188c9 ro hugepages=103117 iommu=pt intel_iommu=on SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1806012 Title: set-cpufreq: 'powersave' governor configuration sanity on ubuntu server Status in systemd package in Ubuntu: New Bug description: Whilst debugging 'slow instance performance' on a Ubuntu Bionic based cloud, I observed that the default cpu governor configuration was set to 'powersave'; toggling this to 'performance' (while in not anyway a particularly green thing todo) resulted in the instance slowness disappearing and the cloud performance being as expected (based on a prior version of the deploy on Ubuntu Xenial). AFAICT Xenial does the same thing albeit in a slight different way, but we definitely did not see the same performance laggy-ness under a Xenial based cloud. Raising against systemd (as this package sets the governor to 'powersave') - I feel that the switch to 'performance' although appropriate then obscures what might be a performance/behavioural difference in the underlying kernel when a machine is under load. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.9 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Nov 30 10:05:46 2018 Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=UUID=a361a524-47eb-46c3-8a04-e5eaa65188c9 ro hugepages=103117 iommu=pt intel_iommu=on SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1806012/+subscriptions -- Mailing list: https://launchpad.net/~
[Touch-packages] [Bug 1794229] Re: python packages should not ship colliding /usr/lib/python3/dist-packages/.pytest_cache
** Bug watch added: Debian Bug tracker #909529 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909529 ** Also affects: alembic (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909529 Importance: Unknown Status: Unknown ** Changed in: alembic (Ubuntu) Status: New => Fix Committed ** Changed in: alembic (Ubuntu) Assignee: (unassigned) => James Page (james-page) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1794229 Title: python packages should not ship colliding /usr/lib/python3/dist- packages/.pytest_cache Status in alembic package in Ubuntu: Fix Committed Status in astroid package in Ubuntu: Invalid Status in dh-python package in Ubuntu: New Status in Debian: Fix Released Status in alembic package in Debian: Unknown Bug description: Python packages should not ship /usr/lib/python3/dist- packages/.pytest_cache Recently, two packages python3-alembic and python3-astroid both shipped these files which collided on package install dh-python has been improved upstream to stream all hidden "dot" directories in Debian #907871 This change should be imported and both alembic and astroid should be rebuilt (plus any other packages shipping this file) Preparing to unpack .../178-python3-astroid_2.0.4-1_all.deb ... Unpacking python3-astroid (2.0.4-1) over (1.6.5-1ubuntu4) ... dpkg: error processing archive /tmp/apt-dpkg-install-rbF4wE/178-python3-astroid_2.0.4-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/.pytest_cache/v/cache/nodeids', which is also in package python3-alembic 1.0.0-1ubuntu1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alembic/+bug/1794229/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780332] Re: vaultlocker does not ensure that udev is triggered to create /dev/disk/by-uuid/ symlink and fails
@xnox
as dmitriis state's we've worked around this issue in vaultlocker;
however I do think that fixing this more generally would be a nice
broader ecosystem step - fixing and underlying race rather than papering
over it in tooling high up the stack is always more preferable.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1780332
Title:
vaultlocker does not ensure that udev is triggered to create /dev/disk
/by-uuid/ symlink and fails
Status in vaultlocker:
Fix Released
Status in cryptsetup package in Ubuntu:
New
Status in lvm2 package in Ubuntu:
New
Status in systemd package in Ubuntu:
Incomplete
Bug description:
When an encrypted device is setup up a UUID (osd_fsid) is passed from
the charm to be used in the cryptsetup command which accepts a UUID to
place into the LUKS header (shown in cryptsetup luksDump ).
https://github.com/openstack/charm-ceph-osd/blob/stable/18.05/lib/ceph/utils.py#L1788-L1804
UUID comes from osd_fsid
https://github.com/openstack-charmers/vaultlocker/blob/8c9cb85dc3ed5dbf18c66a810d189a5230d85c34/vaultlocker/shell.py#L69-L80
# else statement is used here
block_uuid = str(uuid.uuid4()) if not args.uuid else args.uuid
dmcrypt.luks_format(key, block_device, block_uuid) # creates a LUKS
header
# ...
dmcrypt.luks_open(key, block_uuid) # sets up a device with device mapper
decrypting it via dmcrypt
https://github.com/openstack-
charmers/vaultlocker/blob/d813233179bdf2eec8ed101c702a8e552a966f44/vaultlocker/dmcrypt.py#L44-L56
This UUID is visible in blkid output
/dev/sdc: UUID="" TYPE="crypto_LUKS"
and a udev rule exists to create a /dev/disk/by-uuid/ symlink (which is normally used for filesystem -> block device
resolution)
https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in#n25
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*",
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"
Where vaultlocker fails is in luks_open command (right after luks_format)
# cryptsetup --batch-mode --key-file - open UUID=
crypt- --type luks
because it tries to access /dev/disk/by-uuid/ which
does not exist.
This happens since udev rules are not re-triggered to create this
symlink after a LUKS device is created.
Solution: call the command below after luks_format before luks_open
udevadm settle --exit-if-exists=/dev/disk/by-uuid/
To manage notifications about this bug go to:
https://bugs.launchpad.net/vaultlocker/+bug/1780332/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780332] Re: vaultlocker does not ensure that udev is triggered to create /dev/disk/by-uuid/ symlink and fails
tl;dr you don't need vaultlocker to reproduce this issue :-)
** Changed in: cryptsetup (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1780332
Title:
vaultlocker does not ensure that udev is triggered to create /dev/disk
/by-uuid/ symlink and fails
Status in vaultlocker:
Fix Released
Status in cryptsetup package in Ubuntu:
New
Status in systemd package in Ubuntu:
Incomplete
Bug description:
When an encrypted device is setup up a UUID (osd_fsid) is passed from
the charm to be used in the cryptsetup command which accepts a UUID to
place into the LUKS header (shown in cryptsetup luksDump ).
https://github.com/openstack/charm-ceph-osd/blob/stable/18.05/lib/ceph/utils.py#L1788-L1804
UUID comes from osd_fsid
https://github.com/openstack-charmers/vaultlocker/blob/8c9cb85dc3ed5dbf18c66a810d189a5230d85c34/vaultlocker/shell.py#L69-L80
# else statement is used here
block_uuid = str(uuid.uuid4()) if not args.uuid else args.uuid
dmcrypt.luks_format(key, block_device, block_uuid) # creates a LUKS
header
# ...
dmcrypt.luks_open(key, block_uuid) # sets up a device with device mapper
decrypting it via dmcrypt
https://github.com/openstack-
charmers/vaultlocker/blob/d813233179bdf2eec8ed101c702a8e552a966f44/vaultlocker/dmcrypt.py#L44-L56
This UUID is visible in blkid output
/dev/sdc: UUID="" TYPE="crypto_LUKS"
and a udev rule exists to create a /dev/disk/by-uuid/ symlink (which is normally used for filesystem -> block device
resolution)
https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in#n25
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*",
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"
Where vaultlocker fails is in luks_open command (right after luks_format)
# cryptsetup --batch-mode --key-file - open UUID=
crypt- --type luks
because it tries to access /dev/disk/by-uuid/ which
does not exist.
This happens since udev rules are not re-triggered to create this
symlink after a LUKS device is created.
Solution: call the command below after luks_format before luks_open
udevadm settle --exit-if-exists=/dev/disk/by-uuid/
To manage notifications about this bug go to:
https://bugs.launchpad.net/vaultlocker/+bug/1780332/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780332] Re: vaultlocker does not ensure that udev is triggered to create /dev/disk/by-uuid/ symlink and fails
Dimitri
vaultlocker is a helper tool for managing dmcrypt/LUKS keys in Vault.
vaultlocker provides commands to format a block devices using an
encryption key, and to unlock a block device previously encrypted by
vaultlocker (along with some systemd unit configurations to perform this
action on reboots).
Currently vaultlocker performs targetted rescan and settle udevadm
operations post luksFormat to wait for appropriate /dev entries to be
created; I consider this a workaround as it would be generally nicer if
this was actually performed as part of the luksFormat operation in
cryptsetup - once the format operation completes, block devices would be
ready for use without any need to udevadm trigger/settle in other
tooling.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1780332
Title:
vaultlocker does not ensure that udev is triggered to create /dev/disk
/by-uuid/ symlink and fails
Status in vaultlocker:
Fix Released
Status in cryptsetup package in Ubuntu:
New
Status in systemd package in Ubuntu:
Incomplete
Bug description:
When an encrypted device is setup up a UUID (osd_fsid) is passed from
the charm to be used in the cryptsetup command which accepts a UUID to
place into the LUKS header (shown in cryptsetup luksDump ).
https://github.com/openstack/charm-ceph-osd/blob/stable/18.05/lib/ceph/utils.py#L1788-L1804
UUID comes from osd_fsid
https://github.com/openstack-charmers/vaultlocker/blob/8c9cb85dc3ed5dbf18c66a810d189a5230d85c34/vaultlocker/shell.py#L69-L80
# else statement is used here
block_uuid = str(uuid.uuid4()) if not args.uuid else args.uuid
dmcrypt.luks_format(key, block_device, block_uuid) # creates a LUKS
header
# ...
dmcrypt.luks_open(key, block_uuid) # sets up a device with device mapper
decrypting it via dmcrypt
https://github.com/openstack-
charmers/vaultlocker/blob/d813233179bdf2eec8ed101c702a8e552a966f44/vaultlocker/dmcrypt.py#L44-L56
This UUID is visible in blkid output
/dev/sdc: UUID="" TYPE="crypto_LUKS"
and a udev rule exists to create a /dev/disk/by-uuid/ symlink (which is normally used for filesystem -> block device
resolution)
https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in#n25
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*",
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"
Where vaultlocker fails is in luks_open command (right after luks_format)
# cryptsetup --batch-mode --key-file - open UUID=
crypt- --type luks
because it tries to access /dev/disk/by-uuid/ which
does not exist.
This happens since udev rules are not re-triggered to create this
symlink after a LUKS device is created.
Solution: call the command below after luks_format before luks_open
udevadm settle --exit-if-exists=/dev/disk/by-uuid/
To manage notifications about this bug go to:
https://bugs.launchpad.net/vaultlocker/+bug/1780332/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1791710] Re: tar 1.29b-2 breaks pristine-tar
** Also affects: pristine-tar (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
https://bugs.launchpad.net/bugs/1791710
Title:
tar 1.29b-2 breaks pristine-tar
Status in pristine-tar package in Ubuntu:
New
Status in tar package in Ubuntu:
New
Bug description:
Steps to reproduce:
docker run -ti ubuntu:18.04 /bin/bash
apt-get update
apt-get install git build-essential tar pristine-tar
git clone git://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/neutron
cd neutron/
for i in `git branch -a | grep remote | grep -v HEAD | grep -v master`; do
git branch --track ${i#remotes/origin/} $i; done
# this command will fail
pristine-tar -v checkout neutron_10.0.7.orig.tar.gz
# to fix it update tar
apt-get install wget && wget
http://mirrors.kernel.org/ubuntu/pool/main/t/tar/tar_1.30+dfsg-2_amd64.deb
apt-get install ./tar_1.30+dfsg-2_amd64.deb
# now it works
pristine-tar -v checkout neutron_10.0.7.orig.tar.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pristine-tar/+bug/1791710/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
** Changed in: openvswitch (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: openvswitch (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Fix Released
Status in clamav package in Ubuntu:
Triaged
Status in controlaula package in Ubuntu:
Invalid
Status in epoptes package in Ubuntu:
New
Status in ethtool package in Ubuntu:
Triaged
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
Triaged
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
New
Status in openvpn package in Ubuntu:
New
Status in openvswitch package in Ubuntu:
Triaged
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750240] Re: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1
Bug could do with more detail but I think this happens when you make /usr/bin/python point to python3 - this breaks everything - python3 is always /usr/bin/python3. ** Changed in: python-decorator (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-decorator in Ubuntu. https://bugs.launchpad.net/bugs/1750240 Title: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 Status in python-decorator package in Ubuntu: Invalid Bug description: rush up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-decorator 4.0.6-1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sun Feb 18 09:54:27 2018 Dependencies: ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1 InstallationDate: Installed on 2018-01-24 (25 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: python-decorator Title: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-decorator/+bug/1750240/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748597] Re: Please backport fix for bugs.debian.org/827015
** Changed in: libunwind (Ubuntu) Status: New => Triaged ** Changed in: libunwind (Ubuntu) Importance: Undecided => Medium ** Also affects: libunwind (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: libunwind (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: libunwind (Ubuntu) Status: Triaged => Fix Released ** Changed in: libunwind (Ubuntu Xenial) Status: New => Triaged ** Changed in: libunwind (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: libunwind (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: libunwind (Ubuntu Trusty) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1748597 Title: Please backport fix for bugs.debian.org/827015 Status in libunwind package in Ubuntu: Fix Released Status in libunwind source package in Trusty: Triaged Status in libunwind source package in Xenial: Triaged Status in libunwind package in Debian: Fix Released Bug description: [Impact] When a C++ exception is thrown with libunwind linked in, the signal mask is corrupted. For MongoDB, if the CPU profiler is enabled (which requires linking libunwind), any exception that is raised within the server may cause random signals to become unblocked on a thread. If SIGTERM becomes unblocked on any thread but the main thread, the server won't exit cleanly (this is particularly evident when running the MongoDB test suite, which starts/stops servers repeatedly). This also seems to impact Pyston: https://lab.nexedi.com/Daetalus/Pyston/commit/1bac7510861a112a9023f821bf3e857a6fb45037 [Test Case] I've attached the test case from the upstream Debian bug (https://bugs.debian.org/827015). $ g++ sigtest.cpp -lpthread $ ./a.out Signals blocked: 1 (Hangup) 65 (Unknown signal 65) Throw exception Signals blocked: 1 (Hangup) 65 (Unknown signal 65) $ g++ sigtest.cpp -lpthread -lunwind $ ./a.out Signals blocked: 1 (Hangup) 65 (Unknown signal 65) Throw exception Signals blocked: 7 (Bus error)8 (Floating point exception)10 (User defined signal 1) 12 (User defined signal 2) 13 (Broken pipe) 15 (Terminated) 17 (Child exited) 20 (Stopped)21 (Stopped (tty input))25 (File size limit exceeded) 26 (Virtual timer expired) 27 (Profiling timer expired)28 (Window changed) 29 (I/O possible) 30 (Power failure) 31 (Bad system call)32 (Unknown signal 32) 33 (Unknown signal 33) 34 (Real-time signal 0) 35 (Real-time signal 1) 36 (Real-time signal 2) 37 (Real-time signal 3) 38 (Real-time signal 4) 39 (Real-time signal 5) 40 (Real-time signal 6) 41 (Real-time signal 7) 42 (Real-time signal 8) 43 (Real-time signal 9) 44 (Real-time signal 10)45 (Real-time signal 11)46 (Real-time signal 12)47 (Real-time signal 13)65 (Unknown signal 65) [Regression Potential] This fix is already present in bionic and Debian testing, and has been for a couple months. The upstream fix has existed for over a year. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1748597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758331] Re: IPv6 Route to OpenVPN Server is not created
Tested on my laptop using hostname based endpoint from IPv6 enable location (was failing previously); packages from PPA resolved my problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1758331 Title: IPv6 Route to OpenVPN Server is not created Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Confirmed Bug description: Hi, When the OpenVPN server pushes routes that overlaps with the openvpn server IP, it should add a route to the OpenVPN server. This seems to get done, but it fails: NetworkManager[1031]: [1521794922.6687] platform: signal: route 6 added: 2a00:x:x::3/128 via fe80::230:48ff:fedc:5067 dev 2 metric 100 mss 0 rt-src rt-ra src ::/128 pref-src 2a02:x:x:x:x:x:x:5fc6 NetworkManager[1031]: [1521794922.6687] device[0x55566c34c4e0] (enxa44cc890f4c8): queued IP6 config change NetworkManager[1031]: [1521794922.6688] platform: route: get IPv6 route for: 2a00:x:x::3 failed with unspecified 2a00:x:x::3 => VPN Server IPv6 Now this seems to be fixed in commit: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=2d1fad641b950520bec1a87c450d0e3b1439e262 Can we get this cherry-picked in Bionic? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1758331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1747388] Re: patch for multipath disks
** Package changed: udev (Ubuntu) => lvm2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1747388
Title:
patch for multipath disks
Status in OpenStack ceph-osd charm:
Invalid
Status in lvm2 package in Ubuntu:
New
Bug description:
According to this page:
https://patchwork.kernel.org/patch/9826353/
there is a bug in ceph that affects the use of FibreChannel disks.
The following patch to file hooks/ceph_hooks.py, fixes it:
*** hooks/ceph_hooks.py 2018-02-02 16:15:40.304388602 +0100
--- hooks/ceph_hooks.py~ 2018-02-02 16:18:47.304401004 +0100
***
*** 369,378
@hooks.hook('storage.real')
def prepare_disks_and_activate():
- # patch for missing dm devices
- # see: https://patchwork.kernel.org/patch/9826353/
- patch_persistent_storage_rules()
-
osd_journal = get_journal_devices()
check_overlap(osd_journal, set(get_devices()))
log("got journal devs: {}".format(osd_journal), level=DEBUG)
--- 369,374
***
*** 558,579
log('Updating status.')
- # patch for missing dm devices
- from subprocess import check_call
-
-
- CEPH_PERSITENT_STORTAGE_RULES =
'/lib/udev/rules.d/60-persistent-storage.rules'
-
-
- def patch_persistent_storage_rules():
- if os.path.isfile(CEPH_PERSITENT_STORTAGE_RULES):
- check_call(['sed', '-i', 's/KERNEL!="loop/KERNEL!="dm*|loop/',
- CEPH_PERSITENT_STORTAGE_RULES])
- log('Patched %s' % CEPH_PERSITENT_STORTAGE_RULES)
- else:
- log('Missing %s' % CEPH_PERSITENT_STORTAGE_RULES)
-
-
if __name__ == '__main__':
try:
hooks.execute(sys.argv)
--- 554,559 ——
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1747388/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage
Also validated that the update fixes an existing machine with the 1.2 update on it (with pacemaker services not running). Pacemaker started after the update. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1727063 Title: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage Status in OpenStack hacluster charm: Invalid Status in init-system-helpers package in Ubuntu: New Status in pacemaker package in Ubuntu: Fix Released Status in init-system-helpers source package in Xenial: New Status in pacemaker source package in Xenial: Triaged Status in init-system-helpers source package in Zesty: New Status in pacemaker source package in Zesty: Fix Released Status in init-system-helpers source package in Artful: New Status in pacemaker source package in Artful: Fix Released Status in init-system-helpers source package in Bionic: New Status in pacemaker source package in Bionic: Fix Released Bug description: [Impact] upgrades of the pacemaker package don't restart pacemaker after the package upgrade, resulting in down HA clusters. [Test Case] sudo apt install pacemaker sudo systemctl start pacemaker sudo dpkg-reconfigure pacemaker pacemaker daemons will not be restarted. [Regression Potential] Minimal, earlier and later versions provide the defaults in the lsb header. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage
Testing from security-proposed PPA: Broken install (dpkg-reconfigure pacemaker already run, daemons stopped): Packages updated and pacemaker daemon restarted by postinst: OK Running install (pacemaker daemons running prior to pkg upgrade): Packages update, pacemaker daemon stop prior to unpack and restarted by postinst: OK >From my perspective the update looks good - but would appreciate a second pair of eyes on this one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1727063 Title: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage Status in OpenStack hacluster charm: Invalid Status in init-system-helpers package in Ubuntu: New Status in pacemaker package in Ubuntu: Fix Released Status in init-system-helpers source package in Xenial: New Status in pacemaker source package in Xenial: Triaged Status in init-system-helpers source package in Zesty: New Status in pacemaker source package in Zesty: Fix Released Status in init-system-helpers source package in Artful: New Status in pacemaker source package in Artful: Fix Released Status in init-system-helpers source package in Bionic: New Status in pacemaker source package in Bionic: Fix Released Bug description: [Impact] upgrades of the pacemaker package don't restart pacemaker after the package upgrade, resulting in down HA clusters. [Test Case] sudo apt install pacemaker sudo systemctl start pacemaker sudo dpkg-reconfigure pacemaker pacemaker daemons will not be restarted. [Regression Potential] Minimal, earlier and later versions provide the defaults in the lsb header. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage
Also tested proposed fix on a three unit gnocchi HA deployment; all pacemaker updates applied and restarted pacemaker postinst as desired. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1727063 Title: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage Status in OpenStack hacluster charm: Invalid Status in init-system-helpers package in Ubuntu: New Status in pacemaker package in Ubuntu: Fix Released Status in init-system-helpers source package in Xenial: New Status in pacemaker source package in Xenial: Triaged Status in init-system-helpers source package in Zesty: New Status in pacemaker source package in Zesty: Fix Released Status in init-system-helpers source package in Artful: New Status in pacemaker source package in Artful: Fix Released Status in init-system-helpers source package in Bionic: New Status in pacemaker source package in Bionic: Fix Released Bug description: [Impact] upgrades of the pacemaker package don't restart pacemaker after the package upgrade, resulting in down HA clusters. [Test Case] sudo apt install pacemaker sudo systemctl start pacemaker sudo dpkg-reconfigure pacemaker pacemaker daemons will not be restarted. [Regression Potential] Minimal, earlier and later versions provide the defaults in the lsb header. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage
Updates building in: https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1727063 Title: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage Status in OpenStack hacluster charm: Invalid Status in init-system-helpers package in Ubuntu: New Status in pacemaker package in Ubuntu: Fix Released Status in init-system-helpers source package in Xenial: New Status in pacemaker source package in Xenial: Triaged Status in init-system-helpers source package in Zesty: New Status in pacemaker source package in Zesty: Fix Released Status in init-system-helpers source package in Artful: New Status in pacemaker source package in Artful: Fix Released Status in init-system-helpers source package in Bionic: New Status in pacemaker source package in Bionic: Fix Released Bug description: [Impact] upgrades of the pacemaker package don't restart pacemaker after the package upgrade, resulting in down HA clusters. [Test Case] sudo apt install pacemaker sudo systemctl start pacemaker sudo dpkg-reconfigure pacemaker pacemaker daemons will not be restarted. [Regression Potential] Minimal, earlier and later versions provide the defaults in the lsb header. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage
** Description changed: [Impact] upgrades of the pacemaker package don't restart pacemaker after the package upgrade, resulting in down HA clusters. [Test Case] sudo apt install pacemaker sudo systemctl start pacemaker sudo dpkg-reconfigure pacemaker pacemaker daemons will not be restarted. [Regression Potential] - TBC as not quite sure where the fix for this is. + Minimal, earlier and later versions provide the defaults in the lsb header. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1727063 Title: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage Status in OpenStack hacluster charm: Invalid Status in init-system-helpers package in Ubuntu: New Status in pacemaker package in Ubuntu: Fix Released Status in init-system-helpers source package in Xenial: New Status in pacemaker source package in Xenial: Triaged Status in init-system-helpers source package in Zesty: New Status in pacemaker source package in Zesty: Fix Released Status in init-system-helpers source package in Artful: New Status in pacemaker source package in Artful: Fix Released Status in init-system-helpers source package in Bionic: New Status in pacemaker source package in Bionic: Fix Released Bug description: [Impact] upgrades of the pacemaker package don't restart pacemaker after the package upgrade, resulting in down HA clusters. [Test Case] sudo apt install pacemaker sudo systemctl start pacemaker sudo dpkg-reconfigure pacemaker pacemaker daemons will not be restarted. [Regression Potential] Minimal, earlier and later versions provide the defaults in the lsb header. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage
Tested OK (pacemaker was restarted after upgrade) Uploaded to unapproved queue for SRU Team review - I'd suggest we fasttrack this ASAP into -updates and -security to catch auto updates for those systems not already updated. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1727063 Title: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage Status in OpenStack hacluster charm: Invalid Status in init-system-helpers package in Ubuntu: New Status in pacemaker package in Ubuntu: Fix Released Status in init-system-helpers source package in Xenial: New Status in pacemaker source package in Xenial: Triaged Status in init-system-helpers source package in Zesty: New Status in pacemaker source package in Zesty: Fix Released Status in init-system-helpers source package in Artful: New Status in pacemaker source package in Artful: Fix Released Status in init-system-helpers source package in Bionic: New Status in pacemaker source package in Bionic: Fix Released Bug description: [Impact] upgrades of the pacemaker package don't restart pacemaker after the package upgrade, resulting in down HA clusters. [Test Case] sudo apt install pacemaker sudo systemctl start pacemaker sudo dpkg-reconfigure pacemaker pacemaker daemons will not be restarted. [Regression Potential] Minimal, earlier and later versions provide the defaults in the lsb header. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage
Doing some testing via: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3010 before upload to xenial-proposed; not that the act of fixing this problem will in itself cause the pacemaker daemons to be started on upgrade. However it won't be auto-applied on a default install (unlike the security update that caused the original issue). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1727063 Title: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage Status in OpenStack hacluster charm: Invalid Status in init-system-helpers package in Ubuntu: New Status in pacemaker package in Ubuntu: Fix Released Status in init-system-helpers source package in Xenial: New Status in pacemaker source package in Xenial: Triaged Status in init-system-helpers source package in Zesty: New Status in pacemaker source package in Zesty: Fix Released Status in init-system-helpers source package in Artful: New Status in pacemaker source package in Artful: Fix Released Status in init-system-helpers source package in Bionic: New Status in pacemaker source package in Bionic: Fix Released Bug description: [Impact] upgrades of the pacemaker package don't restart pacemaker after the package upgrade, resulting in down HA clusters. [Test Case] sudo apt install pacemaker sudo systemctl start pacemaker sudo dpkg-reconfigure pacemaker pacemaker daemons will not be restarted. [Regression Potential] TBC as not quite sure where the fix for this is. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage
Proposed update for xenial ** Patch added: "pacemaker.debdiff" https://bugs.launchpad.net/ubuntu/zesty/+source/pacemaker/+bug/1727063/+attachment/4993845/+files/pacemaker.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1727063 Title: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage Status in OpenStack hacluster charm: Invalid Status in init-system-helpers package in Ubuntu: New Status in pacemaker package in Ubuntu: Fix Released Status in init-system-helpers source package in Xenial: New Status in pacemaker source package in Xenial: Triaged Status in init-system-helpers source package in Zesty: New Status in pacemaker source package in Zesty: Fix Released Status in init-system-helpers source package in Artful: New Status in pacemaker source package in Artful: Fix Released Status in init-system-helpers source package in Bionic: New Status in pacemaker source package in Bionic: Fix Released Bug description: [Impact] upgrades of the pacemaker package don't restart pacemaker after the package upgrade, resulting in down HA clusters. [Test Case] sudo apt install pacemaker sudo systemctl start pacemaker sudo dpkg-reconfigure pacemaker pacemaker daemons will not be restarted. [Regression Potential] TBC as not quite sure where the fix for this is. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage
Actually this only impacts Xenial; Debian carried a patch from: pacemaker (1.1.15~rc3-1) unstable; urgency=medium [ Christoph Berg ] * [23ee108] libcrmservice3.symbols: Exclude systemd symbol on non-linux * [41dea05] Fix time formatting on x32 * [533c5cc] Fix FTBFS on GNU Hurd [ Arturo Borrero Gonzalez ] * [698053d] d/tests/control: add isolation-container restriction [ Ferenc Wágner ] * [065159d] New patch Enable-the-init-scripts-on-multi-user-runlevels.patch * [7a5008b] New patch Make-the-asciidoc-documentation-reproducible.patch * [08a4162] New patch Add-remote_fs-dependencies-to-the-init-scripts.patch * [7a65d2c] New upstream release (1.1.15~rc1) * [dd9f5f4] Remove upstreamed patches, refresh the rest * [0cdd116] Update symbol files * [3de7a21] New patch Add-documentation-URIs-to-the-service-files.patch * [9faaa02] Move documentation generators into Build-Depends-Indep * [9362a46] Move documentation into /usr/share/doc/pacemaker * [64c0e84] Move misc documentation files into the pacemaker-doc package * [837e74d] New patch Read-default-files-in-pacemaker.service.patch * [72fef80] New upstream release (1.1.15~rc2) * [69ee575] Remove patch included in 1.1.15~rc2 * [46dce98] Also add documentation URI to our version of crm_mon.service * [8c25aff] New patch to avoid using WIFCONTINUED entirely * [a28e0ae] New upstream release (1.1.15~rc3) * [a8976fe] Remove freshly upstreamed patches, refresh the rest -- Ferenc Wágner Sat, 28 May 2016 22:28:49 +0200 Which re-enables the default runlevels. ** Changed in: pacemaker (Ubuntu Bionic) Status: Triaged => Fix Released ** Changed in: pacemaker (Ubuntu Artful) Status: Triaged => Fix Released ** Changed in: pacemaker (Ubuntu Zesty) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1727063 Title: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage Status in OpenStack hacluster charm: Invalid Status in init-system-helpers package in Ubuntu: New Status in pacemaker package in Ubuntu: Fix Released Status in init-system-helpers source package in Xenial: New Status in pacemaker source package in Xenial: Triaged Status in init-system-helpers source package in Zesty: New Status in pacemaker source package in Zesty: Fix Released Status in init-system-helpers source package in Artful: New Status in pacemaker source package in Artful: Fix Released Status in init-system-helpers source package in Bionic: New Status in pacemaker source package in Bionic: Fix Released Bug description: [Impact] upgrades of the pacemaker package don't restart pacemaker after the package upgrade, resulting in down HA clusters. [Test Case] sudo apt install pacemaker sudo systemctl start pacemaker sudo dpkg-reconfigure pacemaker pacemaker daemons will not be restarted. [Regression Potential] TBC as not quite sure where the fix for this is. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage
This issue can be fixed by re-adding the required Start/Stop bits to the LSB header; however the behaviour of update-rc.d when native systemd unit files are in use looks odd to me. Raising an init-system-helpers bug task for foundations team input on this. ** Also affects: init-system-helpers (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1727063 Title: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage Status in OpenStack hacluster charm: Invalid Status in init-system-helpers package in Ubuntu: New Status in pacemaker package in Ubuntu: Triaged Status in init-system-helpers source package in Xenial: New Status in pacemaker source package in Xenial: Triaged Status in init-system-helpers source package in Zesty: New Status in pacemaker source package in Zesty: Triaged Status in init-system-helpers source package in Artful: New Status in pacemaker source package in Artful: Triaged Status in init-system-helpers source package in Bionic: New Status in pacemaker source package in Bionic: Triaged Bug description: [Impact] upgrades of the pacemaker package don't restart pacemaker after the package upgrade, resulting in down HA clusters. [Test Case] sudo apt install pacemaker sudo systemctl start pacemaker sudo dpkg-reconfigure pacemaker pacemaker daemons will not be restarted. [Regression Potential] TBC as not quite sure where the fix for this is. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1727063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675456] Re: package python-decorator 4.0.6-1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 127
Настраивается пакет python-decorator (4.0.6-1) … /var/lib/dpkg/info/python-decorator.postinst: 6: /var/lib/dpkg/info/python-decorator.postinst: pycompile: not found dpkg: ошибка при обработке пакета python-decorator (--configure): подпроцесс установлен сценарий post-installation возвратил код ошибки 127 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-decorator in Ubuntu. https://bugs.launchpad.net/bugs/1675456 Title: package python-decorator 4.0.6-1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 127 Status in python-decorator package in Ubuntu: Invalid Bug description: 1) the release of Ubiuntu: ubuntu 16.04 LTS 2) python-decorator: Установлен: 4.0.6-1 Кандидат: 4.0.6-1 Таблица версий: *** 4.0.6-1 500 500 http://ru.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status 3) I entered to command line: sudo apt-get install python-numpy python-scipy python-dev python-pip python-nose g++ libopenblas-dev git And expected the install all of packages 4) I got a messange, that this packeges have installed already and they have owned a last vertion. But also i got the messange, that in packeges: python-crypto python-decorator python-pil:i386 python-imaging python-nose python-pip python-wheel python-scipy were an errors ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-decorator 4.0.6-1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 Date: Thu Mar 23 20:09:07 2017 Dependencies: ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 127 InstallationDate: Installed on 2016-07-30 (236 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: python-decorator Title: package python-decorator 4.0.6-1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-decorator/+bug/1675456/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675456] Re: package python-decorator 4.0.6-1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 127
pycompile is provided by python-minimal which is a direct dependency of pretty much all python-* packages; why its not found is a bit of a mystery - you can try reinstalling it: sudo apt install --reinstall python-minimal to see if that helps? Also check if its already present and you have something wonky going on with paths. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-decorator in Ubuntu. https://bugs.launchpad.net/bugs/1675456 Title: package python-decorator 4.0.6-1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 127 Status in python-decorator package in Ubuntu: Invalid Bug description: 1) the release of Ubiuntu: ubuntu 16.04 LTS 2) python-decorator: Установлен: 4.0.6-1 Кандидат: 4.0.6-1 Таблица версий: *** 4.0.6-1 500 500 http://ru.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status 3) I entered to command line: sudo apt-get install python-numpy python-scipy python-dev python-pip python-nose g++ libopenblas-dev git And expected the install all of packages 4) I got a messange, that this packeges have installed already and they have owned a last vertion. But also i got the messange, that in packeges: python-crypto python-decorator python-pil:i386 python-imaging python-nose python-pip python-wheel python-scipy were an errors ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-decorator 4.0.6-1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 Date: Thu Mar 23 20:09:07 2017 Dependencies: ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 127 InstallationDate: Installed on 2016-07-30 (236 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: python-decorator Title: package python-decorator 4.0.6-1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-decorator/+bug/1675456/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675456] Re: package python-decorator 4.0.6-1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 127
https://askubuntu.com/questions/565438/deleted-the-python-binary-and- cant-recover-using-apt-get-what-can-i-do also has some advice here. ** Changed in: python-decorator (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-decorator in Ubuntu. https://bugs.launchpad.net/bugs/1675456 Title: package python-decorator 4.0.6-1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 127 Status in python-decorator package in Ubuntu: Invalid Bug description: 1) the release of Ubiuntu: ubuntu 16.04 LTS 2) python-decorator: Установлен: 4.0.6-1 Кандидат: 4.0.6-1 Таблица версий: *** 4.0.6-1 500 500 http://ru.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status 3) I entered to command line: sudo apt-get install python-numpy python-scipy python-dev python-pip python-nose g++ libopenblas-dev git And expected the install all of packages 4) I got a messange, that this packeges have installed already and they have owned a last vertion. But also i got the messange, that in packeges: python-crypto python-decorator python-pil:i386 python-imaging python-nose python-pip python-wheel python-scipy were an errors ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-decorator 4.0.6-1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 Date: Thu Mar 23 20:09:07 2017 Dependencies: ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 127 InstallationDate: Installed on 2016-07-30 (236 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: python-decorator Title: package python-decorator 4.0.6-1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-decorator/+bug/1675456/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667372] Re: package python-decorator 4.0.6-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Setting up python-decorator (4.0.6-1) ... /var/lib/dpkg/info/python-decorator.postinst: 6: /var/lib/dpkg/info/python-decorator.postinst: pycompile: not found dpkg: error processing package python-decorator (--configure): subprocess installed post-installation script returned error exit status 127 pycompile is provided by python-minimal; as this is a direct dependency of python-decorator I can only assume a local change was made to the system to remove this binary - please can you check its present and if not: sudo apt install --reinstall python-minimal Marking this bug as 'Invalid' as its not specific to this python module. ** Changed in: python-decorator (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-decorator in Ubuntu. https://bugs.launchpad.net/bugs/1667372 Title: package python-decorator 4.0.6-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in python-decorator package in Ubuntu: Invalid Bug description: error message when boot system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-decorator 4.0.6-1 ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44 Uname: Linux 4.4.0-63-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Wed Feb 22 22:16:54 2017 Dependencies: DuplicateSignature: package:python-decorator:4.0.6-1 Setting up python-decorator (4.0.6-1) ... /var/lib/dpkg/info/python-decorator.postinst: 6: /var/lib/dpkg/info/python-decorator.postinst: pycompile: not found dpkg: error processing package python-decorator (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2016-12-06 (78 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: python-decorator Title: package python-decorator 4.0.6-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-decorator/+bug/1667372/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703573] Re: package python-decorator 4.0.6-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Any chance /usr/bin/python is not a symlink to /usr/bin/python2.7? ConfigParser is part of the Python 2.7 stdlib; in Python 3 its been renamed to configparser, so the debpython module won't work with Python 3. I'm going to mark this bug as Invalid; if the above is not true, please set back to new. ** Changed in: python-decorator (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-decorator in Ubuntu. https://bugs.launchpad.net/bugs/1703573 Title: package python-decorator 4.0.6-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-decorator package in Ubuntu: Invalid Bug description: package python-decorator 4.0.6-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 I am seeing system internal error message popping up everytime I start the OS and this Bug also doesn't allow me to do system updates ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-decorator 4.0.6-1 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sat Jul 8 16:52:48 2017 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-01-11 (180 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: python-decorator Title: package python-decorator 4.0.6-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-decorator/+bug/1703573/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710313] Re: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1
Looks like somehow 'python-configparser' is no longer installed on your desktop; try resolving using: sudo apt install python-configparser python-minimal uses configparser, but has no direct depends which I find a little odd. ** Package changed: python-decorator (Ubuntu) => python-defaults (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-decorator in Ubuntu. https://bugs.launchpad.net/bugs/1710313 Title: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 Status in python-defaults package in Ubuntu: New Bug description: I can't enter the desktop system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-decorator 4.0.6-1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Aug 11 23:44:37 2017 Dependencies: ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1 InstallationDate: Installed on 2017-08-10 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: python-decorator Title: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1710313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710313] Re: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1
Re-assigning to python-defaults (which provides python-minimal). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1710313 Title: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 Status in python-defaults package in Ubuntu: New Bug description: I can't enter the desktop system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-decorator 4.0.6-1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Aug 11 23:44:37 2017 Dependencies: ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1 InstallationDate: Installed on 2017-08-10 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: python-decorator Title: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1710313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1702300] Re: package libcephfs1 10.2.7-0ubuntu0.17.04.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado
This is a general installation issue rather than a specific issue with this library: A processar 'triggers' para libc-bin (2.24-9ubuntu2.2) ... /sbin/ldconfig.real: /usr/lib/x86_64-linux-gnu/libplc4.so is not a symbolic link /sbin/ldconfig.real: /usr/lib/x86_64-linux-gnu/libnspr4.so is not a symbolic link /sbin/ldconfig.real: /usr/lib/x86_64-linux-gnu/libplds4.so is not a symbolic link Re-targetting to one of the impacted .so's but I think its probably a localized issue in your installation. ** Package changed: ceph (Ubuntu) => nspr (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nspr in Ubuntu. https://bugs.launchpad.net/bugs/1702300 Title: package libcephfs1 10.2.7-0ubuntu0.17.04.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado Status in nspr package in Ubuntu: New Bug description: eu não sei o que esta acontecendo somente que o sistema pediu pra enviar relatorio ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libcephfs1 10.2.7-0ubuntu0.17.04.1 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: libgcrypt20:amd64: Install libgcrypt20:amd64: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Jul 4 09:04:56 2017 DpkgHistoryLog: Start-Date: 2017-07-04 09:04:41 Commandline: /usr/bin/unattended-upgrade Upgrade: libgcrypt20:amd64 (1.7.6-1, 1.7.6-1ubuntu0.1) ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2017-05-06 (58 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: ceph Title: package libcephfs1 10.2.7-0ubuntu0.17.04.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/1702300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1643675] Re: hugepages for non-default pagesize need manual setup
** Changed in: charm-nova-compute
Importance: Undecided => Medium
** Changed in: charm-nova-compute
Status: New => Triaged
** Changed in: nova-compute (Juju Charms Collection)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1643675
Title:
hugepages for non-default pagesize need manual setup
Status in OpenStack nova-compute charm:
Triaged
Status in libvirt package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Confirmed
Status in nova-compute package in Juju Charms Collection:
Invalid
Bug description:
This is a amd64 xenial/mitaka deploy using 1607 charms release
where I need to have 1G hugepages available for openstack/kvm.
nova-compute charm should provide ways to ease e.g.
1G hugepages setup, currently only exposes a
"hugepages" setting that ends setting vm.nr_hugepages
for the node, but even after settings kernel cmdline
parameters for 1G hugepages (hugepagesz=1G hugepages=128),
is not usable by libvirt-bin:
#1 systemd:
Installs /lib/systemd/system/dev-hugepages.mount with
default pagesize
=> no hugetblfs mount with (e.g.) pagesize=1G
#2 libvirt-bin:
Installs apparmor profile ("libvirt-qemu") which only allows:
# for access to hugepages
owner "/run/hugepages/kvm/libvirt/qemu/**" rw,
owner "/dev/hugepages/libvirt/qemu/**" rw,
=> not possible to have other mount points for other pagesizes.
I've workaround'd #1,#2 above by overriding systemd's
by creating a /etc/systemd/system/dev-hugepages.mount
with below extra line at [Mount] section:
Options=pagesize=1G
-> https://paste.ubuntu.com/23513048/
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-nova-compute/+bug/1643675/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1643675] Re: hugepages for non-default pagesize need manual setup
FWIW I think kernel boot command line options should be the preferred
way of allocating hugepages as its generally the most reliable way of
doing it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1643675
Title:
hugepages for non-default pagesize need manual setup
Status in libvirt package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Status in nova-compute package in Juju Charms Collection:
Triaged
Bug description:
This is a amd64 xenial/mitaka deploy using 1607 charms release
where I need to have 1G hugepages available for openstack/kvm.
nova-compute charm should provide ways to ease e.g.
1G hugepages setup, currently only exposes a
"hugepages" setting that ends setting vm.nr_hugepages
for the node, but even after settings kernel cmdline
parameters for 1G hugepages (hugepagesz=1G hugepages=128),
is not usable by libvirt-bin:
#1 systemd:
Installs /lib/systemd/system/dev-hugepages.mount with
default pagesize
=> no hugetblfs mount with (e.g.) pagesize=1G
#2 libvirt-bin:
Installs apparmor profile ("libvirt-qemu") which only allows:
# for access to hugepages
owner "/run/hugepages/kvm/libvirt/qemu/**" rw,
owner "/dev/hugepages/libvirt/qemu/**" rw,
=> not possible to have other mount points for other pagesizes.
I've workaround'd #1,#2 above by overriding systemd's
by creating a /etc/systemd/system/dev-hugepages.mount
with below extra line at [Mount] section:
Options=pagesize=1G
-> https://paste.ubuntu.com/23513048/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1643675/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1643675] Re: hugepages for non-default pagesize need manual setup
@jjo
Use of 'default_hugepagesz=1G' might also tweak things a bit.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1643675
Title:
hugepages for non-default pagesize need manual setup
Status in libvirt package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Status in nova-compute package in Juju Charms Collection:
Triaged
Bug description:
This is a amd64 xenial/mitaka deploy using 1607 charms release
where I need to have 1G hugepages available for openstack/kvm.
nova-compute charm should provide ways to ease e.g.
1G hugepages setup, currently only exposes a
"hugepages" setting that ends setting vm.nr_hugepages
for the node, but even after settings kernel cmdline
parameters for 1G hugepages (hugepagesz=1G hugepages=128),
is not usable by libvirt-bin:
#1 systemd:
Installs /lib/systemd/system/dev-hugepages.mount with
default pagesize
=> no hugetblfs mount with (e.g.) pagesize=1G
#2 libvirt-bin:
Installs apparmor profile ("libvirt-qemu") which only allows:
# for access to hugepages
owner "/run/hugepages/kvm/libvirt/qemu/**" rw,
owner "/dev/hugepages/libvirt/qemu/**" rw,
=> not possible to have other mount points for other pagesizes.
I've workaround'd #1,#2 above by overriding systemd's
by creating a /etc/systemd/system/dev-hugepages.mount
with below extra line at [Mount] section:
Options=pagesize=1G
-> https://paste.ubuntu.com/23513048/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1643675/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1643675] Re: hugepages for non-default pagesize need manual setup
This feels like this generally needs improving, with automatic mounting
of hugepage FS for different pagesize options - so for example:
/dev/hugepages1G
/def/hugepages
with appropriate apparmor changes as well for libvirt to allow access to
common paths on Ubuntu systems.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1643675
Title:
hugepages for non-default pagesize need manual setup
Status in libvirt package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Status in nova-compute package in Juju Charms Collection:
Triaged
Bug description:
This is a amd64 xenial/mitaka deploy using 1607 charms release
where I need to have 1G hugepages available for openstack/kvm.
nova-compute charm should provide ways to ease e.g.
1G hugepages setup, currently only exposes a
"hugepages" setting that ends setting vm.nr_hugepages
for the node, but even after settings kernel cmdline
parameters for 1G hugepages (hugepagesz=1G hugepages=128),
is not usable by libvirt-bin:
#1 systemd:
Installs /lib/systemd/system/dev-hugepages.mount with
default pagesize
=> no hugetblfs mount with (e.g.) pagesize=1G
#2 libvirt-bin:
Installs apparmor profile ("libvirt-qemu") which only allows:
# for access to hugepages
owner "/run/hugepages/kvm/libvirt/qemu/**" rw,
owner "/dev/hugepages/libvirt/qemu/**" rw,
=> not possible to have other mount points for other pagesizes.
I've workaround'd #1,#2 above by overriding systemd's
by creating a /etc/systemd/system/dev-hugepages.mount
with below extra line at [Mount] section:
Options=pagesize=1G
-> https://paste.ubuntu.com/23513048/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1643675/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629102] Re: Unable to start or initialise any ceph process (ceph-mon)
Somehow this bug just went away - I'm not 100% sure why but marking
invalid for ceph.
** Changed in: ceph (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/1629102
Title:
Unable to start or initialise any ceph process (ceph-mon)
Status in ceph package in Ubuntu:
Invalid
Status in google-perftools package in Ubuntu:
Incomplete
Status in libunwind package in Ubuntu:
New
Bug description:
Latest yakkety server build, with ceph 10.2.2; creation of the ceph-
mon FS hangs:
ceph-mon --mkfs -i juju-
3da7bf0b-0062-4a2f-8949-d85e6579b759-machine-15 --keyring
/var/lib/ceph/tmp/juju-
3da7bf0b-0062-4a2f-8949-d85e6579b759-machine-15.mon.keyring
spinning in:
nanosleep({0, 201}, NULL) = 0
top of backtrace:
#0 0x7f5a619efd10 in __nanosleep_nocancel () at
../sysdeps/unix/syscall-template.S:84
No locals.
#1 0x7f5a624b9193 in base::internal::SpinLockDelay(int volatile*, int,
int) () from /usr/lib/libtcmalloc.so.4
No symbol table info available.
#2 0x7f5a624b9026 in SpinLock::SlowLock() () from
/usr/lib/libtcmalloc.so.4
No symbol table info available.
#3 0x7f5a624adb78 in tcmalloc::ThreadCache::InitModule() () from
/usr/lib/libtcmalloc.so.4
No symbol table info available.
#4 0x7f5a624bbe55 in tc_malloc () from /usr/lib/libtcmalloc.so.4
No symbol table info available.
#5 0x7f5a5fc05f7d in __fopen_internal (filename=0x7f5a6291c4a0
"/usr/lib/libtcmalloc.so.4", mode=0x7f5a5f984c6a "r", is32=1) at iofopen.c:69
new_f =
#6 0x7f5a5f982ab8 in ?? () from /usr/lib/x86_64-linux-gnu/libunwind.so.8
No symbol table info available.
#7 0x7f5a5f983624 in ?? () from /usr/lib/x86_64-linux-gnu/libunwind.so.8
No symbol table info available.
#8 0x7f5a5f983710 in _ULx86_64_dwarf_find_debug_frame () from
/usr/lib/x86_64-linux-gnu/libunwind.so.8
No symbol table info available.
#9 0x7f5a5f983cde in ?? () from /usr/lib/x86_64-linux-gnu/libunwind.so.8
No symbol table info available.
#10 0x7f5a5fcdc0a4 in __GI___dl_iterate_phdr (callback=0x7f5a5f983940,
data=0x7fff3a02ba90) at dl-iteratephdr.c:76
__clframe = {__cancel_routine = , __cancel_arg = 0x0,
__do_it = 1, __cancel_type = }
nloaded = 26
ns =
caller =
l = 0x7f5a6291c4c0
info = {dlpi_addr = 140026172706816, dlpi_name = 0x7f5a6291c4a0
"/usr/lib/libtcmalloc.so.4", dlpi_phdr = 0x7f5a62489040, dlpi_phnum = 8,
dlpi_adds = 26, dlpi_subs = 0, dlpi_tls_modid = 2, dlpi_tls_data =
0x7f5a62906760}
ret = 0
looks like initial setup of tcmalloc is spinning - I've seen the same happen
on start of the ceph-mon daemon (which I thought was the original problem).
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ceph-mon 10.2.2-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Thu Sep 29 20:43:51 2016
Ec2AMI: ami-045c
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small.osci
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: ceph
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1629102/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1631328] Re: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration"
** Changed in: ceph (Ubuntu) Assignee: (unassigned) => James Page (james-page) ** Changed in: ceph (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1631328 Title: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration" Status in ceph package in Ubuntu: In Progress Status in systemd package in Ubuntu: New Status in ceph-osd package in Juju Charms Collection: Invalid Bug description: The "ceph/default," "ceph_radosgw/simple_nonha" and "ceph/harden" mojo specs @ Yakkety are failing like so: Units are consistently blocked in Juju status: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration" Snippets from ceph-osd unit syslog: mkjournal error creating journal on /var/lib/ceph/tmp/mnt.W59Jhd/journal: (13) Permission denied Oct 7 03:13:30 juju-osci-sv13-machine-4 systemd[1]: Failed to start Ceph disk activation: /dev/vdb1. See: http://pastebin.ubuntu.com/23288515/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1631328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1631328] Re: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration"
** Changed in: ceph (Ubuntu) Status: New => Triaged ** Changed in: ceph (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1631328 Title: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration" Status in ceph package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Status in ceph-osd package in Juju Charms Collection: Invalid Bug description: The "ceph/default," "ceph_radosgw/simple_nonha" and "ceph/harden" mojo specs @ Yakkety are failing like so: Units are consistently blocked in Juju status: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration" Snippets from ceph-osd unit syslog: mkjournal error creating journal on /var/lib/ceph/tmp/mnt.W59Jhd/journal: (13) Permission denied Oct 7 03:13:30 juju-osci-sv13-machine-4 systemd[1]: Failed to start Ceph disk activation: /dev/vdb1. See: http://pastebin.ubuntu.com/23288515/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1631328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1631328] Re: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration"
Not a charm bug - marking invalid. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1631328 Title: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration" Status in ceph package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Status in ceph-osd package in Juju Charms Collection: Invalid Bug description: The "ceph/default," "ceph_radosgw/simple_nonha" and "ceph/harden" mojo specs @ Yakkety are failing like so: Units are consistently blocked in Juju status: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration" Snippets from ceph-osd unit syslog: mkjournal error creating journal on /var/lib/ceph/tmp/mnt.W59Jhd/journal: (13) Permission denied Oct 7 03:13:30 juju-osci-sv13-machine-4 systemd[1]: Failed to start Ceph disk activation: /dev/vdb1. See: http://pastebin.ubuntu.com/23288515/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1631328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629102] Re: Unable to start or initialise any ceph process (ceph-mon)
No, the packages in:
https://launchpad.net/~openstack-ubuntu-testing/+archive/ubuntu/ceph-
sru/+build/10968224
where built using the 4.1ubuntu1 version from the archive and have the
same symptom.
The dependency is via google-perftools rather that direct from ceph.
** Changed in: ceph (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/1629102
Title:
Unable to start or initialise any ceph process (ceph-mon)
Status in ceph package in Ubuntu:
New
Status in google-perftools package in Ubuntu:
Invalid
Status in libunwind package in Ubuntu:
New
Bug description:
Latest yakkety server build, with ceph 10.2.2; creation of the ceph-
mon FS hangs:
ceph-mon --mkfs -i juju-
3da7bf0b-0062-4a2f-8949-d85e6579b759-machine-15 --keyring
/var/lib/ceph/tmp/juju-
3da7bf0b-0062-4a2f-8949-d85e6579b759-machine-15.mon.keyring
spinning in:
nanosleep({0, 201}, NULL) = 0
top of backtrace:
#0 0x7f5a619efd10 in __nanosleep_nocancel () at
../sysdeps/unix/syscall-template.S:84
No locals.
#1 0x7f5a624b9193 in base::internal::SpinLockDelay(int volatile*, int,
int) () from /usr/lib/libtcmalloc.so.4
No symbol table info available.
#2 0x7f5a624b9026 in SpinLock::SlowLock() () from
/usr/lib/libtcmalloc.so.4
No symbol table info available.
#3 0x7f5a624adb78 in tcmalloc::ThreadCache::InitModule() () from
/usr/lib/libtcmalloc.so.4
No symbol table info available.
#4 0x7f5a624bbe55 in tc_malloc () from /usr/lib/libtcmalloc.so.4
No symbol table info available.
#5 0x7f5a5fc05f7d in __fopen_internal (filename=0x7f5a6291c4a0
"/usr/lib/libtcmalloc.so.4", mode=0x7f5a5f984c6a "r", is32=1) at iofopen.c:69
new_f =
#6 0x7f5a5f982ab8 in ?? () from /usr/lib/x86_64-linux-gnu/libunwind.so.8
No symbol table info available.
#7 0x7f5a5f983624 in ?? () from /usr/lib/x86_64-linux-gnu/libunwind.so.8
No symbol table info available.
#8 0x7f5a5f983710 in _ULx86_64_dwarf_find_debug_frame () from
/usr/lib/x86_64-linux-gnu/libunwind.so.8
No symbol table info available.
#9 0x7f5a5f983cde in ?? () from /usr/lib/x86_64-linux-gnu/libunwind.so.8
No symbol table info available.
#10 0x7f5a5fcdc0a4 in __GI___dl_iterate_phdr (callback=0x7f5a5f983940,
data=0x7fff3a02ba90) at dl-iteratephdr.c:76
__clframe = {__cancel_routine = , __cancel_arg = 0x0,
__do_it = 1, __cancel_type = }
nloaded = 26
ns =
caller =
l = 0x7f5a6291c4c0
info = {dlpi_addr = 140026172706816, dlpi_name = 0x7f5a6291c4a0
"/usr/lib/libtcmalloc.so.4", dlpi_phdr = 0x7f5a62489040, dlpi_phnum = 8,
dlpi_adds = 26, dlpi_subs = 0, dlpi_tls_modid = 2, dlpi_tls_data =
0x7f5a62906760}
ret = 0
looks like initial setup of tcmalloc is spinning - I've seen the same happen
on start of the ceph-mon daemon (which I thought was the original problem).
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ceph-mon 10.2.2-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Thu Sep 29 20:43:51 2016
Ec2AMI: ami-045c
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small.osci
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: ceph
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1629102/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629102] Re: Unable to start or initialise any ceph process (ceph-mon)
I reverted that change and uploaded to:
https://launchpad.net/~openstack-ubuntu-testing/+archive/ubuntu/ceph-
sru
to test and confirm that appears to resolve this problem for me.
** Changed in: google-perftools (Ubuntu)
Status: New => Invalid
** Changed in: libunwind (Ubuntu)
Importance: Undecided => High
** Changed in: ceph (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/1629102
Title:
Unable to start or initialise any ceph process (ceph-mon)
Status in ceph package in Ubuntu:
Invalid
Status in google-perftools package in Ubuntu:
Invalid
Status in libunwind package in Ubuntu:
New
Bug description:
Latest yakkety server build, with ceph 10.2.2; creation of the ceph-
mon FS hangs:
ceph-mon --mkfs -i juju-
3da7bf0b-0062-4a2f-8949-d85e6579b759-machine-15 --keyring
/var/lib/ceph/tmp/juju-
3da7bf0b-0062-4a2f-8949-d85e6579b759-machine-15.mon.keyring
spinning in:
nanosleep({0, 201}, NULL) = 0
top of backtrace:
#0 0x7f5a619efd10 in __nanosleep_nocancel () at
../sysdeps/unix/syscall-template.S:84
No locals.
#1 0x7f5a624b9193 in base::internal::SpinLockDelay(int volatile*, int,
int) () from /usr/lib/libtcmalloc.so.4
No symbol table info available.
#2 0x7f5a624b9026 in SpinLock::SlowLock() () from
/usr/lib/libtcmalloc.so.4
No symbol table info available.
#3 0x7f5a624adb78 in tcmalloc::ThreadCache::InitModule() () from
/usr/lib/libtcmalloc.so.4
No symbol table info available.
#4 0x7f5a624bbe55 in tc_malloc () from /usr/lib/libtcmalloc.so.4
No symbol table info available.
#5 0x7f5a5fc05f7d in __fopen_internal (filename=0x7f5a6291c4a0
"/usr/lib/libtcmalloc.so.4", mode=0x7f5a5f984c6a "r", is32=1) at iofopen.c:69
new_f =
#6 0x7f5a5f982ab8 in ?? () from /usr/lib/x86_64-linux-gnu/libunwind.so.8
No symbol table info available.
#7 0x7f5a5f983624 in ?? () from /usr/lib/x86_64-linux-gnu/libunwind.so.8
No symbol table info available.
#8 0x7f5a5f983710 in _ULx86_64_dwarf_find_debug_frame () from
/usr/lib/x86_64-linux-gnu/libunwind.so.8
No symbol table info available.
#9 0x7f5a5f983cde in ?? () from /usr/lib/x86_64-linux-gnu/libunwind.so.8
No symbol table info available.
#10 0x7f5a5fcdc0a4 in __GI___dl_iterate_phdr (callback=0x7f5a5f983940,
data=0x7fff3a02ba90) at dl-iteratephdr.c:76
__clframe = {__cancel_routine = , __cancel_arg = 0x0,
__do_it = 1, __cancel_type = }
nloaded = 26
ns =
caller =
l = 0x7f5a6291c4c0
info = {dlpi_addr = 140026172706816, dlpi_name = 0x7f5a6291c4a0
"/usr/lib/libtcmalloc.so.4", dlpi_phdr = 0x7f5a62489040, dlpi_phnum = 8,
dlpi_adds = 26, dlpi_subs = 0, dlpi_tls_modid = 2, dlpi_tls_data =
0x7f5a62906760}
ret = 0
looks like initial setup of tcmalloc is spinning - I've seen the same happen
on start of the ceph-mon daemon (which I thought was the original problem).
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ceph-mon 10.2.2-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Thu Sep 29 20:43:51 2016
Ec2AMI: ami-045c
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small.osci
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: ceph
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1629102/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629102] Re: Unable to start or initialise any ceph process (ceph-mon)
Reverting back to libunwind 1.1-4.1 resolves this problem for me - the
changelog entry is:
libunwind (1.1-4.1ubuntu1) yakkety; urgency=medium
* Configure with --enable-debug-frame. LP: #1590236.
-- Matthias Klose Mon, 19 Sep 2016 13:28:08 +0200
ceph was functional on yakkety not that long ago (this landed into
updates on the 28th).
** Also affects: libunwind (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/1629102
Title:
Unable to start or initialise any ceph process (ceph-mon)
Status in ceph package in Ubuntu:
New
Status in google-perftools package in Ubuntu:
New
Status in libunwind package in Ubuntu:
New
Bug description:
Latest yakkety server build, with ceph 10.2.2; creation of the ceph-
mon FS hangs:
ceph-mon --mkfs -i juju-
3da7bf0b-0062-4a2f-8949-d85e6579b759-machine-15 --keyring
/var/lib/ceph/tmp/juju-
3da7bf0b-0062-4a2f-8949-d85e6579b759-machine-15.mon.keyring
spinning in:
nanosleep({0, 201}, NULL) = 0
top of backtrace:
#0 0x7f5a619efd10 in __nanosleep_nocancel () at
../sysdeps/unix/syscall-template.S:84
No locals.
#1 0x7f5a624b9193 in base::internal::SpinLockDelay(int volatile*, int,
int) () from /usr/lib/libtcmalloc.so.4
No symbol table info available.
#2 0x7f5a624b9026 in SpinLock::SlowLock() () from
/usr/lib/libtcmalloc.so.4
No symbol table info available.
#3 0x7f5a624adb78 in tcmalloc::ThreadCache::InitModule() () from
/usr/lib/libtcmalloc.so.4
No symbol table info available.
#4 0x7f5a624bbe55 in tc_malloc () from /usr/lib/libtcmalloc.so.4
No symbol table info available.
#5 0x7f5a5fc05f7d in __fopen_internal (filename=0x7f5a6291c4a0
"/usr/lib/libtcmalloc.so.4", mode=0x7f5a5f984c6a "r", is32=1) at iofopen.c:69
new_f =
#6 0x7f5a5f982ab8 in ?? () from /usr/lib/x86_64-linux-gnu/libunwind.so.8
No symbol table info available.
#7 0x7f5a5f983624 in ?? () from /usr/lib/x86_64-linux-gnu/libunwind.so.8
No symbol table info available.
#8 0x7f5a5f983710 in _ULx86_64_dwarf_find_debug_frame () from
/usr/lib/x86_64-linux-gnu/libunwind.so.8
No symbol table info available.
#9 0x7f5a5f983cde in ?? () from /usr/lib/x86_64-linux-gnu/libunwind.so.8
No symbol table info available.
#10 0x7f5a5fcdc0a4 in __GI___dl_iterate_phdr (callback=0x7f5a5f983940,
data=0x7fff3a02ba90) at dl-iteratephdr.c:76
__clframe = {__cancel_routine = , __cancel_arg = 0x0,
__do_it = 1, __cancel_type = }
nloaded = 26
ns =
caller =
l = 0x7f5a6291c4c0
info = {dlpi_addr = 140026172706816, dlpi_name = 0x7f5a6291c4a0
"/usr/lib/libtcmalloc.so.4", dlpi_phdr = 0x7f5a62489040, dlpi_phnum = 8,
dlpi_adds = 26, dlpi_subs = 0, dlpi_tls_modid = 2, dlpi_tls_data =
0x7f5a62906760}
ret = 0
looks like initial setup of tcmalloc is spinning - I've seen the same happen
on start of the ceph-mon daemon (which I thought was the original problem).
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ceph-mon 10.2.2-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Thu Sep 29 20:43:51 2016
Ec2AMI: ami-045c
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small.osci
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: ceph
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1629102/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508767] Re: IBM POWER8 unhandled signal 11 / SEGV
Marking UCA bug task as Invalid; is this an ongoing issue still? the bug has not been updated in 10 months so I'm assuming either something got fixed, or everyone has moved onto something else. ** Changed in: cloud-archive Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: Invalid Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: Confirmed Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signa
[Touch-packages] [Bug 1455097] Re: /etc/pm/sleep.d/ is no more processed
** Changed in: ceph (Ubuntu) Status: New => Fix Committed ** Changed in: ceph (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1455097 Title: /etc/pm/sleep.d/ is no more processed Status in aiccu package in Ubuntu: New Status in ceph package in Ubuntu: Fix Committed Status in grub2 package in Ubuntu: New Status in ifplugd package in Ubuntu: New Status in lizardfs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in pm-utils package in Ubuntu: Won't Fix Status in toshset package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: New Bug description: I added a new script in /etc/pm/sleep.d/ that worked fine before the upgrade to vivid. I was wondering why it doesn't work and I find out that /var/log/pm-suspend.log is empty, and pm-powersave.log too (last logs from pm-suspend were on Apr 28, when I upgraded from utopic to vivid. The laptop suspends and wakes fine, it just seems that no pm scripts are run after suspend/powersave. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pm-utils 1.4.1-15 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 14 15:36:26 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-12 (792 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1455097/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1591382] Re: [SRU] Add support for newton cloud-archive
Its the OpenStack Newton release archive for Ubuntu 16.04; it contains backports of all the packages required to run OpenStack Newton from the Yakkety release -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1591382 Title: [SRU] Add support for newton cloud-archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Yakkety: Fix Released Bug description: Please add support for: cloud-archive:newton cloud-archive:newton-proposed This will also need to be SRU'ed back to xenial. [Impact] End users have to manually enable the newton cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:newton sudo add-apt-repository cloud-archive:newton-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1591382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1581065] Re: incorrect parsing of != dependency versions
Our newton testing PPA is running with proposed enabled and builds are coming through just fine: https://launchpad.net/~openstack-ubuntu- testing/+archive/ubuntu/newton/+packages Note that we did have a wedge in the PPA to workaround this problem; I checked the build logs for the last heat builds and confirmed they are using the version from xenial-proposed. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1581065 Title: incorrect parsing of != dependency versions Status in dh-python package in Ubuntu: Fix Released Status in dh-python source package in Xenial: Fix Committed Status in dh-python source package in Yakkety: Fix Released Bug description: [Impact] dh-python incorrectly used != version operators in some cases, resulting in failed package builds; this impacts a number of stable updates for Xenial which blacklist a specific cryptography version. [Test Case] Build stable release of glance/keystone/nova for xenial/mitaka (parse problem in original bug report) [Regression Potential] Testing OK in yakkety; change is minimal and ensures != operator is ignored when detected. [Original Bug Report] Some updates to requirements for openstack projects (glance and keystone specifically) is causing dh-python to incorrectly generate a != version dependency; this is the requires.txt entry: cryptography!=1.3.0,>=1.0 which causes (utimately): dpkg-gencontrol: warning: can't parse dependency python-cryptography (!= 1.3.0) from the generated dependency line: "python-castellan, python-crypto (>= 2.6), python-cryptography (!= 1.3.0), python-debtcollector, python-eventlet, python-futurist, python-glance-store, python-httplib2, python-iso8601, python- jsonschema, python-keystoneauth1, python-keystoneclient, python- keystonemiddleware, python-migrate, python-monotonic, python-openssl, python-oslo.concurrency, python-oslo.config, python-oslo.context, python-oslo.db, python-oslo.i18n, python-oslo.log, python- oslo.messaging, python-oslo.middleware, python-oslo.policy, python- oslo.serialization, python-oslo.service, python-oslo.utils, python- osprofiler, python-paste, python-pastedeploy, python-pbr, python- prettytable, python-retrying, python-semantic-version, python-six (>= 1.9.0), python-sqlalchemy (>= 1.0~), python-sqlalchemy (<< 1.1), python-stevedore, python-taskflow, python-webob, python-wsme, python:any (<< 2.8), python:any (>= 2.6~), python:any (>= 2.7.5-5~), python:any (>= 2.7~)," ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dh-python 2.20151103ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 12 15:15:36 2016 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-17 (115 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) PackageArchitecture: all SourcePackage: dh-python UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1581065/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582813] Re: service --status-all always reports upstart managed daemons as running
linked bug 1581171 impacts pretty much every openstack charm running on a trusty install. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1582813 Title: service --status-all always reports upstart managed daemons as running Status in lsb package in Ubuntu: Confirmed Bug description: The change to lsb-base that landed into -updates on the 12th of May: lsb (4.1+Debian11ubuntu6.1) trusty; urgency=medium * Add 01-upstart-lsb from the upstart package and make executing rc.d scripts no-op if there is an upstart job for that script. (LP: #1273462) -- Zhang Hua Thu, 06 Aug 2015 11:11:16 -0500 changed the behaviour of init.d scripts to pass through to the associated upstart configuration for process management, where packages ship both an upstart configuration and an init.d configuration. This has a rather nasty side effect on 'service --status-all', which calls the 'status' method on all installed init.d scripts - this gets translated into: status for upstart scripts, which correctly identifies the process as not running, but always returns a 0 return code. As a result, --status-all incorrectly identifies upstart processes as running even when they are not. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lsb-base 4.1+Debian11ubuntu6.1 ProcVersionSignature: User Name 3.13.0-86.130-generic 3.13.11-ckt39 Uname: Linux 3.13.0-86-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Tue May 17 16:47:30 2016 Dependencies: Ec2AMI: ami-015b Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small.osci Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all SourcePackage: lsb UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1582813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
