Bug 1080771 - Failed to restore snapshot after force-stop app
Summary: Failed to restore snapshot after force-stop app
Keywords:
Status: CLOSED DUPLICATE of bug 1081020
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Image
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Ben Parees
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-26 06:15 UTC by Lei Zhang
Modified: 2015-05-15 00:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-26 15:36:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lei Zhang 2014-03-26 06:15:16 UTC
Description of problem:
Given one app created(e.g., myphp53), do save snapshot, force stop app, restore snapshot, failed to restore snapshot.

[lijun@ray Work]$ rhc app force-stop myphp53
RESULT:
myphp53 force stopped
[lijun@ray Work]$ rhc snapshot restore -a  myphp53 -f myphp53.tar.gz 
Restoring from snapshot myphp53.tar.gz...
Removing old git repo: ~/git/myphp53.git/
Removing old data dir: ~/app-root/data/*
Restoring ~/git/myphp53.git and ~/app-root/data
Error in trying to restore snapshot. You can try to restore manually by running:
cat 'myphp53.tar.gz' | ssh 533247253ffb2c4b120003f0.rhcloud.com 'restore INCLUDE_GIT'

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

How reproducible:
always

Steps to Reproduce:
1.Create one app and do save snapshot
#rhc app create myphp53 php-5.3
#rhc snapshot save myphp53
2.force stop app and do restore snapshot
#rhc app force-stop myphp53
#rhc snapshot restore -a myphp53 -f myphp53.tar.gz 
3.

Actual results:
Failed to restore snapshot after force stop app

Expected results:
Should restore snapshot successfully after force stop app

Additional info:

Comment 1 Michal Fojtik 2014-03-26 15:36:09 UTC

*** This bug has been marked as a duplicate of bug 1081020 ***


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