The following lists the fixed and known issues in this release. If you experience any of the following issues, open an incident with Teradata Customer Support and include the Key in your description.
Known Issues
TCMC
| Key | Description |
|---|---|
| TCMC-1826 | When users attempt to disable the 'Internet connection' option from the SETTINGS tab in the CCP UI, it gives an error saying, "There was a problem internal server error". The endpoint is returning error 500 when request to remove the CIDRs list is sent. Workaround: From UI there is no workaround as such. The users see the Internal Server Error dialog, when attempting to disable the option. The user can close the error dialog, but there is no way to disable the option. Hence once enabled, the 'Internet Connection' option cannot be disabled from SETTINGS tab due to the underlying issue in the backend. Deployments: Affected deployments (AZURE, Google Cloud) |
Core Services
| Key | Description |
|---|---|
| CORESRVS-2046 | After QueryGrid is deployed when adding your new datasource, you must provide your Google Cloud project number so that it can be trusted by Private Service Connect Load Balancers. During this process, QueryGrid resources are detached from VantageCloud Lake Private Service Connect Load Balancers, disrupting future network communication vital to QueryGrid functioning properly. Workaround: A change request must be opened to re-attach the QueryGrid resources to the Load Balancers. Deployments: Any VantageCloud Lake on Google Cloud deployment where QueryGrid is also deployed. |
Global Provisioner
| Key | Description |
|---|---|
| GPS-1026 | If cross-AZ private link is being set up, the associated security groups must be updated with the regional CIDR information. Workaround: Submit a request from Support Portal to have Teradata add the regional CIDR to the necessary security groups. Deployments: AWS accounts with cross-AZ privatelink configuration. |