[Bug 1425431] Re: Pacemaker [SIGSEGV - Segmentation violation] using with Heartbeat 3.x
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pacemaker (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1425431 Title: Pacemaker [SIGSEGV - Segmentation violation] using with Heartbeat 3.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1425431/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1432062] Re: Ship the default /etc/multipath.conf on multipath-tools-boot (for user_friendly_names)
BTW, I have prototype patches to fix the spacing issue in udev rules (pathes for kpartx.rules, multipath.rules, and kpartx_id IIRC) But I guess that at this point of the schedule it'd be safer to go w/ shipping a default thing which could have been installed, rather than changing stuff at the udev rules level. The problem seems to emerge from the general dm.rules, which on recent kernels will set DM_NAME as the mangled name which is obtained from sysfs/.../dm/name, but some Debian-specific thing related to dmsetup not exporting variables correctly will re-set DM_NAME to a non-mangled name.. this is leading to problem in the rest of that rules file.. Also, kpartx_id IIRC-2 gets a non-mangled name, in variable dmname IIRC-3.) I can provide those patches if you're interested in taking a look. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1432062 Title: Ship the default /etc/multipath.conf on multipath-tools-boot (for user_friendly_names) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1432062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1380080] Re: Cannot make directory '/var/run/screen': Permission denied (convert init to upstart)
Mmm.. and don't forget to remove the old defaults for your script first. (as in: update-rc.d minecraft remove) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to screen in Ubuntu. https://bugs.launchpad.net/bugs/1380080 Title: Cannot make directory '/var/run/screen': Permission denied (convert init to upstart) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1380080/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 574773] Re: Cannot make directory '/var/run/screen': Permission denied (convert init to upstart)
In fact, look here: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1380080 for a possible solution. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to screen in Ubuntu. https://bugs.launchpad.net/bugs/574773 Title: Cannot make directory '/var/run/screen': Permission denied (convert init to upstart) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/574773/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1380080] Re: Cannot make directory '/var/run/screen': Permission denied (convert init to upstart)
NOTE - the issue is easily fixed (at least for me). I want to run my minecraft script (like others that seem to find this thread just like I did) which requires screen. However the default priority for my script would be the same (i.e. 20) as the one for screen (which also is going to be in the same rc.d folders) and since 'm' comes before 's' - it will attempt to kick off first - and fail. Solution: when updating rc.d - specify later and earlier priorities for your scripts startup and shutdown than the requirements might have. In my case "sudo update-rc.d minecraft defaults 99 10" works like a charm. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to screen in Ubuntu. https://bugs.launchpad.net/bugs/1380080 Title: Cannot make directory '/var/run/screen': Permission denied (convert init to upstart) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1380080/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1432062] [NEW] Ship the default /etc/multipath.conf on multipath-tools-boot (for user_friendly_names)
Public bug reported: If a system is not installed w/ multipath support (i.e., no disk-detect/multipath/enable=true), the /etc/multipath.conf file is not installed. If an user later installs multipath-tools-boot, it will enable the udev rules for multipath support. Those rules don't handle disk devices w/ spaces on their names/uuids/models very well.. That's because of udev's SYMLINK command using spaces to separate multiple links, and the kernel sysfs/dm informing \x20 instead, which is not correctly interpreted by some commands, resulting in file not found errors, for example. Thus, the system fails to boot. There's no problem, however, if user_friendly_names is enabled in multipath.conf (which is enabled in the default multipath.conf from the installer, if it has multipath enabled). Notice it's an acceptable case to install w/out multipath support, and enable it later for booting. Disk devices w/ spaces in naming is not common over SAN/storage systems, but that happens often for conventional disks; for example: - IBM IPR ( IBM IPR-0 5DB6F480 ) - IBM VDASD ( AIX VDASD 00c96f074c00014bb8e713f0.14 ) - QEMU HARDDISK ( QEMU QEMU HARDDISK ) So, please, is it possible to ship the default multipath.conf (e.g., from installer) w/ multipath-tools-boot? For users not to their systems failing to boot after installing multipath-tools-boot manually, after a non-multipath install. ** Affects: multipath-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1432062 Title: Ship the default /etc/multipath.conf on multipath-tools-boot (for user_friendly_names) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1432062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1432060] [NEW] Include SCSI device handlers for improved multipath support (ALUA, RDAC)
Public bug reported: On some SAN storages, the SCSI device handlers ALUA and RDAC help linux to handle much more gracefully some I/O errors resulting from trying to talk to "ghost" paths. Please include those modules (scsi_dh_alua, scsi_dh_rdac) in the initramfs when multipath is enabled (i.e., multipath-tools:debian/hooks/multipath IIRC, on a for-loop that calls manual_add_modules() ). Thanks to Brian King for providing the information. ** Affects: multipath-tools (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Include SCSI device handlers for improved multipath support + Include SCSI device handlers for improved multipath support (ALUA, RDAC) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1432060 Title: Include SCSI device handlers for improved multipath support (ALUA, RDAC) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1432060/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1424042] Re: openstack-dashboard-ubuntu-theme fails to install
** Changed in: horizon (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1424042 Title: openstack-dashboard-ubuntu-theme fails to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1424042/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
Whether this is a bug or feature request, I don't know, but to be sure, it is possible to do this with a .conf file and "sudo service openvpn start" and not possible to do it via network-manager-openvpn (unless you count disabling dnsmasq--I'm curious what side effects this has). As described in the original report, I have verified that these lines in a .conf file allow the server to configure DNS (as long as the server pushes 3 or more DNS servers): script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf but network-manager-openvpn does not support the 'up' and 'down'. This same issue was addressed here: http://askubuntu.com/questions/519920/how-to-run-an-up-script-using- network-manager-openvpn -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1426893] Re: qemu-kvm virtual machines crash with some but not all ubuntu flavors when vmvga video is selected
** Changed in: qemu (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1426893 Title: qemu-kvm virtual machines crash with some but not all ubuntu flavors when vmvga video is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1426893/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1424042] Re: openstack-dashboard-ubuntu-theme fails to install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: horizon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1424042 Title: openstack-dashboard-ubuntu-theme fails to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1424042/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431537] Re: cloud-localds -f vfat fails with "sectors per track" error
** Also affects: cloud-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-utils in Ubuntu. https://bugs.launchpad.net/bugs/1431537 Title: cloud-localds -f vfat fails with "sectors per track" error To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-utils/+bug/1431537/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431533] Re: cloud-localds -f vfat requires Depends: mtools
** Also affects: cloud-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-utils in Ubuntu. https://bugs.launchpad.net/bugs/1431533 Title: cloud-localds -f vfat requires Depends: mtools To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-utils/+bug/1431533/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1422388] Re: Fetch passwords from CloudStack virtual router
verification-done-*; I've tested this cloud-init on Interoute and EC2 successfully. ** Tags removed: verification-needed ** Tags added: verification-done-precise verification-done-trusty verification-done-utopic -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1422388 Title: Fetch passwords from CloudStack virtual router To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1422388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1356855] Re: Cloud-init 0.7.5 Failed to get cloudstack user-data because of trailing slash
Metadata retrieval still works on trusty, marking as verification-done. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1356855 Title: Cloud-init 0.7.5 Failed to get cloudstack user-data because of trailing slash To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1356855/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1356855] Re: Cloud-init 0.7.5 Failed to get cloudstack user-data because of trailing slash
I've tested this version on Interoute (which is a CloudStack cloud). I'll smoke test on another cloud, to ensure that we haven't regressed anything, and then mark this as verification-done. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1356855 Title: Cloud-init 0.7.5 Failed to get cloudstack user-data because of trailing slash To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1356855/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431934] [NEW] FFE: Update djorm-ext-pgarray package to version 1.2 in vivid
Public bug reported: The version currently available in Vivid for djorm-ext-pgarray (0.8) doesn't work with Django 1.7 (the version in Vivid). See bug 1431789 for details. I'd like to get the version 1.2 of djorm-ext-pgarray (https://github.com/niwibe/djorm-pgarray/) into Vivid. ** Affects: djorm-ext-pgarray (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to djorm-ext-pgarray in Ubuntu. https://bugs.launchpad.net/bugs/1431934 Title: FFE: Update djorm-ext-pgarray package to version 1.2 in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djorm-ext-pgarray/+bug/1431934/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1422388] Re: Fetch passwords from CloudStack virtual router
I've tested this version on all relevant versions on Interoute (which is an appropriate CloudStack cloud). I'll smoke test on another cloud, to ensure that we haven't regressed anything, and then mark this as verification-done. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1422388 Title: Fetch passwords from CloudStack virtual router To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1422388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1430109] Re: vmtoolsd does not start automatically after reboot with systemd
I'm taking a look at importing the latest from Debian. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1430109 Title: vmtoolsd does not start automatically after reboot with systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1430109/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1430109] Re: vmtoolsd does not start automatically after reboot with systemd
** Changed in: open-vm-tools (Ubuntu) Assignee: (unassigned) => Ben Howard (utlemming) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1430109 Title: vmtoolsd does not start automatically after reboot with systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1430109/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431650] Re: Multipath devices take long to initialize during initramfs
FYI, this doesn't affect Trusty nor Utopic. That udev code lock code was introduced in 2014-04-14: systemd commit 3ebdb81ef088afd3b4c72b516beb5610f8c93a0d [1] [1] http://cgit.freedesktop.org/systemd/systemd/commit/?id=3ebdb81ef088afd3b4c72b516beb5610f8c93a0d -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1431650 Title: Multipath devices take long to initialize during initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1431650/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431650] Re: Multipath devices take long to initialize during initramfs
The work-around in use: Remove the multipath udev rules from the initramfs. Note: this doesn't remove multipath support from it; there's more in there. Boot from multipath devices works normally (and faster :-) $ grep 'for rules in' /usr/share/initramfs-tools/hooks/multipath for rules in 95-multipath.rules; do $ sudo sed '/for rules in/ s:95-multipath.rules::' -i /usr/share /initramfs-tools/hooks/multipath $ grep 'for rules in' /usr/share/initramfs-tools/hooks/multipath for rules in ; do $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-3.19.0-7-generic $ sudo reboot -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1431650 Title: Multipath devices take long to initialize during initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1431650/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431279] Re: MAAS python scripts do not show the line numbers and the script name when errors are encountered
I tried the following commands maas login maas http://127.0.0.1/MAAS/ 8h77Ye8uEmFEWwqYqr:vTCnwfQzqgdVBv9bRJ:yHuSe5YgAAPHZtkRp6HRgdU8W2tkgy9k maas login ubcloud http://127.0.0.1/MAAS/ 8h77Ye8uEmFEWwqYqr:vTCnwfQzqgdVBv9bRJ:yHuSe5YgAAPHZtkRp6HRgdU8W2tkgy9k maas login ubcloud http://127.0.0.1/MAAS/api/1.0 8h77Ye8uEmFEWwqYqr:vTCnwfQzqgdVBv9bRJ:yHuSe5YgAAPHZtkRp6HRgdU8W2tkgy9k -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1431279 Title: MAAS python scripts do not show the line numbers and the script name when errors are encountered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1431279/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431789] [NEW] ArrayField created with the wrong dbtype with Django 1.7
Public bug reported: Vivid contains Django 1.7 and djorm-ext-pgarray 0.8. djorm-ext-pgarray version 0.8 is not compatible with Django 1.7 migration module. One of the symptoms is that the dbtype of an ArrayField is ignored (and the default dbtype 'int' is used). In other words, when declaring a field like this: djorm_pgarray.fields.ArrayField(default=None, null=True, blank=True, dbtype="text") One ends up with this in the DB: defined as integer[] instead of text[]. (Note that the project has been renamed to djorm-pgarray in version 1.0.) Support for Django 1.7 was added in version 1.0 (see https://github.com/niwibe/djorm-pgarray/blob/master/CHANGES.md). I can confirm that the fields are created correctly with djorm-pgarray 1.0 and Django 1.7. ** Affects: djorm-ext-pgarray (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to djorm-ext-pgarray in Ubuntu. https://bugs.launchpad.net/bugs/1431789 Title: ArrayField created with the wrong dbtype with Django 1.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djorm-ext-pgarray/+bug/1431789/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431279] Re: MAAS python scripts do not show the line numbers and the script name when errors are encountered
What was the exact command that was run? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1431279 Title: MAAS python scripts do not show the line numbers and the script name when errors are encountered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1431279/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431766] [NEW] package cinder-volume 1:2014.2.1-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5
Public bug reported: got this error while installing packages through software updater ProblemType: Package DistroRelease: Ubuntu 14.10 Package: cinder-volume 1:2014.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 Date: Fri Mar 13 10:43:53 2015 DuplicateSignature: package:cinder-volume:1:2014.2.1-0ubuntu1:subprocess new pre-removal script returned error exit status 5 ErrorMessage: subprocess new pre-removal script returned error exit status 5 InstallationDate: Installed on 2015-01-24 (48 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: cinder Title: package cinder-volume 1:2014.2.1-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cinder (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1431766 Title: package cinder-volume 1:2014.2.1-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1431766/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431766] Re: package cinder-volume 1:2014.2.1-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1431766 Title: package cinder-volume 1:2014.2.1-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1431766/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431716] [NEW] "ImportError: cannot import name simplejson" when using piston 0.2.3 with Django 1.7
Public bug reported: In vivid, we have Django 1.7 and piston 0.2.3. Piston 0.2.3 breaks with Django 1.7 because the module django.utils.simplejson has been removed from Django 1.7 (https://docs.djangoproject.com/en/1.7/internals/deprecation /#deprecation-removed-in-1-7). Note that it has been deprecated since Django 1.5 (https://docs.djangoproject.com/en/1.7/releases/1.5/#system- version-of-simplejson-no-longer-used). This patch: https://bitbucket.org/ckarrie/django- piston/commits/024ede7de7179cbe738322f6003c2d8d97d8e2a4 from a fork of piston (AFAIK the "official" upstream piston is unmaintained) fixes the problem. ** Affects: python-django-piston (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-django-piston in Ubuntu. https://bugs.launchpad.net/bugs/1431716 Title: "ImportError: cannot import name simplejson" when using piston 0.2.3 with Django 1.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-django-piston/+bug/1431716/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1423601] Re: [FFe] ceph 0.93 -> hammer release
** Branch linked: lp:ubuntu/vivid-proposed/ceph -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1423601 Title: [FFe] ceph 0.93 -> hammer release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1423601/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431709] [NEW] rsync dies with "inflate returned -3"
Public bug reported: On 12.04.5 64bit server running rsync pulling backups from a 14.04 64bit laptop dies with "inflate returned -3" when using the -z flag on a backup containing a large file (a VM image over 1G). Removing the -z flag works around the issue. See the Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741628 ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Package changed: ubuntu => rsync (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1431709 Title: rsync dies with "inflate returned -3" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1431709/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1431709] [NEW] rsync dies with "inflate returned -3"
You have been subscribed to a public bug: On 12.04.5 64bit server running rsync pulling backups from a 14.04 64bit laptop dies with "inflate returned -3" when using the -z flag on a backup containing a large file (a VM image over 1G). Removing the -z flag works around the issue. See the Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741628 ** Affects: rsync (Ubuntu) Importance: Undecided Status: New -- rsync dies with "inflate returned -3" https://bugs.launchpad.net/bugs/1431709 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rsync in Ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
