systemd-detect-virt is missing on Groovy EC2 AMI

Bug #1902260 reported by Balint Reczey
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-images
Fix Released
Critical
Unassigned
livecd-rootfs (Ubuntu)
Fix Released
Critical
Unassigned
Xenial
Fix Released
Undecided
Unassigned
Bionic
Fix Released
Undecided
Unassigned
Focal
Fix Released
Undecided
Unassigned
Groovy
Fix Released
Critical
Unassigned

Bug Description

[Impact]

 * On some image types, systemd-detect-virt might be missing

[Test Case]

 * $ sudo systemd-detect-virt

Should print a word.

If it prints "no such file or directory" it is buggy.

Best reproduced on initrdless boot, public cloud, where kernel flavour is switched, such as GCP groovy or AWS EC2 groovy. However other image types might be affected too.

Backporting the change to all series, in case there are other places which invoke undivert_grub multiple times in a row.

[Where problems could occur]

 * Hopefully, systemd-detect-virt undivert is now correct. Issues might happen in case systemd is not meant to be installed and yet the file remains on disk; or if the diversion is not removed still. Resulting in incorrect runtime behaviour.

 * For the images where this is fixed, systemd-detect-virt will now start working correctly. Thus may trigger automation to run that relied on missing systemd-detect-virt and thus previously did not execute.

[Other Info]

 * Original bug report

ubuntu/images/hvm-ssd/ubuntu-groovy-20.10-arm64-server-20201022.1

ubuntu@ip-172-31-30-199:~$ dpkg -S systemd-detect-virt
systemd: /usr/bin/systemd-detect-virt
systemd: /usr/share/bash-completion/completions/systemd-detect-virt
systemd: /usr/share/man/man1/systemd-detect-virt.1.gz
ubuntu@ip-172-31-30-199:~$ ls /usr/bin/systemd-detect-virt
ls: cannot access '/usr/bin/systemd-detect-virt': No such file or directory

Since livecd-rootfs plays with diversions of this file it looks suspicious, but I have not fully triaged the problem.

LXD image for amd64 seems to be ok: ubuntu 20.10 amd64 (release) (20201022.1)

Related branches

Balint Reczey (rbalint)
tags: added: rls-gg-incoming
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

maybe we should run debsums as part of the build then.

Revision history for this message
John Chittum (jchittum) wrote :

Confirmed not just for arm64, but also latest amd64 groovy builds

amd64 ami: ubuntu/images-testing/hvm-ssd/ubuntu-groovy-daily-amd64-server-20201104

~$ uname -a
Linux ip-172-31-92-148 5.8.0-1011-aws #11-Ubuntu SMP Thu Oct 22 10:15:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

~$ dpkg -S systemd-detect-virt
systemd: /usr/bin/systemd-detect-virt
systemd: /usr/share/bash-completion/completions/systemd-detect-virt
systemd: /usr/share/man/man1/systemd-detect-virt.1.gz
~$ ls /usr/bin/systemd-detect-virt
ls: cannot access '/usr/bin/systemd-detect-virt': No such file or directory

arm64 ami: ubuntu/images-testing/hvm-ssd/ubuntu-groovy-daily-arm64-server-20201104
~$ uname -a
Linux ip-172-31-52-203 5.8.0-1011-aws #11-Ubuntu SMP Thu Oct 22 10:16:43 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux
~$ dpkg -S systemd-detect-virt
systemd: /usr/bin/systemd-detect-virt
systemd: /usr/share/bash-completion/completions/systemd-detect-virt
systemd: /usr/share/man/man1/systemd-detect-virt.1.gz
~$ ls /usr/bin/systemd-detect-virt
ls: cannot access '/usr/bin/systemd-detect-virt': No such file or directory

compared to latest focal release:

arm64 ami: 099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200720

~$ uname -a
Linux ip-172-31-48-176 5.4.0-1020-aws #20-Ubuntu SMP Fri Jul 10 05:53:22 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux
~$ dpkg -S systemd-detect-virt
systemd: /usr/bin/systemd-detect-virt
systemd: /usr/share/bash-completion/completions/systemd-detect-virt
systemd: /usr/share/man/man1/systemd-detect-virt.1.gz
~$ ls /usr/bin/systemd-detect-virt
/usr/bin/systemd-detect-virt

