[Bug 1803958] Please test proposed package

Łukasz Zemczak 1803958 at bugs.launchpad.net
Thu May 23 08:44:20 UTC 2019


Hello bugproxy, or anyone else affected,

Accepted s390-tools into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/s390-tools/2.6.0-0ubuntu7.3 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. 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.

-- 
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/1803958

Title:
  [UBUNTU] zkey: Fails to run commands generated by 'zkey cryptsetup'

Status in Ubuntu on IBM z Systems:
  In Progress
Status in s390-tools package in Ubuntu:
  Fix Released
Status in s390-tools source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * zkey utility attempts to execute cryptsetup binary and fails to
  find it, due to setting invalid PATH variable (which is missing
  /sbin). Stop resetting the PATH, and use the correct system default
  PATH which leads to correct execution of cryptsetup binary.

  
  [Test Case]

   * enroll system with crypto adapters / get ready to use zkey
   * generate appropriate zkey for an encryption device
   * Use `$ zkey cryptsetup --run` to perform cryptsetup commands via zkey

  [Regression Potential]

   * Currently only '--run' argument is broken, without '--run' the
  commands are printed that one can simply copy&paste and execute
  correctly under sudo. The effects of broken path, and using system
  path, have been discussed in depth at
  https://github.com/ibm-s390-tools/s390-tools/commit/9100327092c470c2e5b5819087c8094822a1c751
  and will result in correctly attempting to execute cryptsetup binary.
  (it may later fail for other reasons, but that's beyond the scope
  here).

  [Other Info]
   
   * Original bug report.

  Description:  zkey: Fails to run commands generated by 'zkey
  cryptsetup'

  Symptom:      Fails to run commands generated by 'zkey cryptsetup'.

  Problem:  When using 'zkey cryptsetup' with --run option the execution
  of the generated commands may fail, when  the executable to be run is
  located in '/sbin'.

  Solution:     Include /sbin into PATH when executing commands.

  Reproduction: Use 'zkey cryptsetup' with option --run on a distribution
                where 'cryptsetup' is located in '/sbin'.

  Upstream commit:
  https://github.com/ibm-s390-tools/s390-tools/commit/9100327092c470c2e5b5819087c8094822a1c751

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



More information about the foundations-bugs mailing list