chzdev can't find modprobe
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
sh: 1: /usr/sbin/modprobe: not found
zfcp device type configure failed
Potential solution ? : adding a symlink is a workaround, is this path hardcoded?
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) |
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 |
Changed in linux (Ubuntu): | |
assignee: | Joseph Salisbury (jsalisbury) → nobody |
tags: | added: id-5b2af6e502d313aed0d2b6a8 |
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 |
Changed in ubuntu-z-systems: | |
status: | In Progress → Fix Committed |
Changed in ubuntu-z-systems: | |
status: | Fix Committed → Fix Released |
tags: | added: cscc |
Did this issue just start happening with 18.04?