Bug 1302254 - [devexp_public_430]Can't copy directory which only contains multiple empty directories to destination dir
[devexp_public_430]Can't copy directory which only contains multiple empty di...
Status: CLOSED WONTFIX
Product: OpenShift Origin
Classification: Red Hat
Component: Build (Show other bugs)
3.x
Unspecified Unspecified
low Severity low
: ---
: ---
Assigned To: Ben Parees
Wenjing Zheng
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-01-27 05:12 EST by XiuJuan Wang
Modified: 2016-01-27 13:24 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-01-27 13:24:37 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description XiuJuan Wang 2016-01-27 05:12:42 EST
Description of problem:
When treat a directory which only contains empty directories as sourcepath, no directory can be copied to destination dir

Version-Release number of selected component (if applicable):
devenv-rhel7_3250
oc v1.1.1-182-ga57296f
kubernetes v1.1.0-origin-1107-g4c8e6f4

How reproducible:
always

Steps to Reproduce:
1.Find a directory only contains empty directories in source image.
2.Create an app with source image.
$oc new-build openshift/ruby:latest   https://github.com/openshift/ruby-hello-world --source-image=openshift/jenkins:latest --source-image-path=/var/lib/yum/repos/x86_64/:xiuwangs2i
3.After build complete, check result image.

Actual results:
3.Nothing copied to destination dir from source path

Expected results:
Coould copy source files/directory to destination dir

Additional info:
Comment 1 Ben Parees 2016-01-27 13:24:37 EST
I can't think of a use case where someone would need/want to copy an entirely empty directory tree out of an image for a build, so i'm going to mark this won't fix as it's not worth the time/effort to address.

Note You need to log in before you can comment on or make changes to this bug.