Description of problem: Cannot create app use amq62-ssl template Version-Release number of selected component (if applicable): openshift v3.4.0.16+cc70b72 kubernetes v1.4.0+776c994 etcd 3.1.0-rc.0 How reproducible: alwasy Steps to Reproduce: 1.oc new-app --template=amq62-ssl --param=AMQ_TRUSTSTORE_PASSWORD\=password,AMQ_KEYSTORE_PASSWORD\=password 2. 3. Actual results: --> Deploying template "openshift/amq62-ssl" to project lk1wr amq62-ssl --------- Application template for JBoss A-MQ brokers. These can be deployed as standalone or in a mesh. This template supports SSL and requires usage of OpenShift secrets. * With parameters: * APPLICATION_NAME=broker * MQ_PROTOCOL=openwire * MQ_QUEUES= * MQ_TOPICS= * MQ_SERIALIZABLE_PACKAGES= * MQ_USERNAME=userKRa # generated * MQ_PASSWORD=HRp4XbiQ # generated * AMQ_SECRET=amq-app-secret * AMQ_TRUSTSTORE=broker.ts * AMQ_TRUSTSTORE_PASSWORD=password * AMQ_KEYSTORE=broker.ks * AMQ_KEYSTORE_PASSWORD=password * AMQ_MESH_DISCOVERY_TYPE=kube * AMQ_STORAGE_USAGE_LIMIT=100 gb * IMAGE_STREAM_NAMESPACE=openshift --> Creating resources ... service "broker-amq-amqp" created service "broker-amq-amqp-ssl" created service "broker-amq-mqtt" created service "broker-amq-mqtt-ssl" created service "broker-amq-stomp" created service "broker-amq-stomp-ssl" created service "broker-amq-tcp" created service "broker-amq-tcp-ssl" created error: DeploymentConfig "broker-amq" is invalid: spec.strategy.rollingParams.maxUnavailable: Invalid value: 0: cannot be 0 when maxSurge is 0 as well --> Failed Expected results: succeed Additional info:
This appears to be a breaking change in the OCP 3.4.0 release, I'm trying to find out more information
Can somebody provide the template that is being used to reproduce this? We had this bug come up a few releases ago and it has being fixed since then, I am not sure why is it suddenly an issue for 3.4.
From the error message it seems that OCP 3.4 sets maxUnavailable to 0 (i.e. default value) and a check was added that at least one of (maxUnavailable, maxSurge) has to be greater than zero. In xPaaS templates for A-MQ we only specify maxSurge = 0. To resolve this issue, we should probably add also maxUnavailable = 1 (or add a parameter specifying this).
I have a fix for this in https://github.com/openshift/origin/pull/11678
Verified with : openshift v3.4.0.24+52fd77b kubernetes v1.4.0+776c994 etcd 3.1.0-rc.0 oc new-app --template=amq62-ssl --param=AMQ_TRUSTSTORE_PASSWORD\=password --param=AMQ_KEYSTORE_PASSWORD\=password --> Deploying template "openshift/amq62-ssl" to project haowang amq62-ssl --------- Application template for JBoss A-MQ brokers. These can be deployed as standalone or in a mesh. This template supports SSL and requires usage of OpenShift secrets. * With parameters: * APPLICATION_NAME=broker * MQ_PROTOCOL=openwire * MQ_QUEUES= * MQ_TOPICS= * MQ_SERIALIZABLE_PACKAGES= * MQ_USERNAME=userYS1 # generated * MQ_PASSWORD=3LaNAKwO # generated * AMQ_SECRET=amq-app-secret * AMQ_TRUSTSTORE=broker.ts * AMQ_TRUSTSTORE_PASSWORD=password * AMQ_KEYSTORE=broker.ks * AMQ_KEYSTORE_PASSWORD=password * AMQ_MESH_DISCOVERY_TYPE=kube * AMQ_STORAGE_USAGE_LIMIT=100 gb * IMAGE_STREAM_NAMESPACE=openshift --> Creating resources ... service "broker-amq-amqp" created service "broker-amq-amqp-ssl" created service "broker-amq-mqtt" created service "broker-amq-mqtt-ssl" created service "broker-amq-stomp" created service "broker-amq-stomp-ssl" created service "broker-amq-tcp" created service "broker-amq-tcp-ssl" created deploymentconfig "broker-amq" created --> Success Run 'oc status' to view your app.
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. https://access.redhat.com/errata/RHBA-2017:0066