[Touch-packages] [Bug 1727063] Re: Pacemaker package upgrades stop but fail to start pacemaker resulting in HA outage
** Tags added: uosci -- 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: Fix Released 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 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
Right, it's just an example. Replace with `sudo virt-manager` equally. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: New Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: New Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: Posting here what gnome says about porting to wayland, and their tests: GNOME Applications under Wayland GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a GTK+ application under Wayland simply by: GDK_BACKEND=wayland gnome-calculator Applications that use Clutter or clutter-gtk also need the Clutter Wayland backend enabled: GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese https://wiki.gnome.org/Initiatives/Wayland/Applications ==> so hope the settings are well set at compile time; maybe a rebuilt to get sure all apps are ok. Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu7 Architecture: i386 CurrentDesktop: GNOME Date: Sun Aug 27 14:23:14 2017 InstallationDate: Installed on 2017-08-26 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) PackageArchitecture: all SourcePackage:
[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
Raised https://bugs.launchpad.net/ubuntu/+source/x11-xserver- utils/+bug/1724748 which I think is actually a dup of this existing bug. Here's what I'm seeing: All (most?) gui apps fail to launch when using sudo, out-of-box, desktop 17.10 install. For example, gparted and virt-manager, which both require sudo, are not usable without a work-around. Out-of-box experience rbeisner@vistula:~⟫ sudo gedit No protocol specified Unable to init server: Could not connect: Connection refused (gedit:32146): Gtk-WARNING **: cannot open display: :0 rbeisner@vistula:~⟫ xhost access control enabled, only authorized clients can connect SI:localuser:rbeisner Work-around: rbeisner@vistula:~⟫ xhost si:localuser:root localuser:root being added to access control list rbeisner@vistula:~⟫ xhost access control enabled, only authorized clients can connect SI:localuser:root SI:localuser:rbeisner rbeisner@vistula:~⟫ sudo gedit rbeisner@vistula:~⟫ # (it launches ok) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: New Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: New Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: Posting here what gnome says about porting to wayland, and their tests: GNOME Applications under Wayland GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a GTK+ application under Wayland simply by: GDK_BACKEND=wayland gnome-calculator Applications that use Clutter or clutter-gtk also need the Clutter Wayland backend enabled: GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese https://wiki.gnome.org/Initiatives/Wayland/Applications ==> so hope the settings are well set at compile time; maybe a rebuilt to get sure all apps are ok. Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back
[Touch-packages] [Bug 1665598] Re: python-crypto throws exception ValueError: CTR mode needs counter parameter, not IV
** Changed in: charm-test-infra Milestone: None => 17.05 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1665598 Title: python-crypto throws exception ValueError: CTR mode needs counter parameter, not IV Status in OpenStack Charm Test Infra: Fix Released Status in python-crypto package in Ubuntu: Fix Released Bug description: We've recently upgraded python-crypto package on 14.04 due to this USN https://www.ubuntu.com/usn/usn-3199-1/ apt history log ``` Start-Date: 2017-02-16 23:43:48 Commandline: apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef dist-upgrade Upgrade: bind9-host:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), liblwres90:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), python-crypto:amd64 (2.6.1-4build1, 2.6.1-4ubuntu0.1), libdns100:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisccfg90:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libbind9-90:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), bind9:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), dnsutils:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), bind9utils:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisccc90:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisc95:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13) End-Date: 2017-02-16 23:43:52 ``` Then our python script which uses paramiko failed with this exception ``` Traceback (most recent call last): File "/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", line 1583, in run self.kex_engine.parse_next(ptype, m) File "/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/kex_group1.py", line 68, in parse_next return self._parse_kexdh_reply(m) File "/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/kex_group1.py", line 107, in _parse_kexdh_reply self.transport._activate_outbound() File "/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", line 1881, in _activate_outbound engine = self._get_cipher(self.local_cipher, key_out, IV_out) File "/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", line 1500, in _get_cipher return self._cipher_info[name]['class'].new(key, self._cipher_info[name]['mode'], iv, counter) File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 94, in new return AESCipher(key, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 59, in __init__ blockalgo.BlockAlgo.__init__(self, _AES, key, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/blockalgo.py", line 141, in __init__ self._cipher = factory.new(key, *args, **kwargs) ValueError: CTR mode needs counter parameter, not IV ``` packages versions ``` pycrypto==2.6.1 paramiko==1.12.0 ``` which works okay BEFORE the upgrade. Maybe Debian bug report: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=850025 To manage notifications about this bug go to: https://bugs.launchpad.net/charm-test-infra/+bug/1665598/+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 1638695] Re: Python 2.7.12 performance regression
** Tags added: uosci -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1638695 Title: Python 2.7.12 performance regression Status in python2.7 package in Ubuntu: Confirmed Bug description: I work on the OpenStack-Ansible project and we've noticed that testing jobs on 16.04 take quite a bit longer to complete than on 14.04. They complete within an hour on 14.04 but they normally take 90 minutes or more on 16.04. We use the same version of Ansible with both versions of Ubuntu. After more digging, I tested python performance (using the 'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12). There is a significant performance difference between each version of python. That is detailed in a spreadsheet[0]. I began using perf to dig into the differences when running the python performance module and when using Ansible playbooks. CPU migrations (as measured by perf) are doubled in Ubuntu 16.04 when running the same python workloads. I tried changing some of the kerne.sched sysctl configurables but they had very little effect on the results. I compiled python 2.7.12 from source on 14.04 and found the performance to be unchanged there. I'm not entirely sure where the problem might be now. We also have a bug open in OpenStack-Ansible[1] that provides additional detail. Thanks in advance for any help you can provide! [0] https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing [1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+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 1665598] Re: python-crypto throws exception ValueError: CTR mode needs counter parameter, not IV
** Changed in: charm-test-infra Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1665598 Title: python-crypto throws exception ValueError: CTR mode needs counter parameter, not IV Status in OpenStack Charm Test Infra: Fix Released Status in python-crypto package in Ubuntu: Fix Released Bug description: We've recently upgraded python-crypto package on 14.04 due to this USN https://www.ubuntu.com/usn/usn-3199-1/ apt history log ``` Start-Date: 2017-02-16 23:43:48 Commandline: apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef dist-upgrade Upgrade: bind9-host:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), liblwres90:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), python-crypto:amd64 (2.6.1-4build1, 2.6.1-4ubuntu0.1), libdns100:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisccfg90:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libbind9-90:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), bind9:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), dnsutils:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), bind9utils:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisccc90:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisc95:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13) End-Date: 2017-02-16 23:43:52 ``` Then our python script which uses paramiko failed with this exception ``` Traceback (most recent call last): File "/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", line 1583, in run self.kex_engine.parse_next(ptype, m) File "/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/kex_group1.py", line 68, in parse_next return self._parse_kexdh_reply(m) File "/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/kex_group1.py", line 107, in _parse_kexdh_reply self.transport._activate_outbound() File "/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", line 1881, in _activate_outbound engine = self._get_cipher(self.local_cipher, key_out, IV_out) File "/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", line 1500, in _get_cipher return self._cipher_info[name]['class'].new(key, self._cipher_info[name]['mode'], iv, counter) File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 94, in new return AESCipher(key, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 59, in __init__ blockalgo.BlockAlgo.__init__(self, _AES, key, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/blockalgo.py", line 141, in __init__ self._cipher = factory.new(key, *args, **kwargs) ValueError: CTR mode needs counter parameter, not IV ``` packages versions ``` pycrypto==2.6.1 paramiko==1.12.0 ``` which works okay BEFORE the upgrade. Maybe Debian bug report: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=850025 To manage notifications about this bug go to: https://bugs.launchpad.net/charm-test-infra/+bug/1665598/+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 1665598] Re: python-crypto throws exception ValueError: CTR mode needs counter parameter, not IV
See related: https://bugs.launchpad.net/ubuntu/+source/paramiko/+bug/1665565 ** Tags added: uosci ** Also affects: charm-test-infra Importance: Undecided Status: New ** Changed in: charm-test-infra Status: New => Confirmed ** Changed in: charm-test-infra Importance: Undecided => Critical ** Changed in: charm-test-infra Assignee: (unassigned) => Ryan Beisner (1chb1n) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1665598 Title: python-crypto throws exception ValueError: CTR mode needs counter parameter, not IV Status in OpenStack Charm Test Infra: Confirmed Status in python-crypto package in Ubuntu: Confirmed Bug description: We've recently upgraded python-crypto package on 14.04 due to this USN https://www.ubuntu.com/usn/usn-3199-1/ apt history log ``` Start-Date: 2017-02-16 23:43:48 Commandline: apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef dist-upgrade Upgrade: bind9-host:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), liblwres90:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), python-crypto:amd64 (2.6.1-4build1, 2.6.1-4ubuntu0.1), libdns100:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisccfg90:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libbind9-90:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), bind9:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), dnsutils:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), bind9utils:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisccc90:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13), libisc95:amd64 (9.9.5.dfsg-3ubuntu0.12, 9.9.5.dfsg-3ubuntu0.13) End-Date: 2017-02-16 23:43:52 ``` Then our python script which uses paramiko failed with this exception ``` Traceback (most recent call last): File "/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", line 1583, in run self.kex_engine.parse_next(ptype, m) File "/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/kex_group1.py", line 68, in parse_next return self._parse_kexdh_reply(m) File "/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/kex_group1.py", line 107, in _parse_kexdh_reply self.transport._activate_outbound() File "/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", line 1881, in _activate_outbound engine = self._get_cipher(self.local_cipher, key_out, IV_out) File "/usr/local/nagios/local/lib/python2.7/site-packages/paramiko/transport.py", line 1500, in _get_cipher return self._cipher_info[name]['class'].new(key, self._cipher_info[name]['mode'], iv, counter) File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 94, in new return AESCipher(key, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 59, in __init__ blockalgo.BlockAlgo.__init__(self, _AES, key, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/Crypto/Cipher/blockalgo.py", line 141, in __init__ self._cipher = factory.new(key, *args, **kwargs) ValueError: CTR mode needs counter parameter, not IV ``` packages versions ``` pycrypto==2.6.1 paramiko==1.12.0 ``` which works okay BEFORE the upgrade. Maybe Debian bug report: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=850025 To manage notifications about this bug go to: https://bugs.launchpad.net/charm-test-infra/+bug/1665598/+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 1661869] Re: maas install fails inside of a 16.04 lxd container due to avahi problems
FWIW - I'm using MAAS 2.1.3+bzr5573-0ubuntu1 (16.04.1) in a LXD container successfully in production, albeit privileged, per https://docs.ubuntu.com/maas/2.1/en/installconfig-lxd-install. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1661869 Title: maas install fails inside of a 16.04 lxd container due to avahi problems Status in MAAS: Invalid Status in avahi package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Invalid Bug description: The bug, and workaround, are clearly described in this mailing list thread: https://lists.linuxcontainers.org/pipermail/lxc- users/2016-January/010791.html I'm trying to install MAAS in a LXD container, but that's failing due to avahi package install problems. I'm tagging all packages here. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1661869/+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 1355813] Re: Interface MTU management across MAAS/juju
** Tags added: uosci -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1355813 Title: Interface MTU management across MAAS/juju Status in juju-core: Fix Released Status in MAAS: Triaged Status in juju-core package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Invalid Bug description: Context: juju + MAAS deployed OpenStack environment, misc services deployed under LXC on the bootstrap node, interfaces configured for jumbo frames - note that I had to manually set the LXC container interfaces to mtu 9000 before the bridge would do the same. Action: Reboot one of the containers; MTU on br0 resets from 9000 -> 1500. This feels like more of a 'we need a better way to orchestrate MTU configuration across different services' so raising tasks for MAAS and Juju as well. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.5-0ubuntu0.1 ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 12 13:26:00 2014 KernLog: SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxcsyslog: To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+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 1539546] [NEW] Service mountdevsubfs has to be enabled to start service lvm2
Public bug reported: Xenial daily cloud image 20160129: insserv: Service mountdevsubfs has to be enabled to start service lvm2 This is causing juju bootstraps to fail on Xenial. http://pastebin.ubuntu.com/14694925/ lvm2: Installed: 2.02.133-1ubuntu4 Candidate: 2.02.133-1ubuntu4 Version table: *** 2.02.133-1ubuntu4 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status # from cloudinit log Setting up lvm2 (2.02.133-1ubuntu4) ... update-initramfs: deferring update (trigger activated) insserv: Service mountdevsubfs has to be enabled to start service lvm2 insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package lvm2 (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for initramfs-tools (0.120ubuntu7) ... update-initramfs: Generating /boot/initrd.img-4.3.0-7-generic W: plymouth: The plugin label.so is missing, the selected theme might not work as expected. W: plymouth: You might want to install the plymouth-themes and plymouth-label package to fix this. W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up lvm2 (2.02.133-1ubuntu4) ... update-initramfs: deferring update (trigger activated) insserv: Service mountdevsubfs has to be enabled to start service lvm2 insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package lvm2 (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for initramfs-tools (0.120ubuntu7) ... update-initramfs: Generating /boot/initrd.img-4.3.0-7-generic W: plymouth: The plugin label.so is missing, the selected theme might not work as expected. W: plymouth: You might want to install the plymouth-themes and plymouth-label package to fix this. W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: uosci -- 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/1539546 Title: Service mountdevsubfs has to be enabled to start service lvm2 Status in lvm2 package in Ubuntu: New Bug description: Xenial daily cloud image 20160129: insserv: Service mountdevsubfs has to be enabled to start service lvm2 This is causing juju bootstraps to fail on Xenial. http://pastebin.ubuntu.com/14694925/ lvm2: Installed: 2.02.133-1ubuntu4 Candidate: 2.02.133-1ubuntu4 Version table: *** 2.02.133-1ubuntu4 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status # from cloudinit log Setting up lvm2 (2.02.133-1ubuntu4) ... update-initramfs: deferring update (trigger activated) insserv: Service mountdevsubfs has to be enabled to start service lvm2 insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package lvm2 (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for initramfs-tools (0.120ubuntu7) ... update-initramfs: Generating /boot/initrd.img-4.3.0-7-generic W: plymouth: The plugin label.so is missing, the selected theme might not work as expected. W: plymouth: You might want to install the plymouth-themes and plymouth-label package to fix this. W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up lvm2 (2.02.133-1ubuntu4) ... update-initramfs: deferring update (trigger activated) insserv: Service mountdevsubfs has to be enabled to start service lvm2 insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package lvm2 (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for initramfs-tools (0.120ubuntu7) ... update-initramfs: Generating /boot/initrd.img-4.3.0-7-generic W: plymouth: The plugin label.so is
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
Also confirmed via the Ubuntu charm amulet test in uosci, that Wily is deployable again. Thanks, all! http://paste.ubuntu.com/12238490/ -- 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/1480310 Title: systemctl link request failed for service FOO: Unit name FOO is not valid. Status in juju-core: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: As seen in http://reports.vapour.ws/releases/2936/job/local-deploy-wily-amd64/attempt/136 Juju cannot bootstrap on wily because ERROR juju.service.systemd service.go:149 dbus link request failed for service "juju-db-jenkins-local-deploy-wily-amd64": Unit name /var/lib/juju/init/juju-db-jenkins-local-deploy-wily-amd64/juju-db-jenkins-local-deploy-wily-amd64.service is not valid. This error first occurred after the wily-slave got package updates. The released jujus get the same errors as the jujus under test. This issue is probably an Ubuntu packaging break. I am making the test non-voting since we can see table 1.24.3 no longer works. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1480310/+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 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
On Jul 28, uosci was able to deploy Wily @ Juju 1.24.2. Granted, that was with older Wily images and perhaps older systemd, so it may or may not be helpful information at this point. Here is that successful amulet test output from the trusty/ubuntu charm, which exercises all currently-supported Ubuntu releases (+ current dev Ubuntu release): charm_amulet_test/5429: http://paste.ubuntu.com/12193551/ I think it may be of interest to begin cycling the trusty/ubuntu charm's amulet test in Juju CI as an easy way to do a really basic and quick functional check. ie. grab lp:charms/trusty/ubuntu, then make functional_test. The tests are maintained and validated as Ubuntu releases come and go. Note that tests are only added and enabled for Ubuntu dev versions after confirming that they pass for that version. http://bazaar.launchpad.net/~charmers/charms/trusty/ubuntu/trunk/files/head:/tests/ The Ubuntu charm is, and is intended to be, a minimal hookless nothing. That makes it attractive for inexpensive general validation of test automation, environments, tooling and such (which is uosci's specific interest in it). That could also make it attractive for testing Ubuntu releases vs. Juju releases. -- 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/1480310 Title: systemctl link request failed for service FOO: Unit name FOO is not valid. Status in juju-core: Triaged Status in systemd package in Ubuntu: Fix Released Bug description: As seen in http://reports.vapour.ws/releases/2936/job/local-deploy-wily-amd64/attempt/136 Juju cannot bootstrap on wily because ERROR juju.service.systemd service.go:149 dbus link request failed for service juju-db-jenkins-local-deploy-wily-amd64: Unit name /var/lib/juju/init/juju-db-jenkins-local-deploy-wily-amd64/juju-db-jenkins-local-deploy-wily-amd64.service is not valid. This error first occurred after the wily-slave got package updates. The released jujus get the same errors as the jujus under test. This issue is probably an Ubuntu packaging break. I am making the test non-voting since we can see table 1.24.3 no longer works. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1480310/+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 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
FYI duplicate was @ https://bugs.launchpad.net/juju-core/+bug/1488554. Thanks for pointing it here. -- 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/1480310 Title: systemctl link request failed for service FOO: Unit name FOO is not valid. Status in juju-core: Triaged Status in systemd package in Ubuntu: Fix Released Bug description: As seen in http://reports.vapour.ws/releases/2936/job/local-deploy-wily-amd64/attempt/136 Juju cannot bootstrap on wily because ERROR juju.service.systemd service.go:149 dbus link request failed for service juju-db-jenkins-local-deploy-wily-amd64: Unit name /var/lib/juju/init/juju-db-jenkins-local-deploy-wily-amd64/juju-db-jenkins-local-deploy-wily-amd64.service is not valid. This error first occurred after the wily-slave got package updates. The released jujus get the same errors as the jujus under test. This issue is probably an Ubuntu packaging break. I am making the test non-voting since we can see table 1.24.3 no longer works. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1480310/+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 1389239] Re: apparmor is uninstalled when deploying icehouse nova-compute on Precise
** Tags added: openstack uosci -- 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/1389239 Title: apparmor is uninstalled when deploying icehouse nova-compute on Precise Status in “apparmor” package in Ubuntu: New Status in “libvirt” package in Ubuntu: New Status in “apparmor” source package in Precise: New Status in “libvirt” source package in Precise: New Bug description: When doing juju deploy nova-compute for icehouse with the latest charm on Ubuntu Precise, the apparmor package is uninstalled. Procedure to reproduce : $ juju switch local $ juju get-env | grep serie default-series: precise $ juju bootstrap $ bzr branch lp:charms/nova-compute $ juju deploy --repository=. local:nova-compute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1389239/+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
