Public bug reported:

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?

** Affects: linux (Ubuntu)
     Importance: Undecided
     Assignee: Skipper Bug Screeners (skipper-screen-team)
         Status: New


** Tags: architecture-s39064 bugnameltc-168976 severity-high 
targetmilestone-inin1804

** Tags added: architecture-s39064 bugnameltc-168976 severity-high
targetmilestone-inin1804

** Changed in: ubuntu
     Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1777600

Title:
  chzdev can't find modprobe

Status in linux package in Ubuntu:
  New

Bug description:
  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?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777600/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to