Bug 1525733 - oci-umount: umounthook <error>: Failed to read directory /usr/share/oci-umount/oci-umount.d: No such file or directory
Summary: oci-umount: umounthook <error>: Failed to read directory /usr/share/oci-umoun...
Keywords:
Status: CLOSED DUPLICATE of bug 1525715
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Containers
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Jhon Honce
QA Contact: DeShuai Ma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-13 23:51 UTC by Dan Yocum
Modified: 2017-12-14 18:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-14 18:35:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Dan Yocum 2017-12-13 23:51:18 UTC 
Description of problem:

oci-umount[28510]: umounthook <error>: 3ed4e6548da8: Failed to read directory /usr/share/oci-umount/oci-umount.d: No such file or directory

Appears on OCP installed in GCP.


Version-Release number of selected component (if applicable):

[root@ded-int-gcp-node-infra-1myld yum.repos.d]# yum list atomic-openshift oci-umount docker
Loaded plugins: product-id, search-disabled-repos, subscription-manager
Installed Packages
atomic-openshift.x86_64                                3.7.9-1.git.0.7c71a2d.el7                                 @rhui-rhel-server-7-ose-3.7
docker.x86_64                                          2:1.12.6-68.gitec8512b.el7                                @rhel-server-extras        
oci-umount.x86_64                                      2:2.3.0-1.git51e7c50.el7                                  @rhel-server-extras  


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Jhon Honce 2017-12-14 18:35:28 UTC 
As this is the same version of oci-umount in both bugs

*** This bug has been marked as a duplicate of bug 1525715 ***
Note You need to log in before you can comment on or make changes to this bug.