Red Hat Bugzilla – Bug 1255966
rhc snapshot save timeout flag doesn't work
Last modified: 2016-03-18 14:25:37 EDT
Description of problem:
rhc snapshot save tool exceeds timeout even if --timeout flag is specified
Version-Release number of selected component (if applicable):
Making snapshot for this jenkins application. Other details could be provided
Make a snapshot of jenkins app https://openshift.redhat.com/app/console/application/5458ba5f4382ec26f300031f-jenkins with rhc tool
Steps to Reproduce:
1.Execute the following script:
rhc snapshot-save opendingo/jenkins --timeout 20800
2. Notice in actual results difference in 1 hour(default timeout)
Sat Aug 22 14:40:07 MSK 2015
Pulling down a snapshot of application 'jenkins' to jenkins.tar.gz ...
Error in trying to save snapshot. You can try to save manually by running:
ssh firstname.lastname@example.org 'snapshot' > jenkins.tar.gz
Sat Aug 22 15:40:15 MSK 2015
green letters: done
Can provide any additional info. Also the alternative command recommended by rhc tool isn't working
Thanks for the report. Is this on a Windows or Max/Linux/Unix system? Additionally, how much additional storage does your application use? Could you provide the output of `quota -s` while ssh'd into the application?
If on a linux/unix/Mac system, rhc simply calls the ssh command given in the error output of the command. The timeout could be in the ssh implementation on your client system, or perhaps in the openshift.com server.
If on a Windows system, we use the 'net/ssh' rubygem. We don't specifically specify any timeout, so it is likely a timeout on the openshift server if this is happening on a windows system.
(In reply to Timothy Williams from comment #1)
> Thanks for the report. Is this on a Windows or Max/Linux/Unix system?
> Additionally, how much additional storage does your application use? Could
> you provide the output of `quota -s` while ssh'd into the application?
> If on a linux/unix/Mac system, rhc simply calls the ssh command given in the
> error output of the command. The timeout could be in the ssh implementation
> on your client system, or perhaps in the openshift.com server.
> If on a Windows system, we use the 'net/ssh' rubygem. We don't specifically
> specify any timeout, so it is likely a timeout on the openshift server if
> this is happening on a windows system.
I tried to make snapshot on both Linux and Windows systems.
In case of Windows I've got an error:
Pulling down a snapshot of application 'dustri' to dustri.tar.gz ... Could not parse PKey: no start line
You can look at this bug here https://bugzilla.redhat.com/show_bug.cgi?id=1197301
Also I tried other "recipes" with net-ssh. Nothing helps.
Regarding linux system there is 11G disk space for cartridge on Openshift Online server. And I wonder how you don't know where is a timeout on client or server! Please check this bug.
Should be resolved with https://github.com/openshift/rhc/pull/711
Commit pushed to master at https://github.com/openshift/rhc
Honor global timeout during snapshot save
When saving a snapshot, honor the timeout passed as a global argument, or defined in configuration.
Closing this bug - the pull request should help but likely doesn't resolve the whole issue. The problem and proposed solution are documented in another bug, which this has been marked a duplicate of.
*** This bug has been marked as a duplicate of bug 1080400 ***