mysqli - openshift scaling up - "Unable to restore mysql-5.5 because it appears there is no snapshot for that type" -


i have openshift app mysql 5.5, php 5.4 , phpmyadmin 4.0 convert scalable.

so according instructions shekhar gulati on - https://www.openshift.com/forums/openshift/recreate-an-existing-app-so-it-is-scaleable#comment-30153 took snapshot of old app.
created new scalable app with

$ rhc app create -s apiprod php-5.4 mysql-5.5 phpmyadmin-4 

since old app had phpmyadmin - , cannot add phpmyadmin scalable app. created new app

$ rhc app create -s apiprod php-5.4 mysql-5.5  

untarred old snapshot, deleted phpmyadmin subdirectory old snapshot, tarred again, , tried restoring new scalable app - got following error -

dev@ubuntusrv2:~$ rhc snapshot restore -a apiprod -f oldapp.tar.gz restoring snapshot oldapp.tar.gz... removing old git repo: ~/git/apiprod.git/ removing old data dir: ~/app-root/data/* restoring ~/git/apiprod.git , ~/app-root/data unable restore mysql-5.5 because appears there no snapshot type activation status: success  result: success 

now, problem seems similar 1 experienced molokov on https://www.openshift.com/forums/openshift/recreate-an-existing-app-so-it-is-scaleable#comment-33240

following steps outlined molokov, managed restore old app new scalable app without error.

but mysqli::mysqli() seems having problem connecting database -
command line access works right -

[apiprod-domain.rhcloud.com behat]\> echo $openshift_mysql_db_host 53182ea2500446463d00002e-domain.rhcloud.com [apiprod-domain.rhcloud.com behat]\> mysql -h 53182ea2500446463d00002e-domain.rhcloud.com -u test -p (can log in right) 

ssh-ing oldapp shows ip address instead of hostname on new scalable app

[apiv1-domain.rhcloud.com 53101d1e5004465baa000282]\> echo $openshift_mysql_db_host 127.3.76.130 

i impressed ease things can setup openshift online , use production.

this should common use case - happy know how should proceed

creating snapshot of single gear application, , restoring scaled application not supported, because of way snapshots created, , fact in scaled application db's etc go on own gears. if restore snapshot of non-scaled application non-scaled application, not know how database onto database gear. believe correct solution scenario create workflow on openshift facilitate push button solution migrating non-scaled scaled solution. please make sure vote on feature here (https://www.openshift.com/content/conversion-of-non-scalable-app-to-scalable-one)

also, here knowledge base article posted it:https://www.openshift.com/kb/kb-e1092-user-is-not-able-to-restore-snapshot-of-non-scaled-application-to-scaled-application-or


Comments

Popular posts from this blog

c# - How to get the current UAC mode -

postgresql - Lazarus + Postgres: incomplete startup packet -

javascript - Ajax jqXHR.status==0 fix error -