lsvpd: Missing package dependency
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lsvpd (Ubuntu) |
Fix Released
|
Undecided
|
Steve Langasek | ||
Trusty |
Won't Fix
|
Undecided
|
Steve Langasek |
Bug Description
---Problem Description---
lsvpd uses iprconfig to get enclosure and disk related VPD information.
Hence we need iprconfig (iprutils package) during runtime.
Hence add iprutils as package dependency for lsvpd.
Machine Type = All Power System
---Steps to Reproduce---
- Install lsvpd and run vpdupdate
---uname output---
Ubuntu 16.04
Userspace tool common name: lsvpd
Patch :
-------
diff -Naurp debian/control.org debian/control
--- debian/control.org 2016-01-21 05:56:46.030490432 -0600
+++ debian/control 2016-01-21 05:57:01.094491365 -0600
@@ -9,7 +9,7 @@ Homepage: http://
Package: lsvpd
Architecture: powerpc ppc64 ppc64el
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, iprutils
Description: Utility to List Device Vital Product Data (VPD)
This utility lists device Vital Product Data (VPD), which includes the
following information and more: vendor, version, revision level, serial
Note that we have this issue in 14.04.04 as well. Please apply this patch to both 16.04 and 14.04.04.
-Vasant
tags: | added: architecture-ppc64le bugnameltc-135877 severity-high targetmilestone-inin1604 |
Changed in ubuntu: | |
assignee: | nobody → Taco Screen team (taco-screen-team) |
affects: | ubuntu → lsvpd (Ubuntu) |
Changed in lsvpd (Ubuntu): | |
assignee: | Taco Screen team (taco-screen-team) → Steve Langasek (vorlon) |
status: | New → In Progress |
Changed in lsvpd (Ubuntu Trusty): | |
assignee: | nobody → Steve Langasek (vorlon) |
status: | New → In Progress |
Changed in lsvpd (Ubuntu): | |
status: | Fix Released → Incomplete |
Changed in lsvpd (Ubuntu): | |
status: | Triaged → Fix Committed |
So I uploaded lsvpd to the xenial archive with this change; but then after testing, I see that it merely trades one set of errors for another.
- iprconfig is not shipped as /usr/sbin/iprconfig in Ubuntu, but as /sbin/iprconfig; so adding the dependency does not remove the error.
- adjusting paths so that vpdupdate can find iprconfig results in a new stream of other error messages when invoking vpdupdate:
iprconfig[91936]: Could not open /dev/sg28. No such file or directory
iprconfig[91936]: Could not open /dev/sg28. No such file or directory
iprconfig[91936]: Could not open /dev/sg28. No such file or directory
iprconfig[91936]: Could not open /dev/sg28. No such file or directory
iprconfig[91936]: Could not open /dev/sg28. No such file or directory
iprconfig[91936]: Could not open /dev/sg25. No such file or directory
iprconfig[91936]: Could not open /dev/sg25. No such file or directory
iprconfig[91936]: Could not open /dev/sg25. No such file or directory
iprconfig[91936]: Could not open /dev/sg25. No such file or directory
iprconfig[91936]: Could not open /dev/sg25. No such file or directory
iprconfig[91936]: Could not open /dev/sg25. No such file or directory
iprconfig[91936]: Could not open /dev/sg30. No such file or directory
iprconfig[91936]: Could not open /dev/sg30. No such file or directory
iprconfig[91936]: Could not open /dev/sg30. No such file or directory
iprconfig[91936]: Could not open /dev/sg30. No such file or directory
iprconfig[91936]: Could not open /dev/sg30. No such file or directory
iprconfig[91936]: Could not open /dev/sg30. No such file or directory
(etc)
- after running vpdupdate with fixed paths, the output of 'lsvpd' is almost precisely identical from before. Only two lines of diference in the output, and it appears that the new output contains less information rather than more?
@@ -422,7 +422,7 @@ WZS008E- P1-C14- B3-T0-L0 WZS008E- P1-C14 WZS008E- P1-C15- B3-T0-L0 WZS008E- P1-C15
*XB 3
*XT 0
*XL 0
-*YL U78CB.001.
+*YL U78CB.001.
*FC
*DS -SCSI Enclosure Services Device
*AX sg27
@@ -970,7 +970,7 @@
*XB 3
*XT 0
*XL 0
-*YL U78CB.001.
+*YL U78CB.001.
*FC
*DS -SCSI Disk Drive
*AX sg39
Perhaps because this particular system doesn't support ipr scsi? Or perhaps, it's because if iprutils aren't installed, one can assume that ipr scsi isn't configured and therefore iprconfig is not going to provide any additional information...
So I'm not sure that the dependency on iprutils is actually required. But I am reasonably certain that vpdupdate should be fixed to suppress error output from iprconfig instead of displaying it.
Please consider whether making this change to lsvpd upstream is a better fix.
For reference, here is the output of 'iprconfig -c show-config 2>/dev/null' on the system where I tested: ------- ------- ---- ------- ------- ------- ---- -----------------
0001:08: 00.0/0: PCI-E SCSI Adapter Not Operational 00.0/0: 2:0:0 Unavailable Device Unknown 00.0/0: 2:1:0 Unavailable Device Unkn...
Name PCI/SCSI Location Description Status
------ -------
sda 0001:08:
sdb 0001:08: