Bug 1209281
Summary: | [pki] pki-pkcs12-extract.sh fails with /dev/fd is not mounted | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Perry Clegg <pclegg> | |
Component: | ovirt-engine | Assignee: | Yaniv Kaul <ykaul> | |
Status: | CLOSED ERRATA | QA Contact: | Jiri Belka <jbelka> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 3.5.0 | CC: | bazulay, didi, iheim, jko, juwu, lsurette, pstehlik, rbalakri, Rhev-m-bugs, sbonazzo, yeylon, ykaul, ylavi | |
Target Milestone: | ovirt-3.6.0-rc | Keywords: | Patch, ZStream | |
Target Release: | 3.6.0 | Flags: | ylavi:
Triaged+
|
|
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | 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. This includes, for example, 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: | ||||
: | 1213288 (view as bug list) | Environment: | ||
Last Closed: | 2016-03-09 21:02:01 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1213288 |
Description
Perry Clegg
2015-04-07 00:01:17 UTC
this utility should not have been added, bug#1133421. anyway, fixed. ok, ovirt-engine-backend-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch verification based on https://bugzilla.redhat.com/show_bug.cgi?id=1213288#c1 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/RHEA-2016-0376.html |