Hide Forgot
Created attachment 1219456 [details] json file used to create the pods Description of problem: oc create -f created and deployed the pods with json input in 3.3 but with 3.4 after the oc create had to issue oc rollout to deploy the deployment configs Version-Release number of selected component (if applicable): openshift v3.4.0.24+52fd77b kubernetes v1.4.0+776c994 etcd 3.1.0-rc.0 How reproducible: Always Steps to Reproduce: 1.Run the below commands both in 3.3 and 3.4 (json file attached) root@ip-172-31-47-12: ~/svt/openshift_scalability/content/quickstarts/cakephp # 2. oc new-project cakepv Now using project "cakepv" on server "https://ip-172-31-47-12.us- west-.compute.internal:8443". You can add applications to this project with the 'new-app' command. For example, try: oc new-app centos/ruby-22-centos7~https://github.com/openshift/ruby-ex.git to build a new example application in Ruby. 3. root@ip-172-31-47-12: ~/svt/openshift_scalability/content/quickstarts/cakephp # oc process -f cakephp-mysql-pv.json | oc create -f - service "cakephp-mysql-example" created route "cakephp-mysql-example" created imagestream "cakephp-mysql-example" created buildconfig "cakephp-mysql-example" created persistentvolumeclaim "mysql" created deploymentconfig "cakephp-mysql-example" created service "mysql" created deploymentconfig "mysql" created 4. wait for the pods to get deployed 4. oc get pods Actual results: in 3.3 both the mysql and cakephp pods get deployed and go into running state after successful deployment but in 3.4 the mysql never gets deployed and in turn makes the cakephp deployment go into error. Here is the output: root@ip-172-31-47-12: ~/svt/openshift_scalability/content/quickstarts/cakephp # oc get pods NAME READY STATUS RESTARTS AGE cakephp-mysql-example-1-build 0/1 Completed 0 2m cakephp-mysql-example-1-deploy 1/1 Running 0 1m cakephp-mysql-example-1-hook-pre 0/1 CrashLoopBackOff 3 1m Expected results: As in 3.3 the mysql and cakephp pods should come up and be in running state in 3.4 Additional info: json file attached as an attachment to the bug.
You have to change the value of "automatic: false" to "automatic: true" in order to trigger automatic rollout of the mysql database. The behavior changed between 3.3 and 3.4 and it is described in the release notes (Michalis can provide link).
https://github.com/openshift/origin/blob/master/UPGRADE.md#origin-14x--ose-34x
Michal & Michail, Thanks for the clarification. I changed the automatic flag on the db trigger and it is behaving as expected per the release notes. I'm closing this bug