In Usage Engine 3.3In Usage Engine 4.0, there are the following known issues:
Table of Contents | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
Anchor |
---|
...
|
The property controlling if Enhanced Security is enabled or not, mz.security.user.control.enabled
is not enabled by default and has to be manually added to the values.yaml file, see Enhanced User Security (4.0).
Anchor | ||||
---|---|---|---|---|
|
If you are using scripted solutions requiring return codes, you must use the mzsh commands, since the mzcli commands do not provide return codes.
...
When having changed fields in the Workflow Properties from being dynamic per workflow to being final, you may have problems running the workflow in the Web Interface.
Anchor | ||||
---|---|---|---|---|
|
...
Info | ||
---|---|---|
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'.
...
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 configuring workflow properties for Datahub task agent, the browse selection dialog for data hub profile does not show the available profiles for selection
Anchor | ||||
---|---|---|---|---|
|
...
Code Block |
---|
Error during request validation: [Path ‘/requesterPlmn’] Instance type (string) does not match any allowed primitive type (allowed: [“object”]) |
Anchor | ||||
---|---|---|---|---|
|
When creating EC Deployments, it is no longer possible to directly edit the workflows that you add to the EC Deployment.
Anchor | ||||
---|---|---|---|---|
|
Users are encountering an issue with request body validation when using a schema file that includes discriminator
and oneOf
keywords in the same schema object. This issue arises due to a limitation in the library implementation.
There is an existing ticket logged on this issue, see https://bitbucket.org/atlassian/swagger-request-validator/issues/771/discriminator-is-not-working-with-oneof. To work around this issue, you can disable request validation for requests containing the schema object.
Anchor | ||||
---|---|---|---|---|
|
Users might encounter a “NoClassDefFoundError” in Data Hub Forwarding agent in Usage Engine 4.0. This is caused by an unintentional removal of a library dependency. To resolve this, the change will be reverted in the subsequent minor release of Usage Engine 4.0.
Page Properties | ||
---|---|---|
| ||
Source bugs for mentioned issues: https://digitalroute.atlassian.net/browse/XE-2989 - mzcli: return code improvement → not sure this is the right bug https://digitalroute.atlassian.net/browse/XE-4297 - mzonline workflow throws error when I have encrypted wfs → check when EOL of MZOnline is scheduled10946 - SAP CC Notification Agent TLS Feature Not Working https://digitalroute.atlassian.net/browse/XE-5846 - Not possible to use terraform on a new Mac with darwin_arm64 architecture12019 - Validation Error for Unsupported Optional Parameters in HTTP2 Client https://digitalroute.atlassian.net/browse/XE-10946 - SAP CC Notification Agent TLS Feature Not Working12201 - Enhanced Security is not Enabled by Default https://digitalroute.atlassian.net/browse/XE-10736 - 3GPP Rel-17 - OAuth2 Access Token Request (OpenAPI Validation Error for Unsupported Optional Parameters in HTTP2 Client)12284 - Workflows Can Only Be Viewed When Creating ECDs https://digitalroute.atlassian.net/browse/XE-12019 - Open API Incorrectly Validates Request Body https://digitalroute.atlassian.net/browse/XE-12882 - Data Hub Workflow Aborts with “NoClassDefFoundError” When updating for a new release:
|