[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.

[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

[Touch-packages] [Bug 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12

hon-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 t

[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

[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.

[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

[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

[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

[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

[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

[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

[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

[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

[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.

[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.

[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

[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

[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.

[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

[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

[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

[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

[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

[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')]

[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.

[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)

[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

[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

[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

[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

[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

[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.

[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

[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-*",

[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

[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

[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.

[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:

[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

[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

[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

[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

[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

[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

[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

[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

[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. --

[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

[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

[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

[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

[Touch-packages] [Bug 1794229] Re: python packages should not ship colliding /usr/lib/python3/dist-packages/.pytest_cache

: 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

[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

[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.

[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

[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

[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.

[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

[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

[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.

[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

[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

[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

[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.

[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:

[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

[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

[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

[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

[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 [

[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

[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 возвратил код

[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

[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

[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

[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

[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

[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

[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

[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-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.

[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

[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:

[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.

[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.

[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.

[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

[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)

[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)

[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

[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

[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.

[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

[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

[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

[Touch-packages] [Bug 1582813] [NEW] service --status-all always reports upstart managed daemons as running

Public bug reported: 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)  

[Touch-packages] [Bug 1581065] Re: incorrect parsing of != dependency versions

** Description changed: - 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: + [Impact] + dh-python incorrectly used != version operators in some cases,

[Touch-packages] [Bug 1581065] Re: incorrect parsing of != dependency versions

** Also affects: dh-python (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: dh-python (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: dh-python (Ubuntu Xenial) Importance: Undecided => High ** Changed in: dh-python (Ubuntu Yakkety)

[Touch-packages] [Bug 1581065] Re: incorrect parsing of != dependency versions

This fix works: https://launchpadlibrarian.net/259176990/dh- python_2.20151103ubuntu1_2.20151103ubuntu2~ubuntu16.10.1~ppa201605121523.diff.gz but not entirely sure why this gets picked up in the first place. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1581065] Re: incorrect parsing of != dependency versions

** Attachment added: "requires.txt" https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1581065/+attachment/4661294/+files/requires.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu.

  1   2   3   >