Bug 1213288
Summary: | [pki] pki-pkcs12-extract.sh fails with /dev/fd is not mounted | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
Component: | ovirt-engine-setup | Assignee: | Yedidyah Bar David <didi> |
Status: | CLOSED ERRATA | QA Contact: | Jiri Belka <jbelka> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.5.0 | CC: | alonbl, bazulay, didi, ecohen, eedri, juwu, lsurette, pstehlik, rbalakri, Rhev-m-bugs, sbonazzo, yeylon, ylavi |
Target Milestone: | --- | Keywords: | Patch, ZStream |
Target Release: | 3.5.3 | Flags: | ylavi:
Triaged+
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | integration | ||
Fixed In Version: | org.ovirt.engine-root-3.5.3-2 | Doc Type: | Bug Fix |
Doc Text: |
Previously, the pki-pkcs12-extract.sh script relied on the existence of the /dev/fd directory. In Linux, this is normally symbolically linked to the /proc/self/fd directory, allowing processes to access its STDIN, STDOUT, etc as named files. If the /dev/fd directory did not exist, the script failed. An example scenario is trying to run engine-setup during installation from a kickstart file. With this update, the script was updated to use the /proc/self/fd directly. Now the script only requires that the /proc direcory is mounted, and does not fail if the /dev/fd directory does not exist.
|
Story Points: | --- |
Clone Of: | 1209281 | Environment: | |
Last Closed: | 2015-06-15 13:27:52 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1209281 | ||
Bug Blocks: |
Comment 1
Yedidyah Bar David
2015-04-20 13:13:24 UTC
https://gerrit.ovirt.org/40089 is needed for the (unlikely) case that there is a file named '/-'. ok, rhevm-backend-3.5.3-0.2.el6ev.noarch followed steps described in #1. added_manually_to_errata Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1095.html |