Bug 1304911 - OpenShift client download weird directory structure
OpenShift client download weird directory structure
Product: OpenShift Container Platform
Classification: Red Hat
Component: Command Line Interface (Show other bugs)
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Troy Dawson
Wei Sun
Depends On:
  Show dependency treegraph
Reported: 2016-02-04 19:15 EST by Takayoshi Kimura
Modified: 2017-02-02 02:20 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-02-01 16:50:35 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Takayoshi Kimura 2016-02-04 19:15:19 EST
Description of problem:

OpenShift client download has weird directory structure.


$ tar tf oc- 

$ tar tf oc- 

$ unzip -l oc- 
Archive:  oc-
  Length      Date    Time    Name
---------  ---------- -----   ----
 38504448  01-26-2016 06:34   mnt/redhat/staging-cds/ose-clients-
---------                     -------
 38504448                     1 file

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


How reproducible:


Steps to Reproduce:
1. Download OpenShift client
2. Open the downloaded archive

Actual results:

See description part.

Expected results:

Previously it was something like "oc-31.0.4/oc" which was good. The current dir structure includes whole our internal build dir.

Additional info:
Comment 1 Juan Vallejo 2017-02-01 11:43:13 EST
@jwforres Should this be reassigned to someone in the release team?
Comment 2 Jessica Forrester 2017-02-01 16:38:40 EST
@tdawson can you work with RCM on that to see why the packaging structure changed?
Comment 3 Troy Dawson 2017-02-01 16:50:35 EST
This was a problem with early 3.1 client downloads and has already been fixed in later versions.

If you are using the OpenShift 3.1 client we recommend that you use the latest version, currently is, that has already been fixed.


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