John Chittum (jchittum)
summary: - systemd-detect-virt is missing on Groovy arm64 EC2 AMI
+ systemd-detect-virt is missing on Groovy EC2 AMI
Changed in cloud-images:
status: New → Confirmed
tags: added: fr-923
tags: removed: rls-gg-incoming
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

also in hirsute

Changed in cloud-images:
importance: Undecided → Critical
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

replace_kernel function may optionally call force_boot_without_initramfs

which then can optionally call divert_grub / update-grub / undivert_grub again.

However, I think replace kernel can only work if grub is diverted or was not yet installed. Thus i'm not sure it is a good idea for force_boot_without_initramfs to do divert_grub and to call update-grub.

Changed in livecd-rootfs (Ubuntu):
importance: Undecided → Critical
status: New → Triaged
Changed in livecd-rootfs (Ubuntu Groovy):
importance: Undecided → Critical
status: New → Triaged
no longer affects: cloud-images/groovy
Revision history for this message
John Chittum (jchittum) wrote :

also affects other cloud-images beyond ec2. confirmed in GCE as well, and may affect other clouds.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package livecd-rootfs - 2.711

---------------
livecd-rootfs (2.711) hirsute; urgency=medium

  * Perform fsck on all rootfs. (LP: #1912835)
  * functions: stop removing systemd-detect-virt unconditionally in undivert_grub
    (LP: #1902260)

 -- Dimitri John Ledkov <email address hidden> Fri, 05 Feb 2021 12:48:44 +0000

Changed in livecd-rootfs (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Please test proposed package

Hello Balint, or anyone else affected,

Accepted livecd-rootfs into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.694.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-groovy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in livecd-rootfs (Ubuntu Groovy):
status: Triaged → Fix Committed
tags: added: verification-needed verification-needed-groovy
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Hello Balint, or anyone else affected,

Accepted livecd-rootfs into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.664.17 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in livecd-rootfs (Ubuntu Focal):
status: New → Fix Committed
tags: added: verification-needed-focal
Changed in livecd-rootfs (Ubuntu Bionic):
status: New → Fix Committed
tags: added: verification-needed-bionic
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Hello Balint, or anyone else affected,

Accepted livecd-rootfs into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.525.51 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

description: updated
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Hello Balint, or anyone else affected,

Accepted livecd-rootfs into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.408.66 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in livecd-rootfs (Ubuntu Xenial):
status: New → Fix Committed
tags: added: verification-needed-xenial
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (livecd-rootfs/2.408.66)

All autopkgtests for the newly accepted livecd-rootfs (2.408.66) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-image/1.10+16.04ubuntu1 (arm64, i386, s390x, amd64, ppc64el)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#livecd-rootfs

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

From https://launchpad.net/~xnox/+livefs/ubuntu/groovy/any/+build/259784

downloading the vmdk image

mounting p15 i can see that /ubuntu/ paths now exist, and will be used for booting via BOOTX64.CSV

 tree /mnt/
/mnt/
└── EFI
    ├── BOOT
    │   ├── BOOTX64.EFI
    │   ├── fbx64.efi
    │   └── mmx64.efi
    └── ubuntu
        ├── BOOTX64.CSV
        ├── grub.cfg
        ├── grubx64.efi
        ├── mmx64.efi
        └── shimx64.efi

3 directories, 8 files

Mounting the p1 partition I can see that fsck will be performed on both partitions

$ cat /mnt/etc/fstab
LABEL=cloudimg-rootfs / ext4 defaults 0 1
LABEL=UEFI /boot/efi vfat defaults 0 1

$ /mnt/usr/bin/systemd-detect-virt
none

can be executed and is present (although this image would not have triggered the bug of missing systemd-detect-virt, this bug would need to be verified elsewhere)

tags: added: verification-done-groovy
removed: verification-needed-groovy
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

From https://launchpad.net/~xnox/+livefs/ubuntu/focal/any/+build/259783

downloading the .img (qcow) image

mounting p15 i can see that /ubuntu/ paths now exist, and will be used for booting via BOOTX64.CSV

 tree /mnt/
/mnt/
└── EFI
    ├── BOOT
    │ ├── BOOTX64.EFI
    │ ├── fbx64.efi
    │ └── mmx64.efi
    └── ubuntu
        ├── BOOTX64.CSV
        ├── grub.cfg
        ├── grubx64.efi
        ├── mmx64.efi
        └── shimx64.efi

3 directories, 8 files

Mounting the p1 partition I can see that fsck will be performed on both partitions

$ cat /mnt/etc/fstab
LABEL=cloudimg-rootfs / ext4 defaults 0 1
LABEL=UEFI /boot/efi vfat defaults 0 1

$ LD_PRELOAD=/mnt/usr/lib/systemd/libsystemd-shared-245.so /mnt/usr/bin/systemd-detect-virt
none

can be executed and is present (although this image would not have triggered the bug of missing systemd-detect-virt, this bug would need to be verified elsewhere)

tags: added: verification-done-focal
removed: verification-needed-focal
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

rom https://launchpad.net/~xnox/+livefs/ubuntu/bionic/any/+build/259782

downloading the .img (qcow) image

mounting p15 i can see that /ubuntu/ paths now exist, and will be used for booting via BOOTX64.CSV

$ tree /mnt/
/mnt/
└── EFI
    ├── BOOT
    │ ├── BOOTX64.EFI
    │ └── fbx64.efi
    └── ubuntu
        ├── BOOTX64.CSV
        ├── grub.cfg
        ├── grubx64.efi
        ├── mmx64.efi
        └── shimx64.efi

3 directories, 7 files

Mounting the p1 partition I can see that fsck will be performed on both partitions

$ cat /mnt/etc/fstab
LABEL=cloudimg-rootfs / ext4 defaults 0 1
LABEL=UEFI /boot/efi vfat defaults 0 1

$ sudo chroot /mnt/ /usr/bin/systemd-detect-virt
Failed to check for virtualization: No such file or directory

can be executed and is present (although this image would not have triggered the bug of missing systemd-detect-virt, this bug would need to be verified elsewhere)

tags: added: verification-done-bionic
removed: verification-needed-bionic
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

From https://launchpad.net/~xnox/+livefs/ubuntu/xenial/any/+build/259781

downloading the livecd.ubuntu-cpc.uefi1.img image.

mounting p1 i can see that:

$ cat /mnt/etc/fstab
LABEL=cloudimg-rootfs / ext4 defaults 0 1
LABEL=UEFI /boot/efi vfat defaults 0 1

fsck will be performed

$ file /mnt/usr/bin/systemd-detect-virt
/mnt/usr/bin/systemd-detect-virt: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=48194abca8f0a3e7b9e698e2dcf114e787057a00, stripped

systemd-detect-virt exists. Although the bug in question would not be triggered on any xenial images.

tags: added: verification-done verification-done-xenial
removed: verification-needed verification-needed-xenial
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Please test proposed package

Hello Balint, or anyone else affected,

Accepted livecd-rootfs into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.408.67 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

tags: added: verification-needed verification-needed-xenial
removed: verification-done verification-done-xenial
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (livecd-rootfs/2.408.67)

All autopkgtests for the newly accepted livecd-rootfs (2.408.67) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-image/1.10+16.04ubuntu1 (s390x, ppc64el, amd64, arm64, i386)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#livecd-rootfs

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

https://launchpad.net/~xnox/+livefs/ubuntu/xenial/any/+build/259925

Get:89 http://ftpmaster.internal/ubuntu xenial-proposed/main amd64 livecd-rootfs amd64 2.408.67 [73.6 kB]

downloading uefi image

p15 is bootable

$ tree /mnt/
/mnt/
├── boot
│   └── grub
│   └── grub.cfg
└── EFI
    └── BOOT
        ├── BOOTX64.EFI
        ├── grub.cfg
        ├── grubx64.efi
        └── mmx64.efi

with removable paths only.

p1 has fsck and systemd-detect-virt is real:

$ cat /mnt/etc/fstab
LABEL=cloudimg-rootfs / ext4 defaults 0 1
LABEL=UEFI /boot/efi vfat defaults 0 1

$ file /mnt/usr/bin/systemd-detect-virt
/mnt/usr/bin/systemd-detect-virt: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=48194abca8f0a3e7b9e698e2dcf114e787057a00, stripped

tags: added: verification-done verification-done-xenial
removed: verification-needed verification-needed-xenial
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package livecd-rootfs - 2.694.3

---------------
livecd-rootfs (2.694.3) groovy; urgency=medium

  [ David Krauser ]
  * buildd: produce kernel and initrd as separate artifacts LP: #1910557
  * buildd: call update-initramfs for all installed kernels
    We only have one kernel installed, so we don't need to
    specify an explicit version. LP: #1910557

  [ Dimitri John Ledkov ]
  * esp: install grub in ubuntu bootloader id path, instead of removable.
    (LP: #1912830)
  * esp: perform fsck. (LP: #1912835)
  * Perform fsck on all rootfs. (LP: #1912835)
  * functions: stop removing systemd-detect-virt unconditionally in undivert_grub
    (LP: #1902260)

livecd-rootfs (2.694.2) groovy; urgency=medium

  [ Cody Shepherd ]
  * Create manifests for buildd tarball images (LP: #1914445)

 -- Dimitri John Ledkov <email address hidden> Tue, 09 Feb 2021 00:40:38 +0000

Changed in livecd-rootfs (Ubuntu Groovy):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package livecd-rootfs - 2.664.17

---------------
livecd-rootfs (2.664.17) focal; urgency=medium

  [ David Krauser ]
  * buildd: produce kernel and initrd as separate artifacts LP: #1910557
  * buildd: call update-initramfs for all installed kernels
    We only have one kernel installed, so we don't need to
    specify an explicit version. LP: #1910557

  [ Dimitri John Ledkov ]
  * esp: install grub in ubuntu bootloader id path, instead of removable.
    (LP: #1912830)
  * esp: perform fsck. (LP: #1912835)
  * Perform fsck on all rootfs. (LP: #1912835)
  * functions: stop removing systemd-detect-virt unconditionally in undivert_grub
    (LP: #1902260)

livecd-rootfs (2.664.16) focal; urgency=medium

  [ Cody Shepherd ]
  * Produce manifests for buildd tarball images (LP: #1914445)

 -- Dimitri John Ledkov <email address hidden> Tue, 09 Feb 2021 00:52:00 +0000

Changed in livecd-rootfs (Ubuntu Focal):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package livecd-rootfs - 2.525.51

---------------
livecd-rootfs (2.525.51) bionic; urgency=medium

  [ David Krauser ]
  * buildd: produce kernel and initrd as separate artifacts LP: #1910557
  * buildd: call update-initramfs for all installed kernels
    We only have one kernel installed, so we don't need to
    specify an explicit version. LP: #1910557

  [ Dimitri John Ledkov ]
  * esp: install grub in ubuntu bootloader id path, instead of removable.
    (LP: #1912830)
  * esp: perform fsck. (LP: #1912835)
  * Perform fsck on all rootfs. (LP: #1912835)
  * functions: stop removing systemd-detect-virt unconditionally in undivert_grub
    (LP: #1902260)

livecd-rootfs (2.525.50) bionic; urgency=medium

  [ Cody Shepherd ]
  * Create manifests for buildd tarball images (LP: #1914445)

 -- Dimitri John Ledkov <email address hidden> Tue, 09 Feb 2021 00:59:37 +0000

Changed in livecd-rootfs (Ubuntu Bionic):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package livecd-rootfs - 2.408.67

---------------
livecd-rootfs (2.408.67) xenial; urgency=medium

  * Revert "esp: install grub in ubuntu bootloader id path, instead of
    removable." as xenial's grub doesn't support shim fallback mode.

livecd-rootfs (2.408.66) xenial; urgency=medium

  [ David Krauser ]
  * buildd: produce kernel and initrd as separate artifacts LP: #1910557
  * buildd: call update-initramfs for all installed kernels
    We only have one kernel installed, so we don't need to
    specify an explicit version. LP: #1910557

  [ Dimitri John Ledkov ]
  * esp: install grub in ubuntu bootloader id path, instead of removable.
  * esp: perform fsck. (LP: #1912835)
  * Perform fsck on all rootfs. (LP: #1912835)
  * functions: stop removing systemd-detect-virt unconditionally in undivert_grub
    (LP: #1902260)

 -- Dimitri John Ledkov <email address hidden> Wed, 10 Feb 2021 13:00:48 +0000

Changed in livecd-rootfs (Ubuntu Xenial):
status: Fix Committed → Fix Released
John Chittum (jchittum)
Changed in cloud-images:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.