Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-3236

issues with AMQ 7.5 templates on OpenShift having default boolean values.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • AMQ 7.6.0.GA
    • AMQ 7.5.0.GA, AMQ 7.6.0.GA
    • None
    • None
    • Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration
    • Low
    • Hide

      It can be solved simply by adding quotes to boolean values in the source template, only to value fields, for example value: "true"

      Show
      It can be solved simply by adding quotes to boolean values in the source template, only to value fields, for example value: "true"
    • Hide

      Same as mentioned in description

      Show
      Same as mentioned in description

      Following the installation instructions of the AMQ 7.5 on openshift, template ERROR is seen

      ]$ for template in amq-broker-75-basic.yaml \
      > amq-broker-75-ssl.yaml \
      > amq-broker-75-custom.yaml \
      > amq-broker-75-persistence.yaml \
      > amq-broker-75-persistence-ssl.yaml \
      > amq-broker-75-persistence-clustered.yaml \
      > amq-broker-75-persistence-clustered-ssl.yaml;
      >  do
      >  oc replace --force -f \
      > https://raw.githubusercontent.com/jboss-container-images/jboss-amq-7-broker-openshift-image/75-7.5.0.GA/templates/${template}
      >  done
      

      The above steps results in below ERROR

      Error from server (BadRequest): Template in version "v1" cannot be handled as a Template: v1.Template.Parameters: []v1.Parameter: v1.Parameter.Value: ReadString: expects " or n, but found f, error found in #10 byte of ...|,"value":false},{"de|..., bigger context ...|_ENABLE_METRICS_PLUGIN","required":false,"value":false},{"description":"Journal type to use; aio or |...
      
      

            rhn-support-rkieley Roderick Kieley
            rhn-support-hnaram Herambh Naram (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: