Bug 1751290

Summary: regression: lsblk not showing PKNAME in f31+
Product: [Fedora] Fedora Reporter: Dusty Mabe <dustymabe>
Component: util-linuxAssignee: Karel Zak <kzak>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: bgilbert, jonathan, kzak
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: util-linux-2.34-3.fc31 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-21 00:01:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dusty Mabe 2019-09-11 15:59:18 UTC
Description of problem:

We are using lsblk --output PKNAME and that appears to have stopped working properly in fedora 31+. Here is the output:

on F30 it works and properly shows `/dev/vda`
```
[vagrant@vanilla-f30 ~]$ lsblk --output PTUUID,PKNAME --pairs --paths --nodeps /dev/vda1
PTUUID="3175bbb3" PKNAME="/dev/vda"
[vagrant@vanilla-f30 ~]$ rpm -q kernel-core util-linux
kernel-core-5.0.9-301.fc30.x86_64
kernel-core-5.2.11-200.fc30.x86_64
util-linux-2.33.2-2.fc30.x86_64
```

on F31 PKNAME is blank:

[vagrant@vanilla-f31 ~]$ lsblk --output PTUUID,PKNAME --pairs --paths --nodeps /dev/vda1
PTUUID="539f29b0" PKNAME=""
[vagrant@vanilla-f31 ~]$ rpm -q kernel-core util-linux
kernel-core-5.3.0-0.rc6.git0.1.fc31.x86_64
util-linux-2.34-2.fc31.x86_64
```

on rawhide (F32) PKNAME is blank:

```
[vagrant@vanilla-rawhide ~]$ lsblk --output PTUUID,PKNAME --pairs --paths --nodeps /dev/vda1
PTUUID="f6214eaa" PKNAME=""                                                                 
[vagrant@vanilla-rawhide ~]$ rpm -q kernel-core util-linux                                  
kernel-core-5.3.0-0.rc8.git0.1.fc32.x86_64                                                  
util-linux-2.34-4.fc32.x86_64
```



Version-Release number of selected component (if applicable):
util-linux-2.34-2.fc31.x86_64
util-linux-2.34-4.fc32.x86_64


How reproducible:
Always

Steps to Reproduce:
1. boot machine (can use a cloud image if you like)
2. run `lsblk --output PTUUID,PKNAME --pairs --paths --nodeps /dev/vda1` 


Actual results:

PKNAME result empty

Expected results:

PKNAME result populated

Comment 1 Karel Zak 2019-09-12 08:53:59 UTC
This is already fixed in upstream tree, commit: http://github.com/karelzak/util-linux/commit/e3bb9bfb76c17b1d05814436ced62c05c4011f48

I'll backport it to f31+

Comment 2 Fedora Update System 2019-09-12 10:08:01 UTC
FEDORA-2019-05938d7bcb has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-05938d7bcb

Comment 3 Fedora Update System 2019-09-12 14:45:21 UTC
util-linux-2.34-3.fc31 has been pushed to the Fedora 31 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-2019-05938d7bcb

Comment 4 Dusty Mabe 2019-09-12 15:35:16 UTC
thanks Karel!

Comment 5 Dusty Mabe 2019-09-12 16:46:07 UTC
After upgrading all of my packages on the system that are provided by the util-linux rpm...

```
Upgrading:                                                                                          
 libblkid          x86_64   2.34-3.fc31
 libfdisk          x86_64   2.34-3.fc31
 libmount          x86_64   2.34-3.fc31
 libsmartcols      x86_64   2.34-3.fc31
 libuuid           x86_64   2.34-3.fc31
 util-linux        x86_64   2.34-3.fc31
```

It all seems to work!

```
[vagrant@vanilla-f31 tmp]$ lsblk --output PTUUID,PKNAME --pairs --paths --nodeps /dev/vda1
PTUUID="7ba0e2fb" PKNAME="/dev/vda"
```

Comment 6 Fedora Update System 2019-09-21 00:01:42 UTC
util-linux-2.34-3.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.