Bug 1017776
| Summary: | Deploying the Cartridge Development Kit is not possible | ||
|---|---|---|---|
| Product: | OKD | Reporter: | Sebastian Lütge <sebastian.luetge> |
| Component: | Image | Assignee: | Paul Morie <pmorie> |
| Status: | CLOSED WONTFIX | QA Contact: | libra bugs <libra-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.x | CC: | dmcphers, ffranz, pch, siegfried.chaisson, xtian |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-05-31 18:22:11 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Sebastian Lütge
2013-10-10 13:35:10 UTC
I cannot reproduce this issue in a devenv. Tested on devenv_4003. I can create the app successfully: [openshift@dhcp-10-143 tmp]$ rhc create-app cdk http://cdk-claytondev.rhcloud.com/manifest/2ccd7a3a7762e4ebb873c0d64a247b180e0600b8 The cartridge 'http://cdk-claytondev.rhcloud.com/manifest/2ccd7a3a7762e4ebb873c0d64a247b180e0600b8' will be downloaded and installed Application Options ------------------- Domain: qiuzhang Cartridges: http://cdk-claytondev.rhcloud.com/manifest/2ccd7a3a7762e4ebb873c0d64a247b180e0600b8 Gear Size: default Scaling: no Creating application 'cdk' ... done The CDK is configured with password ZTNiMGM0NDI5OGZjMWMxNDlhZmJmNGM4OTk2ZmI5MjQyN2FlNDFlNDY0OWI5MzRjYTQ5NT for builds (use 'admin' as the user) Waiting for your DNS name to be available ... done Cloning into 'cdk'... Warning: Permanently added 'cdk-qiuzhang.dev.rhcloud.com' (RSA) to the list of known hosts. Your application 'cdk' is now available. URL: http://cdk-qiuzhang.dev.rhcloud.com/ SSH to: 527c91a87df7577913000110.rhcloud.com Git remote: ssh://527c91a87df7577913000110.rhcloud.com/~/git/cdk.git/ Cloned to: /home/openshift/tmp/cdk Run 'rhc show-app cdk' for more details about your app. Mark the bug as verified. Just repoduced it on the demo VirtualMachine : $ rhc create-app cdk http://cdk-claytondev.rhcloud.com/manifest/2ccd7a3a7762e4ebb873c0d64a247b180e0600b8 The cartridge 'http://cdk-claytondev.rhcloud.com/manifest/2ccd7a3a7762e4ebb873c0d64a247b180e0600b8' will be downloaded and installed Password: ******** Application Options ------------------- Domain: demo Cartridges: http://cdk-claytondev.rhcloud.com/manifest/2ccd7a3a7762e4ebb873c0d64a247b180e0600b8 Gear Size: default Scaling: no Creating application 'cdk' ... Unexpected error: CLIENT_ERROR: Download of 'http://cdk-claytondev.rhcloud.com/archive/2ccd7a3a7762e4ebb873c0d64a247b180e0600b8/cdk.zip' exceeded Content-Length of 9728. Download aborted. My environment : Running the last openshift origin virtual machine download on virtualBox. I found that in cartridge_repository.rb : if content_length && content_length < total raise Net::HTTPBadResponse.new("CLIENT_ERROR: Download of '#{uri}' exceeded Content-Length of #{content_length}. Download aborted.") end Is there a way to configure the content_lenght to match some private content lengths ? The code above looks like controlling something with tha content_length in node repo, but i did'nt found yet the way to set this value in the good way... Thanks for help ! This is related to Origin, not Online and is still being reported. Reopening to investigate against a local installation of Origin. Reported on: http://stackoverflow.com/questions/22913507/unexpected-error-client-error-on-openshift https://www.openshift.com/forums/openshift/cant-install-cartridge-in-openshift-origin We apologize, however, we do not plan to address this report at this time. The majority of our active development is for the v3 version of OpenShift. If you would like for Red Hat to reconsider this decision, please reach out to your support representative. We are very sorry for any inconvenience this may cause. |