Bug 861047 - [US2105][fork]Failed to restore apps using snapshot tarball
Summary: [US2105][fork]Failed to restore apps using snapshot tarball
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: oc
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Mrunal Patel
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-27 11:48 UTC by jizhao
Modified: 2015-05-15 02:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-06 18:49:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description jizhao 2012-09-27 11:48:44 UTC
Description of problem:
Always get "Archive at app3.tar.gz does not contain the target application: ./*/app3" while restoring apps. This may be caused by the directory structure changes.

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

How reproducible:
Always

Steps to Reproduce:
1.Create an app
2.Save snapshot of it
$ rhc app snapshot save -a <appname> -d
3.Restore the app
$ rhc app snapshot restore -a <appname> -f app3.tar.gz -d
  
Actual results:
<----------------output---------------->
Archive at app3.tar.gz does not contain the target application: ./*/app3
If you created this archive rather than exported with rhc-snapshot, be sure
the directory structure inside the archive starts with ./<app_uuid>/
i.e.: tar -czvf <app_name>.tar.gz ./<app_uuid>/
<-------------------------------------->


Expected results:
The app should be restored successfully.

Additional info:

Comment 1 jizhao 2012-09-27 12:04:31 UTC
After embedding mysql-5.1 to the app, restore will succeed.

Comment 3 Jianwei Hou 2012-09-28 08:45:57 UTC
Tested on fork_ami_US2105_178
Seems the above fix has not come into latest ami, so leave this bug for next fork_ami

Comment 4 Jianwei Hou 2012-09-29 07:14:22 UTC
Tested on fork_ami_us2105_189, and still reproduced this problem.

The fixing code has not merged in, so I replaced current code with fix in comment 2 and it works for me.

Assign it back now since the fix has not came in for two ami builds.

Comment 5 Mrunal Patel 2012-10-01 14:52:54 UTC
Fix will be available in next AMI.

Comment 6 Chandrika Gole 2012-10-01 23:24:57 UTC
Test this on devenv2259 and it works

Comment 7 Chandrika Gole 2012-10-03 00:08:56 UTC
verified this on AMI: fork_ami_US2105_203 (ami-3943fe50)


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