Network automation UI

Error message is shown when creating objects that says that the object already exists

Symptom

When you create an object, you might see an error message that says that an object with the same name already exists, even if you cannot see an object with the same name. The objects affected are assembly instances, deployment locations, infrastructure keys, network packages, and secret groups.

Cause

This error happens when all of the following conditions occur:

• The object that you are trying to create is of the same type and has the same name as an existing object.
• The existing object is in a different object group to the one in which you are trying to create the object.
• For the object group that the existing object belongs to, you don't have permission to view the same type of object that you are trying to create.

Solution

Use a different name for the object.

Deployment location is not created or updated after properties are specified

Symptom

When you are creating or editing a deployment location and enter valid properties in JSON format in the Infrastructure-specific Properties field, then click Save, the execution of the assembly might fail. The Ansible® driver logs might contain an Unexpected exception running playbook message.

Cause

JSON objects with simple key-value pairs are not affected by this issue. For example, if you enter the following properties, the assembly functions correctly:

{
             "host_password": "password",
             "host_username": "admin",
             "redfish_password": "password",
             "redfish_username": "Administrator"
           }

However, if a JSON object contains a nested object, the execution of the assembly fails. For example, if you enter the following properties, the execution of the assembly fails:

        {
       "192.0.2.1": {
             "host_password": "password",
             "host_username": "admin",
             "redfish_password": "password",
             "redfish_username": "Administrator"
           }
     }

Solution

To specify a nested map of data properties in the JSON object, use the following structure:

{"propertyName": {
    "type": "map",
    "value": {
      "nestedMapElementName1": "nestedMapElementValue1"
      "nestedMapElementName2": "nestedMapElementValue2"
      ...
      ...
    }
}

The following example shows how you can specify a nested map of authentication properties:

{
    "192.0.2.1": {
        "type": "map",
        "value": {
          "host_password": "password",
          "host_username": "admin",
          "redfish_password": "password",
          "redfish_username": "Administrator"
        }
}

Assembly instance enters null state after intent process is cancelled

If you cancel an intent process at a particular point, the assembly instance might enter the null ("Unknown") state. For example, if you cancel an intent process during a Delete phase of an assembly upgrade, the assembly instance enters the null state. When the assembly instance is in the null state, the New Intent button becomes unavailable on the UI. When an assembly instance is in the null state, you can submit a new intent only by using the API.

An assembly instance that is in the null state is not displayed on the Recent Assembly Instances page, but you can find it in the Assembly Instance Search page.

v(...).then is not a function message is shown in UI

Symptom

The network automation UI might display the following error message:

v(...).then is not a function

Cause

This error happens when the browser cache needs to be cleared.

Solution

Clear your browser cache, then log in to the network automation UI again.