Known Issues (3.1)

In Usage Engine 3.1, there are the following known issues:

Documentation for the 5G PCF SM Policy Data Model Not Complete

The description of the 5G PCF SM Policy data model example that is included in the Development Toolkit(3.1) and can be accessed in the PCC Extensions (3.1) is not described and will be made available in the next release.

Encrypted Workflows Cannot be Viewed in MZOnline

In MZOnline, any encrypted workflows cannot be viewed.

Documentation for System Properties Not Up-to-Date

The descriptions of properties in the Administrator Guide are not up-to-date, so ensure to check what is available in your yaml.values file. Documentation will be updated for the next minor release.

GET Method issue when using HTTP/2 Client with OpenAPI profile

When using the OpenAPI profile, you might encounter an issue where using the HTTP/2 Client to send a GET method to retrieve an API response. When the agent receives the response, you will encounter a Null Pointer Exception.

mzcli Commands Do Not Provide Return Codes

If you are using scripted solutions requiring return codes, you must use the mzsh commands, since the mzcli commands do not provide return codes.

Removing Dynamic Fields May Cause Problems in the Web Interface

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.

OpenAPI Validation Error for Type enum

There is a bug when performing OpenAPI validation for parameters of the enum type. The bug is based on:

The error is recorded as:

Error(s) during request validation: Unable to parse JSON - Unrecognized token'xxx': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false')

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'.

AWS Terraform Template does not Support M1 Mac with darwin_arm64 Architecture

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:

➜ terraform terraform init Initializing the backend... Initializing provider plugins... Finding hashicorp/aws versions matching "~> 2.0"... │ Warning: Version constraints inside provider configuration blocks are deprecated │ on line 5, in provider "aws": │ 5: version = "~> 2.0" │ Terraform 0.13 and earlier allowed provider version constraints inside the provider configuration block, but that is now deprecated and will be removed in a future version of │ Terraform. To silence this warning, move the provider version constraint into the required_providers block. │ Error: Incompatible provider version │ Provider v2.70.1 does not have a package available for your current platform, darwin_arm64. │ Provider releases are separate from Terraform CLI releases, so not all providers are available for all platforms. Other versions of this provider may have different platforms │ supported.

Datahub Profiles not shown in Workflow Properties Profile Selection Window

When configuring workflow properties for Datahub task agent, the browse selection dialog for data hub profile does not show the available profiles for selection