Is there any reason to keep comment 0 on a Fedora bug private?
(In reply to Ján Tomko from comment #1) > Is there any reason to keep comment 0 on a Fedora bug private? The cloning brought some private links with it. If it's preferable, I can close this bug and open a "cleaner" bug.
In general, a cloned bug should always have the Comment 0 sanitized (including ), and the bug should be created as public (barring any other restrictions, such as a security issue). Sanitation should include: * removing the original BZ from the "Clone of" field if the original was private. * removing links to private mailing lists * sensitive data in logs * info about Red Hat release schedules * customer names/details Any of this private information which is necessary for the new public bug (including a pointer to the original BZ, which may really be all you need) can be included in Comment 1, which can then be marked private. The above is doubly true for Fedora and upstream bugs - although in the case of libvirt the bugs are usually worked on by someone employed by Red Hat, this is not always the case. Many people working on Fedora have no direct official association with Red Hat. Since ovirt is a public project, if you will want to reference this BZ anywhere in ovirt release notes, mailing list, etc, you will need a public BZ. People tend to get irate when they are referred to an inaccessible page :-)
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
The patch is: commit 4b4aade59a206b6146d90d87d591386f8fbd68d1 Author: Peter Krempa <pkrempa> Date: Fri Sep 11 17:34:18 2015 +0200 qemu: hotplug: Properly clean up drive backend if frontend hotplug fails Commit 8125113c added code that should remove the disk backend if the fronted hotplug failed for any reason. The code had a bug though as it used the disk string for unplug rather than the backend alias. Fix the code by pre-creating an alias string and using it instead of the disk string. In cases where qemu does not support QEMU_CAPS_DEVICE, we ignore the unplug of the backend since we can't really create an alias in that case. F21 is end of life soon, so let's just pull this in to f22+
libvirt-1.2.13.2-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-2c9678da8c
libvirt-1.2.13.2-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-2c9678da8c
libvirt-1.2.13.2-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.