[Bug 1915873] [NEW] unable to detect touchpad for asus A450L
Public bug reported: Touchpad able to detect using window but doesnt shows up in proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-43-generic 5.8.0-43.49~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 17 04:02:04 2021 InstallationDate: Installed on 2021-02-16 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915873 Title: unable to detect touchpad for asus A450L To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1915873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
Thanks to nugai's comment#25, this works for me: 1. Create a screen layout in `~/.config/monitors.xml`. 2. Copy the file to `/var/lib/gdm3/.config/` and change ownership: sudo cp ~/.config/monitors.xml /var/lib/gdm3/.config/ sudo chown gdm:gdm /var/lib/gdm3/.config/monitors.xml The monitor layout will persist across restarts and screen locks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874217 Title: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839444] [NEW] Grub2 Can't install on /dev/sda
Public bug reported: I wonder if this problem is associated with my hardware. (Sorry for my poor writing) I'm using Lenovo ideapad320-14iap, when I trying to install Ubuntu, I always meet the problem of the grub2. When the Ubuntu 19.04 is the installed version, I got lots of error code (eax, etc.) that seemed about the cpu and said "Kernel Panic" When the Ubuntu 19.10 Daily Build is the installed version, I did not get the long error output but get the error line, as the "Shim" was installing , I got a message "Grub can't install on /dev/sda" IF I ADD THE ARGUMENT "--no-bootloader" AND INSTALL GRUB MANUALLY, I WON'T GET ANY ERROR ABOUT THE BOOTLOADER ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.8 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 Date: Thu Aug 8 16:38:00 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed quiet splash --- LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubiquity-19.10.8 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839444 Title: Grub2 Can't install on /dev/sda To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1839444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818044] [NEW] package udev 229-4ubuntu21.16 failed to install/upgrade: package udev is already installed and configured
Public bug reported: I accepted the upgrade from ubuntu16.04 to ubuntu21.16, but my computer get wrong. I don't know what to do to recover my computer. Please help me! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu21.16 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 CrashReports: 640:0:117:825435:2019-02-28 17:51:16.110720634 +0800:2019-02-28 17:51:19.886966474 +0800:/var/crash/libjson-c2:i386.0.crash 600:0:117:289405:2019-02-27 17:31:36.897573947 +0800:2019-02-27 17:31:37.897573947 +0800:/var/crash/udev.0.crash 600:109:117:0:2019-02-28 17:51:25.039400021 +0800:2019-02-28 17:51:25.039400021 +0800:/var/crash/libjson-c2:i386.0.uploaded 640:0:117:466526:2019-02-20 09:47:37.143724203 +0800:2019-02-20 09:47:38.143724203 +0800:/var/crash/_usr_lib_xorg_Xorg.0.crash 644:0:117:0:2019-02-28 17:51:19.886966474 +0800:2019-02-28 17:51:19.886966474 +0800:/var/crash/libjson-c2:i386.0.upload CustomUdevRuleFiles: 70-snap.core.rules Date: Wed Feb 27 17:31:37 2019 DuplicateSignature: package:udev:229-4ubuntu21.16 Processing triggers for install-info (6.1.0.dfsg.1-5) ... dpkg: error processing package libjson-c2:i386 (--configure): package libjson-c2:i386 is already installed and configured ErrorMessage: package udev is already installed and configured InstallationDate: Installed on 2019-01-21 (37 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Gigabyte Technology Co., Ltd. X299-WU8 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: dpkg Title: package udev 229-4ubuntu21.16 failed to install/upgrade: package udev is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: Default string dmi.board.name: X299-WU8-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd10/03/2018:svnGigabyteTechnologyCo.,Ltd.:pnX299-WU8:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX299-WU8-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X299-WU8 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818044 Title: package udev 229-4ubuntu21.16 failed to install/upgrade: package udev is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1818044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1245245] Re: MMIO write FAULT
After a clean reinstall, the boot is successful, though all program is gone after clean install. If ubuntu has a repair function like windows does, it'd be easier. Though it's fine for me now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1245245 Title: MMIO write FAULT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1245245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1245245] Re: MMIO write FAULT
Attached my error screenshot ** Attachment added: "Error screenshot" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1245245/+attachment/5021706/+files/IMG_20171212_211139.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1245245 Title: MMIO write FAULT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1245245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1245245] Re: MMIO write FAULT
I'm using ubuntu 16.04. This bug also affects me. The machine can only start to emergency mode because of this bug. Error: [Hardware Error] nouveau bus: MMIO write of xx FAULT ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1245245 Title: MMIO write FAULT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1245245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708742] [NEW] package docker.io 1.6.2~dfsg1-1ubuntu4~14.04.1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1
Public bug reported: 正在设置 docker.io (1.6.2~dfsg1-1ubuntu4~14.04.1) ... addgroup: 组 docker 已经存在，且不是系统组。退出。 dpkg: 处理软件包 docker.io (--configure)时出错： 子进程 已安装 post-installation 脚本 返回了错误号 1 在处理时有错误发生： docker.io ProblemType: Package DistroRelease: Ubuntu 14.04 Package: docker.io 1.6.2~dfsg1-1ubuntu4~14.04.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.24 Architecture: amd64 Date: Fri Aug 4 16:48:06 2017 DpkgHistoryLog: Start-Date: 2017-08-04 16:47:33 Commandline: apt-get install fsl Install: tcsh:amd64 (6.18.01-2, automatic), fsl:amd64 (4.1.9-7.2), libnewmat10ldbl:amd64 (1.10.4-5, automatic), fsl-4.1:amd64 (4.1.9-7.2, automatic), libnifti2:amd64 (2.0.0-1, automatic), fsl-doc-4.1:amd64 (4.1.9-7.2, automatic), libgdchart-gd2-noxpm:amd64 (0.11.5-7.1ubuntu1, automatic) DuplicateSignature: package:docker.io:1.6.2~dfsg1-1ubuntu4~14.04.1:子进程 已安装 post-installation 脚本 返回了错误号 1 ErrorMessage: 子进程 已安装 post-installation 脚本 返回了错误号 1 InstallationDate: Installed on 2017-06-21 (44 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: docker.io Title: package docker.io 1.6.2~dfsg1-1ubuntu4~14.04.1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1708742 Title: package docker.io 1.6.2~dfsg1-1ubuntu4~14.04.1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1708742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448092] Re: [needs-packaging] ibmpmlinux
Here is an upgrade of PMUbuntu with Debian support included: # tar tvf ibmpmlinux_3.4.1-1_20160916.tar -rw-r--r-- root/root 19848 2016-09-16 12:13 ibmpmlinux_3.4.1-1.debian.tar.xz -rw-r--r-- root/root536235 2016-09-16 12:13 ibmpmlinux_3.4.1.orig.tar.gz -rw-r--r-- root/root402410 2016-09-16 12:14 ibmpmlinux_3.4.1-1_ppc64el.deb ** Attachment added: "Enhanced PMLinux tar files and their result from dpkg-buildpackage" https://bugs.launchpad.net/ubuntu/+bug/1448092/+attachment/4742188/+files/ibmpmlinux_3.4.1-1_20160916.tar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448092 Title: [needs-packaging] ibmpmlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616902] Re: libdevmapper logging not properly initialized
OK. This has been fixed in multipat-tools upstream repo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616902 Title: libdevmapper logging not properly initialized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1616902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1298061] Re: nova should allow evacuate for an instance in the Error state
** Description changed: [Impact] * Instances in error state cannot be evacuated. [Test Case] * nova evacuate * nova refuses to evacuate the instance because of its state [Regression Potential] * None - * Passed tempest smoke tests locally. + * Passed tempest smoke tests locally. + + Note: one simple way to put an instance into error state is to directly + change its database record, for example update instances set + vm_state='error' where uuid='' We currently allow reboot/rebuild/rescue for an instance in the Error state if the instance has successfully booted at least once. We should allow "evacuate" as well, since it is essentially a "rebuild" on a different compute node. This would be useful in a number of cases, in particular if an initial evacuation attempt fails (putting the instance into the Error state). ** Description changed: [Impact] * Instances in error state cannot be evacuated. [Test Case] * nova evacuate * nova refuses to evacuate the instance because of its state [Regression Potential] * None * Passed tempest smoke tests locally. Note: one simple way to put an instance into error state is to directly - change its database record, for example update instances set - vm_state='error' where uuid='' + change its database record, for example "update instances set + vm_state='error' where uuid=''" We currently allow reboot/rebuild/rescue for an instance in the Error state if the instance has successfully booted at least once. We should allow "evacuate" as well, since it is essentially a "rebuild" on a different compute node. This would be useful in a number of cases, in particular if an initial evacuation attempt fails (putting the instance into the Error state). ** Description changed: [Impact] * Instances in error state cannot be evacuated. [Test Case] * nova evacuate * nova refuses to evacuate the instance because of its state [Regression Potential] * None * Passed tempest smoke tests locally. Note: one simple way to put an instance into error state is to directly change its database record, for example "update instances set vm_state='error' where uuid=''" + We currently allow reboot/rebuild/rescue for an instance in the Error state if the instance has successfully booted at least once. We should allow "evacuate" as well, since it is essentially a "rebuild" on a different compute node. This would be useful in a number of cases, in particular if an initial evacuation attempt fails (putting the instance into the Error state). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1298061 Title: nova should allow evacuate for an instance in the Error state To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1298061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1298061] Re: nova should allow evacuate for an instance in the Error state
** Description changed: [Impact] - * Instances in error state cannot be evacuated. + * Instances in error state cannot be evacuated. [Test Case] - * nova evacuate - * nova refuses to evacuate the instance because of its state + * nova evacuate + * nova refuses to evacuate the instance because of its state [Regression Potential] - * None - + * None + * Passed tempest smoke tests locally. We currently allow reboot/rebuild/rescue for an instance in the Error state if the instance has successfully booted at least once. We should allow "evacuate" as well, since it is essentially a "rebuild" on a different compute node. This would be useful in a number of cases, in particular if an initial evacuation attempt fails (putting the instance into the Error state). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1298061 Title: nova should allow evacuate for an instance in the Error state To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1298061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1298061] Re: nova should allow evacuate for an instance in the Error state
** Changed in: nova (Ubuntu Trusty) Assignee: (unassigned) => Liang Chen (cbjchen) ** Changed in: nova (Ubuntu Trusty) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1298061 Title: nova should allow evacuate for an instance in the Error state To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1298061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621340] Re: 'multipath -r' causes /dev/mapper/ being removed
** Description changed:
+ [Impact]
+
"multipath -r" causes the /dev/mapper/ to disappear momentarily,
which leads to some issue in consumer applications as such OpenStack.
- After some investigation, I found that /dev/mapper/ was deleted by
- udev during the reload, and it was re-created soon later by multipathd
- (livdevmapper code of cause). Detailed findings are as follows:
+
+ [Test Case]
+
+ * connect to an multipath iscsi target
+ * multipath -r
+ * /dev/mapper/ disappears momentarily
+
+ [Regression Potential]
+
+ * None
+
+
+ "multipath -r" causes the /dev/mapper/ to disappear momentarily, which
leads to some issue in consumer applications as such OpenStack. After some
investigation, I found that /dev/mapper/ was deleted by udev during the
reload, and it was re-created soon later by multipathd (livdevmapper code of
cause). Detailed findings are as follows:
For reload in domap (rename as well),
- case ACT_RELOAD:
- r = dm_addmap_reload(mpp, params);
- if (r)
- r = dm_simplecmd_noflush(DM_DEVICE_RESUME, mpp->alias,
- 0, MPATH_UDEV_RELOAD_FLAG);
- break;
+ case ACT_RELOAD:
+ r = dm_addmap_reload(mpp, params);
+ if (r)
+ r = dm_simplecmd_noflush(DM_DEVICE_RESUME, mpp->alias,
+ 0, MPATH_UDEV_RELOAD_FLAG);
+ break;
+ it passes 0 to dm_simplecmd_noflush as argument for needsync, which
+ makes dm_task_set_cookie call being skipped in dm_simplecmd,
- it passes 0 to dm_simplecmd_noflush as argument for needsync, which makes
dm_task_set_cookie call being skipped in dm_simplecmd,
+ if (udev_wait_flag && !dm_task_set_cookie(dmt, ,
((conf->daemon)? DM_UDEV_DISABLE_LIBRARY_FALLBACK : 0) | udev_flags)) {
+ dm_udev_complete(cookie);
+ goto out;
+ }
- if (udev_wait_flag && !dm_task_set_cookie(dmt, ,
((conf->daemon)? DM_UDEV_DISABLE_LIBRARY_FALLBACK : 0) | udev_flags)) {
- dm_udev_complete(cookie);
- goto out;
- }
-
-
- because of the short-circuit evaluation. Thus _do_dm_ioctl in libdevmapper
will add DM_UDEV_DISABLE_DM_RULES_FLAG flag to dmi->event_nr, and that will
eventually be used in the udev rules (55-dm.rules),
+ because of the short-circuit evaluation. Thus _do_dm_ioctl in
+ libdevmapper will add DM_UDEV_DISABLE_DM_RULES_FLAG flag to
+ dmi->event_nr, and that will eventually be used in the udev rules
+ (55-dm.rules),
ENV{DM_UDEV_DISABLE_DM_RULES_FLAG}!="1", ENV{DM_NAME}=="?*",
SYMLINK+="mapper/$env{DM_NAME}"
-
- Since the DM_UDEV_DISABLE_DM_RULES_FLAG is set, the rule will not match. As a
result the link is removed.
+ Since the DM_UDEV_DISABLE_DM_RULES_FLAG is set, the rule will not match.
+ As a result the link is removed.
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621340
Title:
'multipath -r' causes /dev/mapper/ being removed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1621340/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621340] Re: 'multipath -r' causes /dev/mapper/ being removed
** Patch added: "Yakkety patch" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1621340/+attachment/4736879/+files/yakkety.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621340 Title: 'multipath -r' causes /dev/mapper/ being removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1621340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621340] Re: 'multipath -r' causes /dev/mapper/ being removed
** Changed in: multipath-tools (Ubuntu Xenial) Status: New => In Progress ** Changed in: multipath-tools (Ubuntu Xenial) Assignee: (unassigned) => Liang Chen (cbjchen) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621340 Title: 'multipath -r' causes /dev/mapper/ being removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1621340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621340] Re: 'multipath -r' causes /dev/mapper/ being removed
** Patch added: "xenial debdiff" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1621340/+attachment/4736695/+files/xenial.diff ** Changed in: multipath-tools (Ubuntu) Assignee: (unassigned) => Liang Chen (cbjchen) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621340 Title: 'multipath -r' causes /dev/mapper/ being removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1621340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621340] [NEW] 'multipath -r' causes /dev/mapper/ being removed
Public bug reported:
"multipath -r" causes the /dev/mapper/ to disappear momentarily,
which leads to some issue in consumer applications as such OpenStack.
After some investigation, I found that /dev/mapper/ was deleted by
udev during the reload, and it was re-created soon later by multipathd
(livdevmapper code of cause). Detailed findings are as follows:
For reload in domap (rename as well),
case ACT_RELOAD:
r = dm_addmap_reload(mpp, params);
if (r)
r = dm_simplecmd_noflush(DM_DEVICE_RESUME, mpp->alias,
0, MPATH_UDEV_RELOAD_FLAG);
break;
it passes 0 to dm_simplecmd_noflush as argument for needsync, which makes
dm_task_set_cookie call being skipped in dm_simplecmd,
if (udev_wait_flag && !dm_task_set_cookie(dmt, ,
((conf->daemon)? DM_UDEV_DISABLE_LIBRARY_FALLBACK : 0) | udev_flags)) {
dm_udev_complete(cookie);
goto out;
}
because of the short-circuit evaluation. Thus _do_dm_ioctl in libdevmapper will
add DM_UDEV_DISABLE_DM_RULES_FLAG flag to dmi->event_nr, and that will
eventually be used in the udev rules (55-dm.rules),
ENV{DM_UDEV_DISABLE_DM_RULES_FLAG}!="1", ENV{DM_NAME}=="?*",
SYMLINK+="mapper/$env{DM_NAME}"
Since the DM_UDEV_DISABLE_DM_RULES_FLAG is set, the rule will not match. As a
result the link is removed.
** Affects: multipath-tools (Ubuntu)
Importance: Undecided
Assignee: Liang Chen (cbjchen)
Status: In Progress
** Changed in: multipath-tools (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621340
Title:
'multipath -r' causes /dev/mapper/ being removed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1621340/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616902] [NEW] libdevmapper logging not properly initialized
Public bug reported:
dm_init();
if (getuid() != 0) {
fprintf(stderr, "need to be root\n");
exit(1);
}
/* make sure we don't lock any path */
chdir("/");
umask(umask(077) | 022);
conf = alloc_config();
dm_init is called before allocating conf. But dm_init depends on
conf->verbosity to initialize libdevmapper logging. In the current situation,
the verbosity is always set to 0 because conf is 0.
extern void
dm_init(void) {
dm_log_init(_write_log);
dm_log_init_verbose(conf ? conf->verbosity + 3 : 0);
}
** Affects: multipath-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616902
Title:
libdevmapper logging not properly initialized
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1616902/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445947] Re: 'pip3 list' throws AssertionError
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445947 Title: 'pip3 list' throws AssertionError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1445947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445947] Re: 'pip3 list' throws AssertionError
The package python-pip 1.5.4-1ubuntu4 is tested and it fixes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445947 Title: 'pip3 list' throws AssertionError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1445947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests
** Changed in: swift Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280522 Title: Replace assertEqual(None, *) with assertIsNone in tests To manage notifications about this bug go to: https://bugs.launchpad.net/anchor/+bug/1280522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests
** Also affects: swift Importance: Undecided Status: New ** Changed in: swift Assignee: (unassigned) => jingtao liang (liang-jingtao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280522 Title: Replace assertEqual(None, *) with assertIsNone in tests To manage notifications about this bug go to: https://bugs.launchpad.net/anchor/+bug/1280522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests
** Changed in: searchlight Assignee: (unassigned) => jingtao liang (liang-jingtao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280522 Title: Replace assertEqual(None, *) with assertIsNone in tests To manage notifications about this bug go to: https://bugs.launchpad.net/anchor/+bug/1280522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests
** Also affects: searchlight Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280522 Title: Replace assertEqual(None, *) with assertIsNone in tests To manage notifications about this bug go to: https://bugs.launchpad.net/anchor/+bug/1280522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549300] Re: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file
As expected, dialog gets fully recovered in the recent Ubuntu 16.10 (Yakkety Yak) Daily Build root@ubt1610:~# dpkg -l dialog ||/ Name Version Architecture Description +++----== ii dialog 1.3-20160424-1 ppc64el Displays user-friendly dialog boxes from shell scripts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549300 Title: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialog/+bug/1549300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549300] Re: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file
Checking the latest note in the changelog, this bug might have been fixed recently: http://invisible-island.net/dialog/CHANGES.html#t20121230 2016/04/24 + fix a special case in drawing shadow on a line-drawing cell where the alternate-character set flag was lost (report by Martin Kravec). + fix a regression from 2015/05/13 changes for escaping; it is necessary to retain backslashes within quotes to make "\Z" escapes work (report by Marcin Krol). WAIT & SEE a future release of dialog (1.4 by guessing). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549300 Title: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialog/+bug/1549300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1494350] Re: QEMU: causes vCPU steal time overflow on live migration
The proposed package is tested and it passed the test case described in the bug description. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1494350 Title: QEMU: causes vCPU steal time overflow on live migration To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1494350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445947] Re: 'pip3 list' throws AssertionError
trusty also need the fix ** Patch added: "trusty patch" https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1445947/+attachment/4670738/+files/fix_legacy_version_support.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445947 Title: 'pip3 list' throws AssertionError To manage notifications about this bug go to: https://bugs.launchpad.net/pip/+bug/1445947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382079] Re: [SRU] Project selector not working
The package in kilo-proposed archive fixed the issue for me. ** Tags removed: verification-kilo-needed ** Tags added: verification-kilo-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382079 Title: [SRU] Project selector not working To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1382079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445947] Re: 'pip3 list' throws AssertionError
The proposed package (1.5.6-7ubuntu1.2) works well for me. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445947 Title: 'pip3 list' throws AssertionError To manage notifications about this bug go to: https://bugs.launchpad.net/pip/+bug/1445947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369465] Re: nova resize doesn't resize(extend) rbd disk files when using rbd disk backend
Matt, I made debian patch for wily-liberty. But the patch depends on many other commits that kilo doesn't have, and I would be too risky to backport them all to kilo. So I am not going propose a kilo backport. Sorry for the inconvenience. Thanks, Liang -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1369465 Title: nova resize doesn't resize(extend) rbd disk files when using rbd disk backend To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1369465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549300] Re: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file
Unfortunately, the same bug now occurs on Fedora 24, with: dialog-1.3-3.20160209.fc24.ppc64le (Build Date : Fri 19 Feb 2016 11:26:24 PM CST), from the latest build: http://mirrors.rit.edu/fedora/fedora-secondary/releases/test/24_Alpha/Server/ppc64le/iso/Fedora-Server-dvd-ppc64le-24_Alpha-1.3.iso 2016-Mar-29 22:14:02 1.8G -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549300 Title: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialog/+bug/1549300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445947] Re: 'pip3 list' throws AssertionError
** Description changed: + [Impact] + + * Not able show current list of installed packages, e.g. pip freeze. + + [Test Case] + + 1 - install wily/trusty-liberty python-pip package + 2 - pip freeze + 3 - the following error is shown without the patch + + Exception: + Traceback (most recent call last): + File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 122, in main + status = self.run(options, args) + File "/usr/lib/python2.7/dist-packages/pip/commands/freeze.py", line 74, in run + req = pip.FrozenRequirement.from_dist(dist, dependency_links, find_tags=find_tags) + File "/usr/lib/python2.7/dist-packages/pip/__init__.py", line 286, in from_dist + assert len(specs) == 1 and specs[0][0] == '==' + AssertionError + + [Regression Potential] + + * None + + The command 'pip3 list' is broken on vivid: maxb@altimeter:~$ pip3 list [snip] Exception: Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/pip/basecommand.py", line 122, in main - status = self.run(options, args) - File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 80, in run - self.run_listing(options) - File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 142, in run_listing - self.output_package_listing(installed_packages) - File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 151, in output_package_listing - if dist_is_editable(dist): - File "/usr/lib/python3/dist-packages/pip/util.py", line 367, in dist_is_editable - req = FrozenRequirement.from_dist(dist, []) - File "/usr/lib/python3/dist-packages/pip/__init__.py", line 299, in from_dist - assert len(specs) == 1 and specs[0][0] == '==' + File "/usr/lib/python3/dist-packages/pip/basecommand.py", line 122, in main + status = self.run(options, args) + File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 80, in run + self.run_listing(options) + File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 142, in run_listing + self.output_package_listing(installed_packages) + File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 151, in output_package_listing + if dist_is_editable(dist): + File "/usr/lib/python3/dist-packages/pip/util.py", line 367, in dist_is_editable + req = FrozenRequirement.from_dist(dist, []) + File "/usr/lib/python3/dist-packages/pip/__init__.py", line 299, in from_dist + assert len(specs) == 1 and specs[0][0] == '==' AssertionError The problem is that the version string of python-apt is not PEP 440 compliant. Avoiding this crash is already fixed with a one-line patch upstream. Please consider cherry-picking https://github.com/pypa/pip/commit/6cab71f422f2425b4d2283023c9e955f9663dde6 into Vivid's pip. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: python3-pip 1.5.6-5ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 19 16:55:24 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-29 (325 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: python-pip UpgradeStatus: Upgraded to vivid on 2015-03-29 (20 days ago) ** Changed in: python-pip (Ubuntu) Status: Confirmed => In Progress ** Changed in: python-pip (Ubuntu) Assignee: (unassigned) => Liang Chen (cbjchen) ** Patch added: "wily debian patch" https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1445947/+attachment/4633565/+files/fix_legacy_version_support.diff ** Tags added: sts sts-sru -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445947 Title: 'pip3 list' throws AssertionError To manage notifications about this bug go to: https://bugs.launchpad.net/pip/+bug/1445947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369465] Re: nova resize doesn't resize(extend) rbd disk files when using rbd disk backend
** Changed in: nova (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1369465 Title: nova resize doesn't resize(extend) rbd disk files when using rbd disk backend To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1369465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369465] Re: nova resize doesn't resize(extend) rbd disk files when using rbd disk backend
** Changed in: nova (Ubuntu) Assignee: (unassigned) => Liang Chen (cbjchen) ** Patch added: "wily-liberty debian patch" https://bugs.launchpad.net/nova/+bug/1369465/+attachment/4629899/+files/fix_rbd_resize.diff ** Description changed: + [Impact] + + * Not able to resize rbd backed disk image. + + [Test Case] + + 1 - boot an instance with rbd backed disk image + 2 - resize it + 3 - log into the VM + 4 - the disk is not enlarged without this patch + + [Regression Potential] + + * None + + tested with nova trunk commit eb860c2f219b79e4f4c5984415ee433145197570 Configured Nova to use rbd disk backend nova.conf [libvirt] images_type=rbd instances booted successfully and instance disks are in rbd pools, when perform a nova resize to an existing instance, memory and CPU changed to be new flavors but instance disks size doesn't change ** Tags added: sts-sru -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1369465 Title: nova resize doesn't resize(extend) rbd disk files when using rbd disk backend To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1369465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510344] Re: Keyboard Backlight Turns on at boot
Same bug with Dell E6430s ** Also affects: linux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510344 Title: Keyboard Backlight Turns on at boot To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1494350] Re: QEMU: causes vCPU steal time overflow on live migration
The backport has been acked in upstream for 3.4, 3.10, 3.14, and 3.16 stable kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1494350 Title: QEMU: causes vCPU steal time overflow on live migration To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1494350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549300] Re: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file
Whiptail is too simple. It even has no form input box, so there's no way for it to be an alternative for dialog that is popular with non-Ubuntu Linux systems. It's weird that the Ubuntu team pays more attention to whiptail than to dialog. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549300 Title: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialog/+bug/1549300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549300] Re: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file
What are you talking about? There is no point that dialog is not supported on Ubuntu ppc64el server! In fact, dialog package is available by default in apt archive repository: http://us.ports.ubuntu.com/ubuntu-ports, in the same main URL as dash's: http://us.ports.ubuntu.com/ubuntu-ports/pool/main/d/dialog/dialog_1.2-20150920-1ubuntu1_ppc64el.deb http://us.ports.ubuntu.com/ubuntu-ports/pool/main/d/dash/dash_0.5.8-2.1ubuntu2_ppc64el.deb for quick installation for all Ubuntu releases up to 16.04 (Xenial Xerus) so far, as demonstrated below: root@ubt1604KD2:/# uname -a Linux ubt1604KD2 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:06:23 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux root@ubt1604KD2:~# apt install dialog Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: dialog 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 199 kB of archives. After this operation, 1,311 kB of additional disk space will be used. Get:1 http://us.ports.ubuntu.com/ubuntu-ports xenial/main ppc64el dialog ppc64el 1.2-20150920-1ubuntu1 [199 kB] Fetched 199 kB in 0s (255 kB/s) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549300 Title: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialog/+bug/1549300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1546445] Re: support vhost user without specifying vhostforce
Tested with 1:2.2+dfsg-5expubuntu9.7~cloud2, and the fix works for me. ** Tags removed: verification-kilo-needed ** Tags added: verification-kilo-done -- 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/1546445 Title: support vhost user without specifying vhostforce To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1546445/+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 1546445] Re: support vhost user without specifying vhostforce
Tested with 1:2.2+dfsg-5expubuntu9.7~cloud2, and the fix works for me. ** Tags removed: verification-kilo-needed ** Tags added: verification-kilo-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546445 Title: support vhost user without specifying vhostforce To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1546445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382079] Re: Project selector not working
** Changed in: cloud-archive Assignee: (unassigned) => Liang Chen (cbjchen) ** Changed in: cloud-archive Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382079 Title: Project selector not working To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1382079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382079] Re: Project selector not working
** Changed in: cloud-archive Assignee: (unassigned) => Liang Chen (cbjchen) ** Changed in: cloud-archive Status: New => In Progress -- 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/1382079 Title: Project selector not working To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1382079/+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 1546445] Re: support vhost user without specifying vhostforce
** Changed in: cloud-archive Assignee: (unassigned) => Liang Chen (cbjchen) ** Changed in: cloud-archive Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546445 Title: support vhost user without specifying vhostforce To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1546445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1546445] Re: support vhost user without specifying vhostforce
** Changed in: cloud-archive Assignee: (unassigned) => Liang Chen (cbjchen) ** Changed in: cloud-archive Status: New => In Progress -- 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/1546445 Title: support vhost user without specifying vhostforce To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1546445/+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 1546445] Re: support vhost user without specifying vhostforce
** Tags added: sts sts-sru -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546445 Title: support vhost user without specifying vhostforce To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1546445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1546445] Re: support vhost user without specifying vhostforce
** Tags added: sts sts-sru -- 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/1546445 Title: support vhost user without specifying vhostforce To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1546445/+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 1382079] Re: Project selector not working
** Tags added: sts-sru -- 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/1382079 Title: Project selector not working To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1382079/+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 1382079] Re: Project selector not working
** Tags added: sts-sru -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382079 Title: Project selector not working To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1382079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382079] Re: Project selector not working
** Description changed: [Impact] - * Not able to switch projects by the project dropdown list. + * Not able to switch projects by the project dropdown list. [Test Case] - 1 - Log in on Horizon - 2 - make sure that the SESSION_BACKEND is "signed_cookies" - 3 - Try to change project on the dropdown + 1 - enable Identity V3 in local_settings.py + 2 - Log in on Horizon + 3 - make sure that the SESSION_BACKEND is "signed_cookies" + 4 - Try to change project on the dropdown [Regression Potential] - * None - + * None When you try to select a new project on the project dropdown, the project doesn't change. The commit below has introduced this bug on Horizon's master and has passed the tests verifications. https://github.com/openstack/horizon/commit/16db58fabad8934b8fbdfc6aee0361cc138b20af For what I've found so far, the context being received in the decorator seems to be the old context, with the token to the previous project. When you take the decorator out, the context received by the "can_access" function receives the correct context, with the token to the new project. Steps to reproduce: 1 - Enable Identity V3 (to have a huge token) 2 - Log in on Horizon (lots of permissions loaded on session) 3 - Certify that you SESSION_BACKEND is "signed_cookies" 4 - Try to change project on the dropdown The project shall remain the same. ** Tags added: sts ** Changed in: horizon (Ubuntu Vivid) Assignee: (unassigned) => Liang Chen (cbjchen) ** Changed in: horizon (Ubuntu Vivid) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382079 Title: Project selector not working To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1382079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382079] Re: Project selector not working
** Description changed: [Impact] - * Not able to switch projects by the project dropdown list. + * Not able to switch projects by the project dropdown list. [Test Case] - 1 - Log in on Horizon - 2 - make sure that the SESSION_BACKEND is "signed_cookies" - 3 - Try to change project on the dropdown + 1 - enable Identity V3 in local_settings.py + 2 - Log in on Horizon + 3 - make sure that the SESSION_BACKEND is "signed_cookies" + 4 - Try to change project on the dropdown [Regression Potential] - * None - + * None When you try to select a new project on the project dropdown, the project doesn't change. The commit below has introduced this bug on Horizon's master and has passed the tests verifications. https://github.com/openstack/horizon/commit/16db58fabad8934b8fbdfc6aee0361cc138b20af For what I've found so far, the context being received in the decorator seems to be the old context, with the token to the previous project. When you take the decorator out, the context received by the "can_access" function receives the correct context, with the token to the new project. Steps to reproduce: 1 - Enable Identity V3 (to have a huge token) 2 - Log in on Horizon (lots of permissions loaded on session) 3 - Certify that you SESSION_BACKEND is "signed_cookies" 4 - Try to change project on the dropdown The project shall remain the same. ** Tags added: sts ** Changed in: horizon (Ubuntu Vivid) Assignee: (unassigned) => Liang Chen (cbjchen) ** Changed in: horizon (Ubuntu Vivid) Status: New => In Progress -- 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/1382079 Title: Project selector not working To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1382079/+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 1382079] Re: Project selector not working
** Description changed: + [Impact] + + * Not able to switch projects by the project dropdown list. + + [Test Case] + + 1 - Log in on Horizon + 2 - make sure that the SESSION_BACKEND is "signed_cookies" + 3 - Try to change project on the dropdown + + [Regression Potential] + + * None + + When you try to select a new project on the project dropdown, the project doesn't change. The commit below has introduced this bug on Horizon's master and has passed the tests verifications. https://github.com/openstack/horizon/commit/16db58fabad8934b8fbdfc6aee0361cc138b20af For what I've found so far, the context being received in the decorator seems to be the old context, with the token to the previous project. When you take the decorator out, the context received by the "can_access" function receives the correct context, with the token to the new project. Steps to reproduce: 1 - Enable Identity V3 (to have a huge token) 2 - Log in on Horizon (lots of permissions loaded on session) 3 - Certify that you SESSION_BACKEND is "signed_cookies" 4 - Try to change project on the dropdown The project shall remain the same. -- 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/1382079 Title: Project selector not working To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1382079/+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 1382079] Re: Project selector not working
** Description changed: + [Impact] + + * Not able to switch projects by the project dropdown list. + + [Test Case] + + 1 - Log in on Horizon + 2 - make sure that the SESSION_BACKEND is "signed_cookies" + 3 - Try to change project on the dropdown + + [Regression Potential] + + * None + + When you try to select a new project on the project dropdown, the project doesn't change. The commit below has introduced this bug on Horizon's master and has passed the tests verifications. https://github.com/openstack/horizon/commit/16db58fabad8934b8fbdfc6aee0361cc138b20af For what I've found so far, the context being received in the decorator seems to be the old context, with the token to the previous project. When you take the decorator out, the context received by the "can_access" function receives the correct context, with the token to the new project. Steps to reproduce: 1 - Enable Identity V3 (to have a huge token) 2 - Log in on Horizon (lots of permissions loaded on session) 3 - Certify that you SESSION_BACKEND is "signed_cookies" 4 - Try to change project on the dropdown The project shall remain the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382079 Title: Project selector not working To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1382079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1494350] Re: QEMU: causes vCPU steal time overflow on live migration
** Description changed: + [Impact] + It is possible to have vcpu->arch.st.last_steal initialized + from a thread other than vcpu thread, say the main thread, via + KVM_SET_MSRS. That can cause steal_time overflow later (when subtracting from vcpu threads sched_info.run_delay). + + [Test Case] Testing Steps with patched trusty kernel: - Using savemv & loadvm to simulate the migration process. In guest: 1. check steal_time data location rdmsr 0x4b564d03 <- returns the start address 0x7fc0d000 2. exam the steal time before savevm in qemu monitor (qemu) xp /ug 0x7fc0d000 xp /ug 0x7fc0d000 7fc0d000:144139048 < steal time value before savevm (qemu) savevm mytestvm7 savevm mytestvm7 (qemu) quit quit 3. give some load to the host system, e.g. stress --cpu 4. start the guest with "-loadvm mytestvm7" to restore the state of the VM, thus the steal_time MSR 5. exam the steal time value again (qemu) xp /ug 0x7fc0d000 xp /ug 0x7fc0d000 7fc0d000:147428917 < with high cpu load after loadvm, steal time still shows a linear increase The steal_time value would go backward (because of the overflow) after the restoration of the VM state without the fix. - I'm pasting in text from Debian Bug 785557 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785557 b/c I couldn't find this issue reported. It is present in QEMU 2.3, but I haven't tested later versions. Perhaps someone else will find this bug and confirm for later versions. (Or I will when I have time!) Hi, I'm trying to debug an issue we're having with some debian.org machines running in QEMU 2.1.2 instances (see [1] for more background). In short, after a live migration guests running Debian Jessie (linux 3.16) stop accounting CPU time properly. /proc/stat in the guest shows no increase in user and system time anymore (regardless of workload) and what stands out are extremely large values for steal time: % cat /proc/stat cpu 2400 0 1842 650879168 2579640 0 25 136562317270 0 0 cpu0 1366 0 1028 161392988 1238598 0 11 383803090749 0 0 cpu1 294 0 240 162582008 639105 0 8 39686436048 0 0 cpu2 406 0 338 163331066 383867 0 4 333994238765 0 0 cpu3 332 0 235 163573105 318069 0 1 1223752959076 0 0 intr 355773871 33 10 0 0 0 0 3 0 1 0 0 36 144 0 0 1638612 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 5001741 41 0 8516993 0 3669582 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ctxt 837862829 btime 1431642967 processes 8529939 procs_running 1 procs_blocked 0 softirq 225193331 2 77532878 172 7250024 819289 0 54 33739135 176552 105675225 Reading the memory pointed to by the steal time MSRs pre- and post-migration, I can see that post-migration the high bytes are set to 0xff: (qemu) xp /8b 0x1fc0cfc0 1fc0cfc0: 0x94 0x57 0x77 0xf5 0xff 0xff 0xff 0xff The "jump" in steal time happens when the guest is resumed on the receiving side. I've also been able to consistently reproduce this on a Ganeti cluster at work, using QEMU 2.1.3 and kernels 3.16 and 4.0 in the guests. The issue goes away if I disable the steal time MSR using `-cpu qemu64,-kvm_steal_time`. So, it looks to me as if the steal time MSR is not set/copied properly during live migration, although AFAICT this should be the case after 917367aa968fd4fef29d340e0c7ec8c608dffaab. After
[Bug 1494350] Re: QEMU: causes vCPU steal time overflow on live migration
** Description changed: + Testing Steps with patched trusty kernel: + + Using savemv & loadvm to simulate the migration process. + + In guest: + 1. check steal_time data location + rdmsr 0x4b564d03 <- returns the start address 0x7fc0d000 + + 2. Exam the steal time before savevm in qemu monitor + (qemu) xp /ug 0x7fc0d000 + xp /ug 0x7fc0d000 + 7fc0d000:144139048 < steal time value before savevm + (qemu) savevm mytestvm7 + savevm mytestvm7 + (qemu) quit + quit + + 3. give some load to the host system, e.g. stress --cpu + + 4. start the guest with "-loadvm mytestvm7" to restore the state of the + VM, thus the steal_time MSR + + (qemu) xp /ug 0x7fc0d000 + xp /ug 0x7fc0d000 + 7fc0d000:147428917 < with high cpu load after loadvm, steal time still shows a linear increase + + The steal_time value would go backward (because of the overflow) after + the restoration of the VM state without the fix. + + - + + I'm pasting in text from Debian Bug 785557 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785557 b/c I couldn't find this issue reported. It is present in QEMU 2.3, but I haven't tested later versions. Perhaps someone else will find this bug and confirm for later versions. (Or I will when I have time!) Hi, - I'm trying to debug an issue we're having with some debian.org machines - running in QEMU 2.1.2 instances (see [1] for more background). In short, - after a live migration guests running Debian Jessie (linux 3.16) stop - accounting CPU time properly. /proc/stat in the guest shows no increase - in user and system time anymore (regardless of workload) and what stands + I'm trying to debug an issue we're having with some debian.org machines + running in QEMU 2.1.2 instances (see [1] for more background). In short, + after a live migration guests running Debian Jessie (linux 3.16) stop + accounting CPU time properly. /proc/stat in the guest shows no increase + in user and system time anymore (regardless of workload) and what stands out are extremely large values for steal time: - % cat /proc/stat - cpu 2400 0 1842 650879168 2579640 0 25 136562317270 0 0 - cpu0 1366 0 1028 161392988 1238598 0 11 383803090749 0 0 - cpu1 294 0 240 162582008 639105 0 8 39686436048 0 0 - cpu2 406 0 338 163331066 383867 0 4 333994238765 0 0 - cpu3 332 0 235 163573105 318069 0 1 1223752959076 0 0 - intr 355773871 33 10 0 0 0 0 3 0 1 0 0 36 144 0 0 1638612 0 0 0 0 0 0 0 0 0 0 - 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 5001741 41 0 8516993 0 3669582 0 0 0 0 0 0 0 0 0 - 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 - 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 - 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 - 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 - 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 - 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 - 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 - 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 - 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 - 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 - 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 - 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 - 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 - 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 - 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 - 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 + % cat /proc/stat + cpu 2400 0 1842 650879168 2579640 0 25 136562317270 0 0 + cpu0 1366 0 1028 161392988 1238598 0 11 383803090749 0 0 + cpu1 294 0 240 162582008 639105 0 8 39686436048 0 0 + cpu2 406 0 338 163331066 383867 0 4 333994238765 0 0 + cpu3 332 0 235 163573105 318069 0 1 1223752959076 0 0 + intr 355773871 33 10 0 0 0 0 3 0 1 0 0 36 144 0 0 1638612 0 0 0 0 0 0 0 0 0 0 + 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 5001741 41 0 8516993 0 3669582 0 0 0 0 0 0 0 0 0 + 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 + 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 + 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 + 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 + 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[Bug 1494350] Re: QEMU: causes vCPU steal time overflow on live migration
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Liang Chen (cbjchen) ** Changed in: linux (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1494350 Title: QEMU: causes vCPU steal time overflow on live migration To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1494350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448092] Re: [needs-packaging] ibmpmlinux
Hi Mathieu, As my regard to your comment #45, I did some minor changes for your further review. # tar tvf ibmpmlinux_3.2.2-1_20160302.tar -rw-r--r-- root/root 19472 2016-03-02 16:25 ibmpmlinux_3.2.2-1.debian.tar.xz -rw-r--r-- root/root537644 2016-03-02 16:25 ibmpmlinux_3.2.2.orig.tar.gz -rw-r--r-- root/root402482 2016-03-02 16:26 ibmpmlinux_3.2.2-1_ppc64el.deb Here are my responses to your detailed concerns: - Version for Ubuntu should be -0ubuntu1 rather than -1. This is important, since there isn't an ibmpmlinux package in Debian currently that we sync to ubuntu. Should there be, then it would be fine to ship a package with a version -1ubuntu1. The 'ubuntu' suffix denotes it is an upload for ubuntu. Answer: Adding a long string "ubuntu" in the version field is not a good idea. It unnecessarily expands a package file name, which could cause troubles everywhere. Particularly, PMLinux programs can work fine (compatible) for all Linux variants that we support (RedHat, SuSE, Fedora, Ubuntu, and PowerKVM). It seems no meaning to have PMLinux pakage with a "ubuntu" tag. - If you must use an internal revision number following a - in the filename for the include source tarball, then let's modify debian/rules to account for this. Either debian/rules should go extract the specific file needed for the version, or it should avoid that entirely and just extract any tarball named ibmpmlinux_*.tgz Answer: We have no special versioning need for PMLinux. The release- version format "r.r.r-v" that PMLinux adapted is popular for Linux platforms. By search, there exist more than a half pakcages without "ubuntu" in their version strings on Ubuntu 16.04 and apt/dpkg can handle properly at present. We hope to maintain the same if no change is mandatory. - Even the architecture name there is irrelevant if there won't be a build for other architectures. This would mean it's possible to remove all the variables aside from $package. Answer: We have other builds in rpm format for ppc64 Big/little Endians. The architecture mark is critical because PMLinux packages are "global" and "exchangable": For example, PMLinux's RPM package is supposed to work well on a Ubuntu system (if rpm tool installed). - override_dh_clean: rm -rf there will not do anything, it is unnecessary, since there will not be an ibmpmlinux directory to remove (since things are extracted to debian/tmp, which will get cleaned up automatically. Answer: Commented it out as per your suggestion. Thanks. - no need for preinst or postrm. Running verify or uninstall in postinst/prerm is most likely wrong. Answer: Not really. Those function blocks are necessary even if for a package that remains still after installed, not to mention that PMLinux is "dynamic" package. In PMLinux case: 1) preinst is to backup the old daemon programs for comparisons later in postinst for whether to restart the process(es) in upgrade. 2) postrm is to remove PMLinux's temporary data storage and flexible configurations etc generated/changed after installed that apt/dpkg are not aware of. Nothing above is handlable without those scriptlets. Apt/Dpkg can not handle the necessity of restarting old daemons in an upgrade, nor able to uninstall PMLinux with a upstart job after installed PMLinux with a service of systemd in the past (scenario: the user might rollback systemd to upstart, or vice versa). - It is just as easy (not to say easier) to not run them at all and ship the right files from the source of the package. Tuning configuration is fine, but we should not create new directories, symlinks, and such, since that short-circuits the package installation processes from apt and dpkg. They will handle package updates and removing files just fine. Answer: No. apt/dpkg can't do that fine, because PMLinux won't stand still after installed. PMLinux contains data-collecting daemons which do need to create a new directory for data storage under its home path. It is neither fine for tuning configuration. Configuration includes init service rollback or upgrade (upstart <-> systemd) which may result in file content & location changes that apt/dpkg can not manage at all. - In other words, if the source already ships all the right files (including a pre-made systemd service and reasonable default config), then all the maintainer scripts (postinst, preinst, prerm, postrm) can be removed. Otherwise, I would strongly recommend not keeping preinst and postrm. Postrm is completely unnecessary if the symlinks are done using dh_link (see below). Answer: Pre-made systemd is an impossible task. PMLinux.deb installation is a dynamic and adapting procedure. Nothing can be pre-made to fit such a blooming Linux world with so many dependencies. As answered above, systemd vs. upstart is one, PMLinux install vs upgrade is another, and many more, like etc/cron vs spool/cron, Ubuntu vs non-Ubuntu layouts,
[Bug 1549300] Re: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file
** Package changed: ubuntu => dialog (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549300 Title: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialog/+bug/1549300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1546445] Re: support vhost user without specifying vhostforce
** Also affects: cloud-archive Importance: Undecided Status: 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/1546445 Title: support vhost user without specifying vhostforce To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1546445/+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 1546445] Re: support vhost user without specifying vhostforce
** Also affects: cloud-archive Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546445 Title: support vhost user without specifying vhostforce To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1546445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1546445] Re: support vhost user without specifying vhostforce
** Changed in: qemu (Ubuntu Wily) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546445 Title: support vhost user without specifying vhostforce To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1546445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1546445] Re: support vhost user without specifying vhostforce
** Changed in: qemu (Ubuntu Wily) Status: New => Fix Released -- 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/1546445 Title: support vhost user without specifying vhostforce To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1546445/+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 1448092] Re: [needs-packaging] ibmpmlinux
Hi Mathieu,
Following my comment #36, now we have finished the work items of dark
blue in the schedule: PMUbuntu starts to be installed with an init
Service/Job script of sysV, upstart, or systemd. As a service/job, the
PM Data Collector daemon will be started from system boot of runlevel
2-5. Please review at your convenience.
# tar tvf ibmpmlinux_3.2.1-1_20160122.tar
-rw-r--r-- root/root 19468 2016-01-22 19:32 ibmpmlinux_3.2.1-1.debian.tar.xz
-rw-r--r-- root/root536035 2016-01-22 19:32 ibmpmlinux_3.2.1.orig.tar.gz
-rw-r--r-- root/root401598 2016-01-22 19:32 ibmpmlinux_3.2.1-1_ppc64el.deb
Here I just quote the description regarding this feature from
/opt/ibm/pm/README:
PMLinux SERVICE/JOB
PMLinux started to be installed as a service/job since version 3.2.0-1.
This is to support manipulating PMLinux process with the
common Linux service/job management interface, such as "service PMLinux
{start|stop|status}" etc. Meanwhile, PMLinux process will
be started from the init-rc.d sequence in system booting for every
multi-user run-level, and PMLinux's cron frequency is properly
adjusted from "hourly" to "daily" with this startup method.
New command "initservice.PMLnx" was initiated into PMLinux package for this
purpose. By default, the program probes what methods
(of sysV, systemd or upstart) are available on the system, and follows the
best one to define/enable the service/job control code
for PMLinux application accordingly in one of the following files:
/etc/init.d/PMLinux# sysV varieties
{LSBbase|rc_d|init_d}, all obsolete
/etc/init/PMLinux.conf # upstart, popular for
earlier Debian/Ubuntu releases
/lib/systemd/system/PMLinux.service# systemd, the latest trend
for all recent Linux releases
In general, it is not supposed to run this program manually, unless you
have to select a non-default method, or destruct PMLinux
service/job encapsulation. Moreover, it is not blessed to handle PMLinux
daemon with non-service/PMLinux tools, because that may
mess up the process status inside the service/job utilities. Anyway,
PMLinux certainly remains robust as before no matter how the
control interface is configured and utilized.
Here are some command examples under this topic:
(A) Construct PMLinux service/job # on the check list of
verify.PMLnx (run by command line or installation scripts)
# initservice.PMLnx # create PMLinux init
script with current method, or the best if missing/OFF
Constructing PMLinux service on [IBMpKVM3.1.0.45.0::LSBbase,rc_d,systemd*]
...
Created symlink from
/etc/systemd/system/multi-user.target.wants/PMLinux.service to
/usr/lib/systemd/system/PMLinux.service.
Register PMLinux service/job ... done
SUCCESS! (at /lib/systemd/system/PMLinux.service)
Redirecting to /bin/systemctl start PMLinux.service
(B) Change PMLinux service/job with another method
# initservice.PMLnx -J rc_d # Do (A) with an
old/obsolete method "rc_d" ("systemd" seems better)
Reset PM_INIT_SERVICEJOB=rc_d in /var/perf/pm/config/PMLinux.cfg ... done!
Constructing PMLinux service on [IBMpKVM3.1.0.45.0::LSBbase,rc_d*,systemd]
...
Register PMLinux service/job ... done
SUCCESS! (at /etc/init.d/PMLinux) # rc_d script is based on
the profile /etc/init.d/functions, while
# LSBbase's on
/lib/lsb/init-functions, and so on for init_d ...
Starting PMLinux (via systemctl): [ OK ]
(C) Start PMLinux Service Daemon# similarly, you may use
"stop" or "status" to stop or check PMLinux:
# service PMLinux start # "service" command is
generic for all Linux platforms
# start PMLinux # for Ubuntu/Debian only,
where "start" is a "command" if upstart installed!
# systemctl start PMLinux # specific for systemd, or
# be attentional:
serivce/job status integrity might be broken & you have to:
# service PMLinux restart # restart if PMLinux was
stopped by non-service command "kill"
(D) Deregister PMLinux service/job # just in case of
emergency, like system boot hanging at PMLinux service start
# initservice.PMLnx OFF # disable and remove
PMLinux service/job file if existed
# verify.PMLnx # Must repair PMLinux
integrity after you separately run initservice.PMLnx
** Attachment added: "Enhanced PMLinux tar files and their result from
dpkg-buildpackage"
https://bugs.launchpad.net/ubuntu/+bug/1448092/+attachment/4555165/+files/ibmpmlinux_3.2.1-1_20160122.tar
--
You received this bug notification because you are a member of Ubuntu
[Bug 1503826] Re: Boot hangs in blank for no way to enter LVM passphrase at kimchi/virsh console
"plymouth" is installed by default. The latest ubuntu 16.04 daily with LVM encryption installed still can NOT start with normal boot for user input (passphrase) is not seen processed at the dark screen. However, I may start it to the normal multiple-user login if boot the system with recovery mode first. The passphrase input goes fine for recovery mode, and the normal boot does not ask for passphrase again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1503826 Title: Boot hangs in blank for no way to enter LVM passphrase at kimchi/virsh console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1503826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504127] Re: lsb_release throws exception if stdout is closed
Steve, thank you very much for chasing the bug down to lsb_release. There is still no change that this exception occurs only on Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504127 Title: lsb_release throws exception if stdout is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1504127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1514325] Re: VersionedObject.__repr__ should return encoded string
** Description changed: - The following error is reported when creating a volume snapshot with - non-ascii display-description, e.g. cinder snapshot-create --display- - description "中文" my-2nd-volume. + [Impact] + + * Cinder snapshot display-description cannot contain non-ascii + characters. + + [Test Case] + + * cinder create 1 + * cinder snapshot-create --display-description "中文" + + [Regression Potential] + + * None + + + The following error is reported when creating a volume snapshot with non-ascii display-description, e.g. cinder snapshot-create --display-description "中文" my-2nd-volume. 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher [req-81f48a02-b1ef-4aae-9e22-ac2ce1c75b2f 16818cbff07548889da69bf526558d97 7aac0111a39741f59513c05b2d83dd70 - - -] Exception during message handling: 'ascii' codec can't encode characters in position 111-117: ordinal not in range(128) 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher Traceback (most recent call last): 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 142, in _dispatch_and_reply 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher executor_callback)) 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 186, in _dispatch 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher executor_callback) 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 129, in _do_dispatch 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher result = func(ctxt, **new_args) 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher File "/usr/lib/python2.7/dist-packages/osprofiler/profiler.py", line 102, in wrapper 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher info["function"]["kwargs"] = str(kwargs) 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher UnicodeEncodeError: 'ascii' codec can't encode characters in position 111-117: ordinal not in range(128) 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher Root cause is that profiler tries to get a string representation of the arguments (cinder.objects.snapshot.Snapshot) of the snapshot-create cinder-volume service api. As a result, VersionedObject.__repr__ is called to produce such a string representation with an attribute (display-description) containing non-ascii characters, thus returning an unicode object. However when __repr__ returns an unicode object, it's expected that the the returned string can be encoded by default encoding scheme which is ascii in general [1][2]. So __repr__ needs to make sure any unicode string it's going to return are properly encoded. [1] trying to encode the returned string when it's an unicode object https://github.com/python/cpython/blob/2.7/Objects/object.c#L387 [2] if encoding arg is left null, default encoding will be used https://github.com/python/cpython/blob/2.7/Objects/unicodeobject.c#L1355 ** Also affects: cinder (Ubuntu) Importance: Undecided Status: New ** Changed in: cinder (Ubuntu) Status: New => In Progress ** Changed in: cinder (Ubuntu) Assignee: (unassigned) => Liang Chen (cbjchen) -- 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/1514325 Title: VersionedObject.__repr__ should return encoded string To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1514325/+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 1514325] Re: VersionedObject.__repr__ should return encoded string
** Branch linked: lp:~cbjchen/cinder/lp1514325 -- 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/1514325 Title: VersionedObject.__repr__ should return encoded string To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1514325/+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 1514325] Re: VersionedObject.__repr__ should return encoded string
** Branch linked: lp:~cbjchen/cinder/lp1514325 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1514325 Title: VersionedObject.__repr__ should return encoded string To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1514325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1514325] Re: VersionedObject.__repr__ should return encoded string
** Description changed: - The following error is reported when creating a volume snapshot with - non-ascii display-description, e.g. cinder snapshot-create --display- - description "中文" my-2nd-volume. + [Impact] + + * Cinder snapshot display-description cannot contain non-ascii + characters. + + [Test Case] + + * cinder create 1 + * cinder snapshot-create --display-description "中文" + + [Regression Potential] + + * None + + + The following error is reported when creating a volume snapshot with non-ascii display-description, e.g. cinder snapshot-create --display-description "中文" my-2nd-volume. 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher [req-81f48a02-b1ef-4aae-9e22-ac2ce1c75b2f 16818cbff07548889da69bf526558d97 7aac0111a39741f59513c05b2d83dd70 - - -] Exception during message handling: 'ascii' codec can't encode characters in position 111-117: ordinal not in range(128) 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher Traceback (most recent call last): 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 142, in _dispatch_and_reply 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher executor_callback)) 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 186, in _dispatch 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher executor_callback) 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 129, in _do_dispatch 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher result = func(ctxt, **new_args) 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher File "/usr/lib/python2.7/dist-packages/osprofiler/profiler.py", line 102, in wrapper 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher info["function"]["kwargs"] = str(kwargs) 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher UnicodeEncodeError: 'ascii' codec can't encode characters in position 111-117: ordinal not in range(128) 2015-11-09 05:55:50.995 29937 ERROR oslo_messaging.rpc.dispatcher Root cause is that profiler tries to get a string representation of the arguments (cinder.objects.snapshot.Snapshot) of the snapshot-create cinder-volume service api. As a result, VersionedObject.__repr__ is called to produce such a string representation with an attribute (display-description) containing non-ascii characters, thus returning an unicode object. However when __repr__ returns an unicode object, it's expected that the the returned string can be encoded by default encoding scheme which is ascii in general [1][2]. So __repr__ needs to make sure any unicode string it's going to return are properly encoded. [1] trying to encode the returned string when it's an unicode object https://github.com/python/cpython/blob/2.7/Objects/object.c#L387 [2] if encoding arg is left null, default encoding will be used https://github.com/python/cpython/blob/2.7/Objects/unicodeobject.c#L1355 ** Also affects: cinder (Ubuntu) Importance: Undecided Status: New ** Changed in: cinder (Ubuntu) Status: New => In Progress ** Changed in: cinder (Ubuntu) Assignee: (unassigned) => Liang Chen (cbjchen) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1514325 Title: VersionedObject.__repr__ should return encoded string To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1514325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448092] Re: [needs-packaging] ibmpmlinux
Hi Mathieu, Thank you for your review to the detail. I now upload PMUbuntu files with a few minor changes regarding file mode & gzip -n that you suggested. The crontab message is normal for an uninitialized spool crontab file of root. PMUbuntu's cron entry is required to be created at /etc/cron.*, so our installation scripts need to ensure PM cron entry does not exist in spool/crontab, and delete it if found. If someone already has other entries in root's crontab, then there will be no error from crontab querying, and the scripts can continue to do whatever needed (likely nothing on Ubuntu if nobody installed PMUbuntu and adjusted the settings before). We still need /usr/sbin/config.PMLnx until Ubuntu can fully handle /opt. By now, the support of /opt is partially broken for all Ubuntu releases. For example, with default, root profile does not contain either /opt/man for manpage search, or /opt/(s)bin for executable search ($PATH). Maintainer scripts are also necessary for now. There are some flexibilities provided by PMUbuntu that the hard-coded package installers (dpkg/rpm) can not manipulate, such as directory layout selection and crontab/configuration rollback. ** Attachment added: "Enhanced PMLinux tar files and their result from dpkg-buildpackage" https://bugs.launchpad.net/ubuntu/+bug/1448092/+attachment/4524257/+files/ibmpmlinux_3.2.0-2_20151120.tar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448092 Title: [needs-packaging] ibmpmlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448092] Re: [needs-packaging] ibmpmlinux
Recent PMUbuntu tar file contains a few enhancements in symbol links repair up to today (2015-10-27). ** Attachment added: "Enhanced PMLinux tar files and their result from dpkg-buildpackage" https://bugs.launchpad.net/ubuntu/+bug/1448092/+attachment/4507007/+files/ibmpmlinux_3.2.0-1.tar_20151027 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448092 Title: [needs-packaging] ibmpmlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448092] Re: [needs-packaging] ibmpmlinux
Hi Mathieu,
Thank you for your quick review and response. I am uploading the new tar
file, with the following answers to your comments:
- Version for Ubuntu should be -0ubuntu1 rather than -1.
The '1' in the PMLinux version "3.2.0-1" is an initial build serial
number. PMLinux product is for all IBM-specific Linux platforms, some of
them dislike the build number starts from '0', nor suggest a long
repeated subfix (such as "-0ubuntu1") in their versioning. In fact, even
on Ubuntu, I only see half of deb packages having "ubuntu" in their
version strings.
- compat file should contain "9", not "5".
Changed as suggested, although we are unwilling to tight any
limitations.
- for debian/control, please use the following line in place of the Depends:
line for ibmpmlinux:
Depends: ${shlibs:Depends}, dialog (>= 0.8), bash (>= 3.0), ${misc:Depends}
Changed as suggested.
- no need for preinst or postrm. Running verify or uninstall in
postinst/prerm is most likely wrong.
That's the style converted into deb from rpm.
It could have problem only when PMLinux is kicked in before its dependencies
in system installation, which is unlikely for a leaf package.
Sharing common programs is a good thing, so is what we do here to eliminate
multiple copies existing in installation/upgrade and daily maintenance programs.
- no application should change crontab for the root user by editing the
file. If anything, it should instead ship a file in the right
directories in /etc/cron.d
Again, PMLinux is compatible for all Linux variants. It has diverse
options & features for users to choose. That program branches to change
crontab will not be reached on Ubuntu by default.
- rather than doing symlinks in postinst/prerm; the links should be
created using dh_links, a file debian/links will have to simply contain
the source and destination for the symlinks to create.
Again, that's rpm style converted into deb. It's just a way of self integrity
to eliminate any special dependencies on an installation environment.
For deb, PMLinux package already contains the major symlinks in the files
list, which can then be created by dpkg in installtion, and postinst is just to
verify if dpkg or rpm does it right.
- please use debian/install containing the following, rather than copying files
in debian/rules:
opt
etc
usr/share/man opt/
Added debian/install with the above content, except " opt/" (which
will ruin the man page feature under current Ubuntu releases, because
they still do not support (add /opt/man in searching paths) any files in
/opt/man/*)
- you don't need file copies, creating directories or any such thing using
override_dh_auto_build in debian/rules; instead, you can use the following:
override_dh_install:
mkdir $(CURDIR)/debian/tmp
tar -xpzf $(pkg_tgz) -C $(CURDIR)/debian/tmp
dh_install
Yes, optimized as you suggested.
- It will be easiest for you to get the package name and version like this:
package := $(shell dpkg-parsechangelog -S Source)
version := $(shell dpkg-parsechangelog -S Version | sed -e 's/-.*//')
Note that here I pick just what goes in front of the - for the version number.
No. dpkg-parsechangelog does not support "-S" option in Ubuntu 14.03
- please remove the line "override_dh_shlibdeps:" in debian/rules; this
will fill in ${shlibs:Depends} for you automatically with the right
version of libc.
Done as suggested.
- also, I suppose the PMLinux.8 manpage should be decompressed and let
dh_installman deal with it in debian/rules, to get rid of this lintian warning:
W: ibmpmlinux: package-contains-timestamped-gzip opt/man/man8/PMLinux.8.gz
This warning is not real but a lintian bug. Please see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762105.
Nothing looks wrong for gzipping PMLinux-deb.manual. Decompressing is not an
option because it makes a simple thing complicated and is merely to satisfy
lintian's unimportant hobby.
** Bug watch added: Debian Bug tracker #762105
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762105
** Attachment added: "Updated PMLinux tar files and their result from
dpkg-buildpackage"
https://bugs.launchpad.net/ubuntu/+bug/1448092/+attachment/4503535/+files/ibmpmlinux_3.2.0-1.tar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448092
Title:
[needs-packaging] ibmpmlinux
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1448092/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448092] Re: [needs-packaging] ibmpmlinux
Hi Mathieu, Thank you very much. Please review our new build ibmpmlinux_3.2.0-1.tar in the attachment which contains: -rw-r--r-- root/root 19460 2015-10-22 11:39 ibmpmlinux_3.2.0-1.debian.tar.xz -rw-r--r-- root/root523655 2015-10-22 11:39 ibmpmlinux_3.2.0.orig.tar.gz -rw-r--r-- root/root390764 2015-10-22 11:39 ibmpmlinux_3.2.0-1_ppc64el.deb for PMLinux Version 3.2.0-1 with all the necessary FHS compliance items implemented, as described in PMLinux compliance schedule.png in my note on 2015-10-13. If possible, we still hope to see PMLinux package available in Ubuntu 15.10 archive. ** Attachment added: "PMLinux tar files and their result from dpkg-buildpackage" https://bugs.launchpad.net/ubuntu/+bug/1448092/+attachment/4502520/+files/ibmpmlinux_3.2.0-1.tar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448092 Title: [needs-packaging] ibmpmlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448092] Re: [needs-packaging] ibmpmlinux
Hi Mathieu, The schedule for Ubuntu 15.10 to release is running out. Here we PMLinux team are wondering if there is time left for our package inclusion in Ubuntu 15.10 Archive repository? If time allows, we still want to submit a PMLinux update for review next week, with the major changes for FHS compliance included (detail enclosed in attachment), while leaving optional service/job enhancement for next Ubuntu release ** Attachment added: "PMLinux compliance schedule.png" https://bugs.launchpad.net/ubuntu/+bug/1448092/+attachment/4493749/+files/PMLinux%20compliance%20schedule.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448092 Title: [needs-packaging] ibmpmlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500684] Re: update to 5.6.20 or above for security fixes
** Changed in: mysql-5.6 (Ubuntu Trusty) Status: Triaged => In Progress ** Changed in: mysql-5.6 (Ubuntu Trusty) Assignee: (unassigned) => Liang Chen (cbjchen) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500684 Title: update to 5.6.20 or above for security fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1500684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500684] Re: update to 5.6.20 or above for security fixes
** Changed in: mysql-5.6 (Ubuntu Trusty) Status: Triaged => In Progress ** Changed in: mysql-5.6 (Ubuntu Trusty) Assignee: (unassigned) => Liang Chen (cbjchen) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1500684 Title: update to 5.6.20 or above for security fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1500684/+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 1500684] Re: update to 5.6.20 or above for security fixes
** Summary changed: - update to 5.6.20 for security fixes + update to 5.6.20 or above for security fixes -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1500684 Title: update to 5.6.20 or above for security fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1500684/+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 1500684] Re: update to 5.6.20 or above for security fixes
** Summary changed: - update to 5.6.20 for security fixes + update to 5.6.20 or above for security fixes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500684 Title: update to 5.6.20 or above for security fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1500684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504127] Re: grep -q gets broken pipe message with multiple expressions
** Package changed: ubuntu => bash (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504127 Title: grep -q gets broken pipe message with multiple expressions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1504127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446247] Re: Lubuntu 15.04 - No power indicator in applet indicator
By following the URL provided by Schneider, I managed to have the battery indicator back to work on Lubuntu 15.04(upgraded from 14.10). Here are my manual installation steps of xubuntu-staging without using 'apt-get dist-upgrade:' 1. goto https://launchpad.net/~xubuntu-dev/+archive/ubuntu/xubuntu-staging/+sourcepub/5186374/+listing-archive-extra and download packages based on your architecture. For example: $ wget https://launchpad.net/~xubuntu-dev/+archive/ubuntu/xubuntu-staging/+files/xfce4-power-manager-data_1.5.2-0ubuntu1%7E15.10_all.deb $ wget https://launchpad.net/~xubuntu-dev/+archive/ubuntu/xubuntu-staging/+files/xfce4-power-manager-plugins_1.5.2-0ubuntu1%7E15.10_amd64.deb $ wget https://launchpad.net/~xubuntu-dev/+archive/ubuntu/xubuntu-staging/+files/xfce4-power-manager_1.5.2-0ubuntu1%7E15.10_amd64.deb 2. get the latest libxfce4panel-2.0. For example: $ wget http://gb.archive.ubuntu.com/ubuntu/ubuntu/ubuntu/ubuntu/pool/universe/x/xfce4-panel/libxfce4panel-2.0-4_4.12.0-3ubuntu2_amd64.deb 3. install libxfce4-ui-2-0 for one of he required dependencies: $ sudo apt-get install libxfce4ui-2-0 4. update xfce4-power-manager to 1.5.x by installing .deb files downloaded in step 1 and 2: $ sudo dpkg -i libxfce4panel-2.0-4_4.12.0-3ubuntu2_amd64.deb xfce4-power-manager-data_1.5.2-0ubuntu1~15.10_all.deb xfce4-power-manager_1.5.2-0ubuntu1~15.10_amd64.deb xfce4-power-manager-plugins_1.5.2-0ubuntu1~15.10_amd64.deb 5. run xfce4-power-manager-settings command from the command line and then check that Status notifications and System tray icon are set to ON. 6. run xfce4-power-manager --restart from the command line -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446247 Title: Lubuntu 15.04 - No power indicator in applet indicator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1446247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448092] Re: [needs-packaging] ibmpmlinux
Hi Mathieu, Thank you very much for your hours in the review. It sounds you almost get to the bottom of PMUbuntu. > - ship a sysv init script in /etc/init.d/ (which should work both for 15.10 and all the way to 14.04) This means we need to modify PMUbuntu to be a service (or job in upstart term). It's fine but will take some time. > - ship all files in their paths under /opt/ibm/pm ... We will follow the requests that you mentioned here, but not necessary to replace every "/var/perf/pm" with PMUbuntu's new home because we still try to maintain PM programs good for all Linux variants. > We also don't appear to need the preinst, prerm, postrm files; That those scriptlets are installed to /debian is not what we expect at all. The scripts are for package install/upgrade/uninstall moments only and supposed to be stored in apt/dpkg internal database. > since running verify.PMLnx or uninstall.PMLnx cause incompatible paths to be added on the filesystem, or crontab to be changed, which aren't allowable as per the packaging policy. If we decide to move home for PMUbuntu, then there will be no incompatible paths created by the final .PMLnx programs. PM item in crontab will also be relocated into /etc/cron.* as per your request. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448092 Title: [needs-packaging] ibmpmlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448092] Re: [needs-packaging] ibmpmlinux
> Why should it be a blocker now that we are asking for ibmpmlinux to be installed to /opt instead? PMLinux has only one menu command for all of the user interfaces, "/var/perf/pm/config.PMLnx", which has a symbol link at /usr/sbin/config.PMLnx for root working well without $PATH setting. Now, as per Mathieu's request "putting *everything* under /opt" " to fulfill FHS standard, we have to move that public link into /opt/sbin, which will ruin the interface access, so does PMLinux man help if we also relocate PMLinux.8.gz from /usr/share/man to /opt/man. > Isn't it preferrable to have this software in the partner archive, with or > without /opt/bin path integration, than to not have it in the archive? Because Ubuntu is not ready for basic /opt support, what I hope is Ubuntu team still allows PMLinux continue to use /usr/sbin and /usr/share/man. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448092 Title: [needs-packaging] ibmpmlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448092] Re: [needs-packaging] ibmpmlinux
Thank you very much, Steve. > ... but lintian does not support analyzing such a package using the appropriate rules. Then, Ubuntu community should not reject a package destined for /opt, based on lintian's analysis output until that tool is fixed to comply with all FHS specifications. > Are there any technical blockers to placing the package's contents in > /opt/ibm/pm, with symlinks to /etc/opt/ibm/pm and /var/opt/ibm/pm > for the writable parts? Yes, but only Ubuntu system (iso) is the blocker. Administrator (root) can NOT run (& man) commands in /opt/(s)bin (& /opt/man) without the path because /opt/(s)bin are not included in $PATH by default when they exist. This is another Ubuntu bug (in user profile initialization) for unconditional enforcement of the FHS standard while the system is actually not ready for. Note: 1) As I tested, SuSE has supported /opt/(s)bin in $PATH if the directories exist, at least since sles10; Fedora/Red Hat/Ubuntu are not yet; 2) "man" will work fine because it was designed in the configuration to look into /opt/man once /opt/(s)bin appear in $PATH. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448092 Title: [needs-packaging] ibmpmlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500684] [NEW] update to 5.6.20 for security fixes
Public bug reported: A three year old security bug - MySQL Authentication Error Message User Enumeration Vulnerability still presents in trusty package. ** Affects: mysql-5.6 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1500684 Title: update to 5.6.20 for security fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1500684/+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 1500684] [NEW] update to 5.6.20 for security fixes
Public bug reported: A three year old security bug - MySQL Authentication Error Message User Enumeration Vulnerability still presents in trusty package. ** Affects: mysql-5.6 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500684 Title: update to 5.6.20 for security fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1500684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448092] Re: [needs-packaging] ibmpmlinux
>> Q: "Would it be possible to recompile just to replace /var/perf/pm with >> /opt/ibm/pm? " >> A: Although technically possible, it might raise questions on the viability >> of PM-Ubuntu project: >>1) For a FHS-compliant system, it is supposed to store "static" things >> only in /opt which may then be mounted for read only; > If this is truly an issue for you ... No, I don't mind at all. It is merely an issue for FHS which requires that only static stuff may be stored in /opt. > storing files in the proper paths in /usr/lib, and keeping just the very few > binaries > that are expected to ever be run by users in /usr/bin, is quite acceptable The thing is, IBM has PMLinux, ESA(Electronic Service Agent), RSCT(Reliable Scalable Cluster Technology) ... As I knew: ESA's traditional home is at /opt/ibm/esa/, and RSCT team has been struggling to move away from /usr/sbin/rsct/ for FHS compliance on Ubuntu. I hope RSCT's home to be decided at /opt/ibm/rsct/, then many IBM optional packages may stay closely. > The only thing that is being objected to is the use of paths in /var/perf; > which isn't FHS-compliant. > As I've expressed before, it is a requirement for packages in the archive to > follow Debian and Ubuntu packaging policies. That is fine and we shall comply with. What we keep asking is only to reserve that old address as a relocation sign for some moments. >> 2) There will be awful consequences to move home for PM (for IBM i, AIX, >> Linux, KVM ...) after we released the product more than a decade. > Why? Worry of big trouble in cross-platform customer support > On the contrary, this is why I am asking whether you can recompile these > binaries. > To know where to find their files, these programs must have it hard-coded > somewhere. This means this value can be changed. Technically, we just need to add an extra path in the list for configuration search. This is not a big deal in code/document revision. The major issue remains in cross-platform technical support. > I thought I had mentioned it in the previous comment, but maybe I forgot: > there's an additional issue > with keeping manual pages in /usr/share/man if the rest is shipped in /opt. > Packages shipping things > in /opt should ship *everything* in /opt, not pick and choose. This "everything in" condition in FHS standard is certainly ridiculous: First of all, Ubuntu itself has not yet complied with it: "man" does not look into /opt/man/ with current /etc/manpath.config, while /opt/bin/ is not included in $PATH by default. Secondly, we have evidences from PMLinux to feel it bad: 1) when we have intimate files (like .cfg & .help) and naturally want to keep them at local, FHS forces to separate them far away; 2) when we cooperatively distribute something (like PMUbuntu.8.gz) to a place acknowledged for system wide utilities (such as "man"), FHS still says no and we shall have to move them back to private. > While I agree I've given you both options, it seems as though with all the > coming data, it is likely > best to ship ibmpmlinux files in proper /usr tree instead, such as in the > initial packaging I provided > for review in the bug (which was still affected by the binaries' requirement > for arbitrary paths). There are some problems: 1) PMLinux is NOT a lib, and looks weird to exist in /usr/lib; 2) IBM ESA has been at /opt/ibm/esa/. It's good for PMLinux to be together with ESA who, among other things, services PMLinux's data transmission to IBM. By the way, have you found why lintian complained PMLinux at /opt/ibm/pm/ ? (I sent you the tar balls on Sep 17 by email) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448092 Title: [needs-packaging] ibmpmlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448092] Re: [needs-packaging] ibmpmlinux
Thank you Mathieu. Q: "Would it be possible to recompile just to replace /var/perf/pm with /opt/ibm/pm? " A: Although technically possible, it might raise questions on the viability of PM-Ubuntu project: 1) For a FHS-compliant system, it is supposed to store "static" things only in /opt which may then be mounted for read only; 2) There will be awful consequences to move home for PM (for IBM i, AIX, Linux, KVM ...) after we released the product more than a decade. Q: "This way we could have a PMLinux.cfg in a reasonable location and use it to guide binaries ..." A: Impossible. Program always runs first before configuration takes effect. It's the location of binaries that matters and guides where to find the configuration file, then knows where to store data and where to locate other things (such as sub-programs, text documents, temporary locks/buffers etc.). Q: "or have the binaries 'just work' without any config file present?" A: Yes, PM can works well with .cfg file absent. In this circumstance, PM must run in default patterns. However, if config file does not exist, there is no way to control PM behaves differently (off the defaults), particularly, under the specific directories layout on Ubuntu. Here I update the proposal (version 1.1, right sheet in the attachment) for your review for PM-Ubuntu with the files of static in /opt/ibm/pm and of dynamic in /var/opt/ibm/pm, except the manual's (static) still in the traditional place /usr/share/man. ** Attachment added: "PMLinux Dirs-Files layout with of static in /opt/ibm/pm/ and variable in /var/opt/ibm/pm/" https://bugs.launchpad.net/ubuntu/+bug/1448092/+attachment/4472742/+files/PMUbuntu%20opt-var%20proposal.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448092 Title: [needs-packaging] ibmpmlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448092] Re: [needs-packaging] ibmpmlinux
"should changing PM_HOME to point to the new directory instead of /var/perf/pm work instead of creating symlinks?" No, it won't work. PMLinux.cfg will not take effect because it is now separated from PMLinux binaries, and NOT at default searching locations. The solution is either one below: 1) Create some symbol links to fully regain the original layout So that we still run programs in /var/perf/pm/, but it becomes running them in /opt/ibm/pm/, while /opt/ibm/pm/bin/programs reading PMLinux.cfg in /opt/ibm/pm/config/ becomes finding it in /etc/opt/ibm/ 2) Reprogram PMLinux with distributed FHS layout Change PMLinux programs to find PMLinux in /etc/ibm/pm/ Then also need to correct documents to reflect the new locations. Of course, I prefer 1), and only if the original implementation is not an option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448092 Title: [needs-packaging] ibmpmlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448092] Re: [needs-packaging] ibmpmlinux
Thanks Mathieu. There are only two "public" symbol links in controversy: 1) /var/adm/perfmgr -> /var/perf/pm/ HMC/FSM/ESA services use it to find PMLinux data file for transmission. 2) /var/perf/pm -> /opt/ibm/pm/ PMLinux refers it to regain original files layout (virtual ) against Ubuntu FHS enforcement. Other three links involved are local (or "private"), and product owner should have flexibility to do so: /opt/ibm/pm/tmp -> /var/opt/ibm/pm/tmp/ /opt/ibm/pm/daily -> /var/opt/ibm/pm/daily/ /opt/ibm/pm/config -> /etc/opt/ibm/pm/ As you can see here, FHS compliance only has negative impact on PMLinux and makes simple files layout complicated. There is no evident advantage for installing PMLinux under /opt/ibm/pm than in /var/perf/pm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448092 Title: [needs-packaging] ibmpmlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448092] Re: [needs-packaging] ibmpmlinux
Hi Mathieu, Thank you a lot for your time spent in reviewing and rearranging PMLinux's dirs/files layout. Actually, Breno, Erwan and I etc. already discussed about FHS (FileSystem Hierarchy Standard) enforcement several weeks ago. The right home for PMLinux seemed to be at /opt/ibm/pm/. Accordingly, I had ever created a PMLinux package based on that new home (see middle column in the attachment). However, that newly built PMLinux package did not pass lintian’s validation either, with almost as many non-compliance complaints as for PMLinux's original .deb. In other words, lintian did not really comply with the FHS standard for itself! Regarding your suggestion at a different location /usr/lib/ibmpmlinux/. I am afraid it might still not satisfy lintian because this path is also unknown to lintian. If that has no problem, I'd like to change to /usr/lib/ibm/pm/ for possible compatibility issues in case other IBM products may face the same frustration in future. Please review the detailed layout at 3rd column in the attachment. In order to make PMLinux work as before, a few symbol links need to be created by PMLinux installation scripts (see bottom part in the attachment). If the links, such as /var/perf/pm pointing to PMLinux's new home, are not allowed, then PMLinux requires lots of modifications to be adapted for new layouts. Personally, I still prefer PMLinux’s current dirs/files layout (see 1st column in the attachment). As I think, FHS’s distribution style is only good for the essential kernel/utilities of Linux system. It is overdone for Ubuntu to discipline any independent applications with FHS, because not every product acts/sits very close to core system, and mixing up their files with others makes simple things complicated. Instead, small tree layout (Windows style) has its tremendous conveniences. "Will PMLinux still work properly if we move all the binaries to /usr/lib/ibmpmlinux, for example?" Yes, but only if PMLinux (programs) can manage to locate PMLinux.cfg. PMLinux was designed to find the parameters file in this sequence: as specified by command line option, in subdirectory "config" under the program's parent directory, or in default directory "/var/perf/pm/config". If PMLinux.cfg not found (like sitting inside /etc without a link reference), PMLinux will run at /var/perf/pm with hard-coded default options. "Could we please have a new copy of the documentation with paths changed?" As commented above, if we are allowed to create a few symbol links to regain the original layout, then nothing in the documents needs correction. Otherwise, many codes & documents need to be changed and tested – There will be no quick answer in this tough circumstance. ** Attachment added: "PMLinux Dirs-Files layouts for PM home at /var/perf/pm, /opt/ibm/pm, or /usr/lib/ibm/pm" https://bugs.launchpad.net/ubuntu/+bug/1448092/+attachment/4466417/+files/PMLinux%20Dirs-Files%20Layouts.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448092 Title: [needs-packaging] ibmpmlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448092] Re: [needs-packaging] ibmpmlinux
Hi Mathieu, As I just checked today, ibmPMLinux package was still NOT archived in Ubuntu 1510's daily builds (http://cdimage.ubuntu.com/ubuntu- server/daily/current/wily-server-ppc64el.iso). Accordingly, I have not yet got a chance to test PMLinux package being installed from Ubuntu iso. The time seems running out of the schedule for PMLinux to join Ubuntu 1510. I am wondering how the acceptance procedure is going on? Please let me know once green light is given from the review. There will be new PMLinux tar balls with recent feature enhancement/bug fix for update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448092 Title: [needs-packaging] ibmpmlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448092] Re: [needs-packaging] ibmpmlinux
Mathieu, thank you very much for your response with an encouraging progress update. Please tell us the detailed time line (schedule) of Ubuntu 15.10. We may provide new up-to-date tar balls to be built in before the release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448092 Title: [needs-packaging] ibmpmlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457517] Re: Unable to boot from volume when flavor disk too small
** Description changed:
+ [Impact]
+
+ * Without the backport, booting from volume requires flavor disk size
+ larger than volume size, which is wrong. This patch skips flavor disk
+ size checking when booting from volume.
+
+ [Test Case]
+
+ * 1. create a bootable volume
+2. boot from this bootable volume with a flavor that has disk size smaller
than the volume size
+3. error should be reported complaining disk size too small
+4. apply this patch
+5. boot from that bootable volume with a flavor that has disk size smaller
than the volume size again
+6. boot should succeed
+
+ [Regression Potential]
+
+ * none
+
+
Version: 1:2015.1.0-0ubuntu1~cloud0 on Ubuntu 14.04
I attempt to boot an instance from a volume:
nova boot --nic net-id=[NET ID] --flavor v.512mb --block-device
source=volume,dest=volume,id=[VOLUME
ID],bus=virtio,device=vda,bootindex=0,shutdown=preserve vm
This results in nova-api raising a FlavorDiskTooSmall exception in the
_check_requested_image function in compute/api.py. However, according
to [1], the root disk limit should not apply to volumes.
[1] http://docs.openstack.org/admin-guide-cloud/content/customize-
flavors.html
Log (first line is debug output I added showing that it's looking at the
image that the volume was created from):
2015-05-21 10:28:00.586 25835 INFO nova.compute.api
[req-1fb882c7-07ae-4c2b-86bd-3d174602d0ae f438b80d215c42efb7508c59dc80940c
8341c85ad9ae49408fa25074adba0480 - - -] image: {'min_disk': 0, 'status':
'active', 'min_ram': 0, 'properties': {u'container_format': u'bare',
u'min_ram': u'0', u'disk_format': u'qcow2', u'image_name': u'Ubuntu 14.04
64-bit', u'image_id': u'cf0dffef-30ef-4032-add0-516e88048d85',
u'libvirt_cpu_mode': u'host-passthrough', u'checksum':
u'76a965427d2866f006ddd2aac66ed5b9', u'min_disk': u'0', u'size': u'255524864'},
'size': 21474836480}
2015-05-21 10:28:00.587 25835 INFO nova.api.openstack.wsgi
[req-1fb882c7-07ae-4c2b-86bd-3d174602d0ae f438b80d215c42efb7508c59dc80940c
8341c85ad9ae49408fa25074adba0480 - - -] HTTP exception thrown: Flavor's disk is
too small for requested image.
Temporary solution: I have special flavor for volume-backed instances so I
just set the root disk on those to 0, but this doesn't work if volume are used
on other flavors.
Reproduce: create flavor with 1 GB root disk size, then try to boot an
instance from a volume created from an image that is larger than 1 GB.
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nova (Ubuntu)
Assignee: (unassigned) = Liang Chen (cbjchen)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1457517
Title:
Unable to boot from volume when flavor disk too small
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1457517/+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 1457517] Re: Unable to boot from volume when flavor disk too small
** Description changed:
+ [Impact]
+
+ * Without the backport, booting from volume requires flavor disk size
+ larger than volume size, which is wrong. This patch skips flavor disk
+ size checking when booting from volume.
+
+ [Test Case]
+
+ * 1. create a bootable volume
+2. boot from this bootable volume with a flavor that has disk size smaller
than the volume size
+3. error should be reported complaining disk size too small
+4. apply this patch
+5. boot from that bootable volume with a flavor that has disk size smaller
than the volume size again
+6. boot should succeed
+
+ [Regression Potential]
+
+ * none
+
+
Version: 1:2015.1.0-0ubuntu1~cloud0 on Ubuntu 14.04
I attempt to boot an instance from a volume:
nova boot --nic net-id=[NET ID] --flavor v.512mb --block-device
source=volume,dest=volume,id=[VOLUME
ID],bus=virtio,device=vda,bootindex=0,shutdown=preserve vm
This results in nova-api raising a FlavorDiskTooSmall exception in the
_check_requested_image function in compute/api.py. However, according
to [1], the root disk limit should not apply to volumes.
[1] http://docs.openstack.org/admin-guide-cloud/content/customize-
flavors.html
Log (first line is debug output I added showing that it's looking at the
image that the volume was created from):
2015-05-21 10:28:00.586 25835 INFO nova.compute.api
[req-1fb882c7-07ae-4c2b-86bd-3d174602d0ae f438b80d215c42efb7508c59dc80940c
8341c85ad9ae49408fa25074adba0480 - - -] image: {'min_disk': 0, 'status':
'active', 'min_ram': 0, 'properties': {u'container_format': u'bare',
u'min_ram': u'0', u'disk_format': u'qcow2', u'image_name': u'Ubuntu 14.04
64-bit', u'image_id': u'cf0dffef-30ef-4032-add0-516e88048d85',
u'libvirt_cpu_mode': u'host-passthrough', u'checksum':
u'76a965427d2866f006ddd2aac66ed5b9', u'min_disk': u'0', u'size': u'255524864'},
'size': 21474836480}
2015-05-21 10:28:00.587 25835 INFO nova.api.openstack.wsgi
[req-1fb882c7-07ae-4c2b-86bd-3d174602d0ae f438b80d215c42efb7508c59dc80940c
8341c85ad9ae49408fa25074adba0480 - - -] HTTP exception thrown: Flavor's disk is
too small for requested image.
Temporary solution: I have special flavor for volume-backed instances so I
just set the root disk on those to 0, but this doesn't work if volume are used
on other flavors.
Reproduce: create flavor with 1 GB root disk size, then try to boot an
instance from a volume created from an image that is larger than 1 GB.
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nova (Ubuntu)
Assignee: (unassigned) = Liang Chen (cbjchen)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457517
Title:
Unable to boot from volume when flavor disk too small
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1457517/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1348244] Re: debug log messages need to be unicode
@Sebastien, The fix for Nova is merged at LP#1459046. cinder patch is still needed. But the current cinder patch is unnecessarily big, it can be done more easily as LP#1459046 does. I will remove the cinder patch for now, and propose a simpler one later. Thanks. ** Patch removed: trusty cinder debdiff https://bugs.launchpad.net/nova/+bug/1348244/+attachment/4416906/+files/cinder-2014.1.4-0ubuntu3-lp1348244.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1348244 Title: debug log messages need to be unicode To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1348244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1348244] Re: debug log messages need to be unicode
@Sebastien, The fix for Nova is merged at LP#1459046. cinder patch is still needed. But the current cinder patch is unnecessarily big, it can be done more easily as LP#1459046 does. I will remove the cinder patch for now, and propose a simpler one later. Thanks. ** Patch removed: trusty cinder debdiff https://bugs.launchpad.net/nova/+bug/1348244/+attachment/4416906/+files/cinder-2014.1.4-0ubuntu3-lp1348244.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1348244 Title: debug log messages need to be unicode To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1348244/+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 1196924] Re: Stop and Delete operations should give the Guest a chance to shutdown
The proposed build have been deployed and tested, and this work as expected. ** 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 nova in Ubuntu. https://bugs.launchpad.net/bugs/1196924 Title: Stop and Delete operations should give the Guest a chance to shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1196924/+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 1196924] Re: Stop and Delete operations should give the Guest a chance to shutdown
The proposed build have been deployed and tested, and this work as expected. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1196924 Title: Stop and Delete operations should give the Guest a chance to shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1196924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1353939] Re: Rescue fails with 'Failed to terminate process: Device or resource busy' in the n-cpu log
** Description changed: + [Impact] + + * Users may sometimes fail to shutdown an instance if the associated qemu +process is on uninterruptable sleep (typically IO). + + [Test Case] + + * 1. create some IO load in a VM +2. look at the associated qemu, make sure it has STAT D in ps output +3. shutdown the instance +4. with the patch in place, nova will retry calling libvirt to shutdown + the instance 3 times to wait for the signal to be delivered to the + qemu process. + + [Regression Potential] + + * None + + message: Failed to terminate process AND message:'InstanceNotRescuable' AND message: 'Exception during message handling' AND tags:screen-n-cpu.txt The above log stash-query reports back only the failed jobs, the 'Failed to terminate process' close other failed rescue tests, but tempest does not always reports them as an error at the end. message: Failed to terminate process AND tags:screen-n-cpu.txt Usual console log: Details: (ServerRescueTestJSON:test_rescue_unrescue_instance) Server 0573094d-53da-40a5-948a-747d181462f5 failed to reach RESCUE status and task state None within the required time (196 s). Current status: SHUTOFF. Current task state: None. http://logs.openstack.org/82/107982/2/gate/gate-tempest-dsvm-postgres- full/90726cb/console.html#_2014-08-07_03_50_26_520 Usual n-cpu exception: http://logs.openstack.org/82/107982/2/gate/gate-tempest-dsvm-postgres-full/90726cb/logs/screen-n-cpu.txt.gz#_2014-08-07_03_32_02_855 2014-08-07 03:32:02.855 ERROR oslo.messaging.rpc.dispatcher [req-39ce7a3d-5ceb-41f5-8f9f-face7e608bd1 ServerRescueTestJSON-2035684545 ServerRescueTestJSON-1017508309] Exception during message handling: Instance 0573094d-53da-40a5-948a-747d181462f5 cannot be rescued: Driver Error: Failed to terminate process 26425 with SIGKILL: Device or resource busy 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last): 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 134, in _dispatch_and_reply 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher incoming.message)) 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 177, in _dispatch 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher return self._do_dispatch(endpoint, method, ctxt, args) 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 123, in _do_dispatch 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher result = getattr(endpoint, method)(ctxt, **new_args) 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/new/nova/nova/compute/manager.py, line 408, in decorated_function 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher return function(self, context, *args, **kwargs) 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/new/nova/nova/exception.py, line 88, in wrapped 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher payload) 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/new/nova/nova/openstack/common/excutils.py, line 82, in __exit__ 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher six.reraise(self.type_, self.value, self.tb) 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/new/nova/nova/exception.py, line 71, in wrapped 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher return f(self, context, *args, **kw) 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/new/nova/nova/compute/manager.py, line 292, in decorated_function 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher pass 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/new/nova/nova/openstack/common/excutils.py, line 82, in __exit__ 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher six.reraise(self.type_, self.value, self.tb) 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/new/nova/nova/compute/manager.py, line 278, in decorated_function 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher return function(self, context, *args, **kwargs) 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher File /opt/stack/new/nova/nova/compute/manager.py, line 342, in decorated_function 2014-08-07 03:32:02.855 22829 TRACE oslo.messaging.rpc.dispatcher return function(self, context, *args, **kwargs) 2014-08-07 03:32:02.855 22829 TRACE
