[Bug 1777600] Re: chzdev can't find modprobe

[Dimitri John Ledkov]

** Description changed:

- Description:  only when trying to change some attributes chzdev fails because it cant find modprobe under Ubuntu 18.04
-               
-               root at 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 at 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?
+ [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 at 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 at 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?

** Changed in: s390-tools (Ubuntu Xenial)
       Status: New => In Progress

** Changed in: s390-tools (Ubuntu Bionic)
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to s390-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1777600

Title:
  chzdev can't find modprobe

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in s390-tools package in Ubuntu:
  Fix Released
Status in s390-tools source package in Xenial:
  In Progress
Status in s390-tools source package in Bionic:
  In Progress
Status in s390-tools source package in Cosmic:
  Fix Released

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 at 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 at 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?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1777600/+subscriptions