I have a btrfs volume with two devices mounted on /mnt/test: # mkfs.btrfs /dev/vdb2 /dev/vdb3 # mount /dev/vdb2 /mnt/test In python-blivet 0.54, following code prints mountpoint of /dev/vdb3: b = blivet.Blivet() b.reset() vdb3 = b.devicetree.getDeviceByName('vdb3') # we know that vdb3 contains btrfs... children = b.deviceDeps(vdb3) c = children[0] print c.format.mountpoint /mnt/test With python-blivet-0.61, it prints None. This is API change and it breaks OpenLMI.
This was changed unintentionally by commit 822d92457e36768b. I expect we'll be reverting that commit to fix this bug.
Note that fix is acked and ready to go.
I found out the standard process for proposing a blocker, which doesn't just involve setting it to block the blocker bug, so I'll try that.
Proposed as a Blocker for 21-alpha by Fedora user mulhern using the blocker tracking app because: The change fixes a regression introduced in commit 822d92457e36768b9daa6a3ec689e494e9ba07df. It affects openlmi btrfs related actions. The fix is simple, acked, and ready to go.
This sounds more like freeze exception than blocker stuff to me - in the Fedora process we have a specific status for 'things that we want to put through the freeze, but don't actually break the release criteria': https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process We can certainly consider this as a release blocker, but the criteria for Alpha storage are fairly minimal, and my guess is it'd be rejected: https://fedoraproject.org/wiki/Fedora_21_Alpha_Release_Criteria so unless you actually think we need to *block* the release on this, as opposed to just wanting to pull the fix through the freeze, we could go for 'freeze exception' not blocker status.
Proposed as a Freeze Exception for 21-alpha by Fedora user mulhern using the blocker tracking app because: The change fixes a regression introduced in commit 822d92457e36768b9daa6a3ec689e494e9ba07df. It affects openlmi btrfs related actions. The fix is simple, acked, and ready to go.
Were you able to convert the bug from a blocker to an FE using the blocker reporting webapp? If not, we should probably look at that...
No, I was not able to figure out conversion, I figured that the propose link would do the swap, i.e., if proposed as freeze would remove from proposed blockers, but that did not work. Now it is both a blocker and a freeze, please treat as freeze.
https://fedorahosted.org/fedora-qa/ticket/453
https://phab.qadevel.cloud.fedoraproject.org/T320 ...
Discussed in 2014-09-03 Blocker Review Meeting. Voted as an Accepted Blocker - we will accept a fix if done before release.
s/Accepted Blocker/accepted freeze exception/
python-blivet-0.61.1-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/python-blivet-0.61.1-1.fc21
Package python-blivet-0.61.1-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing python-blivet-0.61.1-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-10190/python-blivet-0.61.1-1.fc21 then log in and leave karma (feedback).
python-blivet-0.61.2-2.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/python-blivet-0.61.2-2.fc21
This was clearly resolved long ago.