Issue ID | Functional Area | Description | Workaround/Resolution |
TPDE-7248 | Web User Interface | The location name is case-sensitive which means a user can create multiple locations with the same name. As a result, even though they have the same name, they are treated as separate records. Also, if two records of the same location name are saved, only one record can be deleted. | There is no workaround. |
TPDE-7910 | Installation on Red Hat Enterprise Linux 9.2 | When installing Automation Suite in a Red Hat Enterprise Linux 9.2 HA setup with security agents running, the installation fails. | Run this command to stop the service: systemctl stop mfetpd After the installation is completed, run this command to start the service:
|
TPDE-7961 | Server onboarding | Brownfield server onboarding is not supported by the CCP API. | There is no workaround. |
TPDE-8161 | License | When one of the control plane (CP) nodes are powered Off, sometimes the CCP API or Facade API may throw a license error. | Contact Dell Customer Support. |
TPDE-8202 | Network issue | When one of the control plane (CP) nodes are disconnected from the network, sometimes the quorum may be lost. | Contact Dell Customer Support. |
TPDE-8217 | Pod scheduling | Pod is not scheduled (not Ready state) after restart or network disconnection of the CP node. | Deleting the pod will reschedule the pod successfully after the core services are up. |
TPDE-8384 | Server onboarding | Default credentials are not used while onboarding a server. | Update the default-credential-secret with the base64-encoded content of the cred.yaml attribute. |
TPDE-8537 | API | When a server is onboarded using a blueprint file, you cannot delete the server when the deployment ID is different from the server name in the inputs. Also, if you have created multiple deployments for a server with different deployment IDs, duplicate server entries are returned when performing a Get Server API call. | The resource payload or deployment inputs should have unique names for each resource deployment and should be the same name as the resource ID. |
TPDE-8655 | Server onboarding (Scaling) | To bring up the DTIAS instance in a high availability mode with remote nodes, onboard the servers in batches (15 at a time). Wait for all the deployments in a batch to complete and trigger the next batch. The deployment fails at times, although the servers are onboarded. | Delete the failed servers and onboard again. |
TPDE-8723 | Uninstalling Dell Telecom Infrastructure Automation Suite (Automation Suite) | When uninstalling Automation Suite, the docker images are not deleted. | After uninstalling Automation Suite, run the following command to clean up the docker images: |
TPDE-8729 | Installing Automation Suite | After a successful Automation Suite installation, the license-manager pods restart and the following error message displays: "statefulsets.apps \"redis-sentinel\" not found" | The license-manager pods restart until the Redis pods are available, and then connect to the Redis pods. |
TPDE-8771 | Site creation | When attempting to create a site without activating the license, the site creation fails as expected. However, once the license is activated, the site creation still fails. | Delete the site using the API, then create the site. |
TPDE-8784 | Remote site creation | Remote site creation fails due to hostname being in uppercase. | Ensure that the hostname is in lowercase. |
TPDE-8841 | Firmware update | NVIDIA NIC Firmware update fails with error 'version mismatch' | It is recommended to use the latest firmware version 26.39.10.02. |
TPDE-8884 | Remote site creation | Remote site creation fails with bmo_secret error. | Re-create the bmo_secret using the CCP-API. |
TPDE-9268 | Operating system (OS) installation | Disk check is taking a long time to complete during Red Hat Enterprise Linux OS installation. | Skip the disk check. Steps to skip disk check when Red Hat Enterprise Linux OS is booting from the iDRAC console:
or Press Escape in the iDRAC console when onboarding a server. |
TPDE-9316 | Deployment | After deploying a management cloud and a workload cloud using CCP API, it is possible to delete the management cloud first without deleting the workload cloud. | First, delete all the workload clouds that are associated with the management cloud. Ensure that there are no workload clouds present for that management cloud. After that, delete the management cloud. |
TPDE-9483 | SCP profile | SCP profile fails to apply from one server to another because the servers did not have identical hardware. | When applying SCP profile from one server to another, ensure that the source and target servers have identical hardware configurations. |
TPDE-9484 | Server deletion | Server deletion fails due to server in failed state. | Contact Dell Customer Support. |
TPDE-9479 | Deployment | The management cloud or workload cloud deployment might fail sometimes due to a scenario when rabbitmq pods restart. | Contact Dell Customer Support. |
TPDE-9562 | Deployment | During deletion of a workload cloud, one of the servers remains in a pending or a queued state. | Contact Dell Customer Support. |
TPDE-9780 | Deployment | After reboot of CP node, some of the pods that are associated with longhorn pvc, along with longhorn share-manager pod do not come up. | Contact Dell Customer Support. |
TPDE-9901 | Web User Interface | For Dell servers, the Automation Suite web user interface displays the PORT ID of the embedded NIC interfaces in the incorrect format. The expected format is <slot number> <port number> <partition number>. But the displayed format is <port number> <Slot number> <partition number>, which is not the correct format. | There is no workaround. |
TPDE-10226 | API | When running the GET all cloud API on a single node cloud, it is taking a long time to receive a response. | In the API, the response time of GET on a single cloud is faster than GET all cloud . |