chzdev can't find modprobe

Bug #1777600 reported by bugproxy
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu on IBM z Systems
Fix Released
High
Dimitri John Ledkov
linux (Ubuntu)
Invalid
High
Unassigned
s390-tools (Ubuntu)
Fix Released
Undecided
Unassigned
Xenial
Fix Released
Undecided
Unassigned
Bionic
Fix Released
Undecided
Unassigned
Cosmic
Fix Released
Undecided
Unassigned

Bug Description

[Impact]

 * chzdev fails to load additional kernel modules at runtime, resulting in failure to activate devices.

[Test Case]

 $ chzdev zfcp --type datarouter=0 dbflevel=5

Should succeed, instead of erroring out / not able to find modprobe.

[Regression Potential]

 * This corrects compiled-in path to /sbin/modprobe, thus making available previously a broken codepath of chzdev.

[Other Info]

 * Original bug report

Description: only when trying to change some attributes chzdev fails because it cant find modprobe under Ubuntu 18.04

              root@m83lp09:~# chzdev zfcp --type datarouter=0 dbflevel=5
              sh: 1: /usr/sbin/modprobe: not found
              zfcp device type configure failed
                  Error: Command failed (exit code 127): /usr/sbin/modprobe -r zfcp

              root@m83lp09:~# whereis modprobe
              modprobe: /sbin/modprobe /etc/modprobe.d /lib/modprobe.d /usr/share/man/man8/modprobe.8.gz

Potential solution ? : adding a symlink is a workaround, is this path hardcoded?

bugproxy (bugproxy)
tags: added: architecture-s39064 bugnameltc-168976 severity-high targetmilestone-inin1804
Changed in ubuntu:
assignee: nobody → Skipper Bug Screeners (skipper-screen-team)
affects: ubuntu → linux (Ubuntu)
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Canonical Kernel Team (canonical-kernel-team)
Changed in linux (Ubuntu):
status: New → Triaged
importance: Undecided → High
Changed in linux (Ubuntu Bionic):
status: New → Triaged
importance: Undecided → High
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue just start happening with 18.04?

Changed in linux (Ubuntu Bionic):
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu):
assignee: Skipper Bug Screeners (skipper-screen-team) → Joseph Salisbury (jsalisbury)
Revision history for this message
Frank Heimes (fheimes) wrote :

Looks to me that it's unfortunately not limited to bionic and affects xenial (and artful), too.

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2018-06-19 09:54 EDT-------
Problem already existed on Ubuntu 16.04:

# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
# chzdev zfcp --type datarouter=0 dbflevel=5
sh: 1: /usr/sbin/modprobe: not found
zfcp device type configure failed
Error: Command failed (exit code 127): /usr/sbin/modprobe -r zfcp

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

Unfortunately it is hardcoded, and there is inconsistent use of modprobe. Let me propose a patch upstream for this issue.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :
no longer affects: linux (Ubuntu Cosmic)
no longer affects: linux (Ubuntu Bionic)
no longer affects: linux (Ubuntu Artful)
no longer affects: linux (Ubuntu Xenial)
Changed in linux (Ubuntu):
status: Triaged → Invalid
Changed in ubuntu-z-systems:
assignee: Canonical Kernel Team (canonical-kernel-team) → Dimitri John Ledkov 🌈 (xnox)
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

I don't believe there any kernel team actions for this bug report.

Changed in linux (Ubuntu):
assignee: Joseph Salisbury (jsalisbury) → nobody
tags: added: id-5b2af6e502d313aed0d2b6a8
Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2018-07-04 09:32 EDT-------
Fix available via upstream..
https://github.com/ibm-s390-tools/s390-tools/commit/d4398aea897475b95e4ab18cde4a32d0d70e6973

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

This bug was fixed in the package s390-tools - 2.5.0-0ubuntu1

---------------
s390-tools (2.5.0-0ubuntu1) cosmic; urgency=medium

  * New upstream release LP: #1776907 LP: #1775627 LP: #1775632
  * Drop udevadm patch, no longer needed
  * Refresh patches
  * Import upstream patches since v2.5.0 LP: #1777600

 -- Dimitri John Ledkov <email address hidden> Tue, 24 Jul 2018 17:00:03 +0100

Changed in s390-tools (Ubuntu Cosmic):
status: New → Fix Released
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: Triaged → In Progress
no longer affects: s390-tools (Ubuntu Artful)
description: updated
Changed in s390-tools (Ubuntu Xenial):
status: New → In Progress
Changed in s390-tools (Ubuntu Bionic):
status: New → In Progress
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello bugproxy, or anyone else affected,

Accepted s390-tools into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/s390-tools/1.34.0-0ubuntu8.8 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 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 s390-tools (Ubuntu Xenial):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-xenial
Changed in s390-tools (Ubuntu Bionic):
status: In Progress → Fix Committed
tags: added: verification-needed-bionic
Revision history for this message
Brian Murray (brian-murray) wrote :

Hello bugproxy, or anyone else affected,

Accepted s390-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/s390-tools/2.3.0-0ubuntu3.1 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 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.

Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: In Progress → Fix Committed
Revision history for this message
Frank Heimes (fheimes) wrote :

Successfully verified on xenial - adjusting tags accordingly.

tags: added: verification-done-xenial
removed: verification-needed-xenial
Revision history for this message
Frank Heimes (fheimes) wrote :

Successfully verified on bionic - adjusting tags accordingly.

tags: added: verification-done verification-done-bionic
removed: verification-needed verification-needed-bionic
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for s390-tools has completed successfully and the package has now been 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 s390-tools - 2.3.0-0ubuntu3.1

---------------
s390-tools (2.3.0-0ubuntu3.1) bionic; urgency=medium

  * zdev: Adjust zdev modprobe path to be compatible with split-usr
    systems. (LP: #1777600)
  * zdev: Trigger generic_ccw devices on any kernel module loads. (LP:
    #1794308)

 -- Dimitri John Ledkov <email address hidden> Mon, 22 Oct 2018 12:37:39 +0100

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

This bug was fixed in the package s390-tools - 1.34.0-0ubuntu8.8

---------------
s390-tools (1.34.0-0ubuntu8.8) xenial; urgency=medium

  * zdev: Adjust zdev modprobe path to be compatible with split-usr
    systems. (LP: #1777600)
  * zdev: Trigger generic_ccw devices on any kernel module loads. (LP:
    #1794308)

 -- Dimitri John Ledkov <email address hidden> Mon, 22 Oct 2018 12:51:12 +0100

Changed in s390-tools (Ubuntu Xenial):
status: Fix Committed → Fix Released
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: Fix Committed → Fix Released
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2018-10-31 04:46 EDT-------
IBM Bugzilla status -> closed, Fix Released by all Releases in service.

Brad Figg (brad-figg)
tags: added: cscc
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.