In Usage Engine 2.1.0, there are the following known issues:
If you are using scripted solutions requiring return codes, you must use the mzsh commands, since the mzcli commands do not provide return codes.
Mzcli - wflist - '-not-member-of-wfgroup' throws exception on classic Usage Engine installation.
When looking at pico details, either in the Web Interface or in the Pico Viewer, the details may not be entirely correct regarding number of CPUs and IP address.
There is a bug when performing OpenAPI validation for parameters of the enum type. The bug is based on: https://bitbucket.org/atlassian/swagger-request-validator/issues/161/mockmvc-openapi-30-type-of-enum-parameter
The error is recorded as:
This occurs when you send a request to an NRF server that is configured using our HTTP2 Server agent with OpenAPI validation enabled. You will be meet with a Bad Request error (Error 400) and the validation fails. There was an issue with the specifications for the type enum within the 'anyOf' section as seen from the example below.
Example: NFType found in TS29510_Nnrf_NFManagement.yaml
A workaround would be to add the 'type: string' parameter on the same level as the 'anyOf'.
It is recommended not to use or create an encrypted dynamic workflow as you will not able to make any changes to the workflow in the web interface.
If you have an old webservice configuration from 8.x that uses keystore then the existing Security profile will be empty and to use a Security profile, you need to create a new one. This also applies to Diameter if it uses the Security profile.
When running the disconnect [hide]mzcli[/hide][hide]10.6[/hide] command in a containerized solution the ECD will unexpectedly terminate.
Settings for the platform, values.yaml:
The setup files for AWS installation does not contain a provider that supports the new M1 Mac darwin_arm64 architecture.
The error is recorded as:
When using Netty 3 there is a known vulnerability (CVE-2019-10797 according to NIST) and the solution and workaround is to use Netty 4.
In other words, the known vulnerability (CVE-2019-10797) does not affect you if you are using Netty 4.
To be backward compliant in terms of performance requirements, it is not feasible to remove Netty 3 from MediationZone at this point.
https://jira.digitalroute.com/browse/XE-4901 Mzcli - wflist - '-not-member-of-wfgroup' throws exception on baremetal
XE-4859 Mzcli - k8s - disconnect causes ecd to be killed
https://jira.digitalroute.com/browse/XE-5846 Not possible to use terraform on a new Mac with darwin_arm64 architecture
https://jira.digitalroute.com/browse/XE-4297 mzonline workflow throws error when I have encrypted wfs