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

pageSizeBytes type mismatch between CRD and Operator

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • AMQ 7.7.0.OPR.2.GA, AMQ 7.8.0.dev
    • operator
    • None
    • False
    • False
    • ?
    • Hide
      In the previous release, if you added an address settings configuration to the Custom Resource (CR) instance for a broker deployment (that is, by adding an `addressSettings.addressSetting` section), you could not include the `pageSizeBytes` property in the address settings. If you included this property and specified a value, the Operator either failed to process the CR, or it processed the CR but could start any brokers. This issue is now resolved.
      Show
      In the previous release, if you added an address settings configuration to the Custom Resource (CR) instance for a broker deployment (that is, by adding an `addressSettings.addressSetting` section), you could not include the `pageSizeBytes` property in the address settings. If you included this property and specified a value, the Operator either failed to process the CR, or it processed the CR but could start any brokers. This issue is now resolved.
    • Documented as Resolved Issue
    • Verified in a release
    • Hide

      for CR error add the entry below in the CR:
       

      addressSetting:
  - match: addressDrop
    maxSizeBytes: 1Mb
    pageSizeBytes: 512K

       Then apply the CR using:

      oc apply -f the CR_example_file.yml

       
      for operator error add the entry below in the CR:

      addressSetting:
  - match: addressDrop
    maxSizeBytes: 1Mb
    pageSizeBytes: 512000

       Then apply the CR using: 

      oc apply -f the CR_example_file.yml
      Show
      for CR error add the entry below in the CR:   addressSetting: - match: addressDrop maxSizeBytes: 1Mb pageSizeBytes: 512K  Then apply the CR using: oc apply -f the CR_example_file.yml   for operator error add the entry below in the CR: addressSetting: - match: addressDrop maxSizeBytes: 1Mb pageSizeBytes: 512000  Then apply the CR using:  oc apply -f the CR_example_file.yml

    Description

      I am not able to use pageSizeBytes in address settings in the CR.

      CRD says this property must be a integer, but the CRD description says it can be specified as a string using K,Mb,Gb notation.
      From CRD:

      pageSizeBytes:                            
  description: >-
    The page size in bytes to use for an address. Supports byte notation like K, Mb, GB, etc.
   type: integer

      If I try to use a string notation, like 512K in the CR, it is no applied and exited with the log message:

      The ActiveMQArtemis "ex-aao" is invalid: spec.addressSettings.addressSetting.pageSizeBytes: Invalid value: "string": spec.addressSettings.addressSetting.pageSizeBytes in body must be of type integer: "string"

      If I use a integer value like 512000, CR is applied by operator fails to create an broker instance with the and log the error:

      E1023 13:06:58.544030       1 reflector.go:134] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:126: Failed to list *v2alpha3.ActiveMQArtemis: v2alpha3.ActiveMQArtemisList.Items: []v2alpha3.ActiveMQArtemis: v2alpha3.ActiveMQArtemis.Spec: v2alpha3.ActiveMQArtemisSpec.AddressSettings: v2alpha3.AddressSettingsType.AddressSetting: []v2alpha3.AddressSettingType: v2alpha3.AddressSettingType.PageSizeBytes: ReadString: expects " or n, but found 5, error found in #10 byte of ...|zeBytes":512000},{"a|..., bigger context ...|ddressDrop","maxSizeBytes":"1Mb","pageSizeBytes":512000},{"addressFullPolicy":"FAIL","match":"addres|...

       

      Attachments

        Activity

          People

            rhn-support-rkieley Roderick Kieley
            tbueno@redhat.com Tiago Bueno
            Tiago Bueno Tiago Bueno
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: