| Summary: | An warning message should be thrown out instead of error message when restore a app with postgresql-8.4 (and postgresl-9.2) cartridge | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Johnny Liu <jialiu> |
| Component: | ImageStreams | Assignee: | Luke Meyer <lmeyer> |
| Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.0.0 | CC: | bleanhar, bparees, dmcphers, jdetiber, lmeyer, nwei, xtian |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openshift-origin-cartridge-postgresql-1.17.3.2 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1003531 | Environment: | |
| Last Closed: | 2014-01-13 14:54:54 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: | |
| Bug Depends On: | 1003531 | ||
| Bug Blocks: | |||
|
Description
Johnny Liu
2013-11-27 11:04:45 UTC
https://github.com/openshift/enterprise-server/pull/162 Author: Ben Parees <bparees> AuthorDate: Tue Nov 19 11:38:50 2013 -0500 Commit: Luke Meyer <lmeyer> CommitDate: Thu Dec 5 17:49:08 2013 -0500 Bug 1003531: An warning message should be thrown out instead of error message when restore a app with postgresql-8.4 (and postgresl-9.2) cartridge bug 1035237 https://bugzilla.redhat.com/show_bug.cgi?id=1035237 b6b0d1aadc1b5685b1d32976b31d0c674148929c #cherrypick openshift-origin-cartridge-postgresql-1.17.3.2 actually built now and should be in next 2.0 puddle. On brew at http://download.devel.redhat.com/brewroot/packages/openshift-origin-cartridge-postgresql/1.17.3.2/1.el6op/noarch/openshift-origin-cartridge-postgresql-1.17.3.2-1.el6op.noarch.rpm OpenShift Enterprise puddle: 2.0/2013-12-09.3 [root@node1 ~]# rpm -qa|grep openshift-origin-cartridge-postgresql openshift-origin-cartridge-postgresql-1.17.3-2.el6op.noarch 1. Create a jbosseap-6.0 app with db #rhc app create js6 jbosseap postgresql-9.2 -s 2. Take snapshot for this app #rhc snapshot save $app 3. Write some data to ../data dir in the app gear and add some data to postgresql 4. snapshot restore this app with that saved $app.tar.gz #rhc snapshot restore $app -f $app.tar.gz Restoring from snapshot js6.tar.gz... Warning: Permanently added 'js6-nweidomain.ose-1209.com.cn,10.4.59.210' (RSA) to the list of known hosts. Removing old git repo: ~/git/js6.git/ Removing old data dir: ~/app-root/data/* Restoring ~/git/js6.git and ~/app-root/data Restoring snapshot for postgresql-9.2 gear Removing old data dir: ~/app-root/data/* Restoring ~/app-root/data ERROR: database "js6" already exists Activation status: success RESULT: Success Error message exists yet. And the code in "cartridges/openshift-origin-cartridge-postgresql/bin/control" file is old. Please try to verify again; openshift-origin-cartridge-postgresql-1.17.3-2.el6op.noarch is not as new as openshift-origin-cartridge-postgresql-1.17.3.2, and the latter is available now. Sorry for putting this ON_QA previously before the puddle was out. OpenShift Enterprise 2.0.1 puddle: [2.0.z/2013-12-16.2] [root@node1 ~]# rpm -qa|grep openshift-origin-cartridge-postgresql openshift-origin-cartridge-postgresql-1.17.3.3-1.el6op.noarch 1. Create a ruby app with db #rhc app create ruby19 ruby-1.9 postgresql-9.2 2. Take snapshot for this app #rhc snapshot save $app 3. Write some data to ../data dir in the app gear and add some data to postgresql 4. snapshot restore this app with that saved $app.tar.gz #rhc snapshot restore $app -f $app.tar.gz Restoring from snapshot ruby19.tar.gz... Warning: Permanently added 'ruby19-nweidomain.ose20-1216-com.cn,10.4.59.171' (RSA) to the list of known hosts. Removing old git repo: ~/git/ruby19.git/ Removing old data dir: ~/app-root/data/* Restoring ~/git/ruby19.git and ~/app-root/data Activation status: success RESULT: Success Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0020.html |