v5.3.1.6
Date of Release: March 2023
Resolved Issues
| JIRA ID | Issue |
|---|---|
| IPD-20864 | The storage client secrets are visible in plain text in Infoworks log for ephemeral clusters. |
| IPD-20933 | When user configures incremental ingestion, the job fails with error records. |
| IPD-20934 | Infoworks is using information_schema.tables instead of information_schema.schemata for schema check. |
| IPD-21010 | The Append and Merge sync modes in pipeline build for the Snowflake CDW environments are running create database if not exists command. |
| IPD-21022 | User is unable to remove audit columns from Infoworks pipeline target in Snowflake CDW environment. |
| IPD-21039 | The fixed width sources expects newly added columns to be of Source type instead of Target type. |
| IPD-21060 | User is unable to create/edit source for the Operations Analyst, Database Admin, and Data Modeller role via API. |
| IPD-20936 | The Preview Data tab on the Infoworks pipeline fails to load data sometimes. |
| IPD-20931 | The Save and Save & Add Another buttons are not working in the aggregate node. |
| IPD-20949 | Upgrade from 5.3.1 to 5.3.1.5 is failing due to invalid image reference as there is a change in the image format in the templates resulting in pod failure. |
| IPD-20752 | The iw_environment_cluster_policy configuration does not take effect for ephemeral clusters |
| IPD-20082 | The API does not populate ClusterID for the Ephemeral cluster. |
| IPD-19720 | User is unable to read Snowflake warehouse name in config-migration APIs. |
| IPD-19773 | APIs are failing since private_key_file_details field is stored in JSON format instead of array format. |
| IPD-19801 | The job summary is not provided as a part of the Job Status API response. |
| IPD-19810 | User is able to set multiple default computes using API calls. |
| IPD-19900 | The zip file downloaded from Application Logs does not contain cluster logs. |
Upgrade
Prerequisites
Before going through the below mentioned prerequisites for this section, ensure that all the Prerequisites for Installing Infoworks on AKS are validated.
- Ensure the current deployment’s chart is present in Infoworks home directory (${IW_HOME})
- Validate that the version of the old chart is 5.3.1.
xxxxxxxxxxcat /opt/infoworks/iw-k8s-installer/infoworks/Chart.yaml | grep appVersionxxxxxxxxxxappVersion: 5.3.1Upgrade Instructions
To upgrade from 5.3.1 to 5.3.1.6, execute the following commands:
Step 1: Download the update-k8s.sh script using the below command
xxxxxxxxxxwget https://iw-saas-setup.s3.us-west-2.amazonaws.com/5.3/update-k8s.shStep 2: Give executable permission to the update-k8s.sh script.
xxxxxxxxxxchmod +x update-k8s.shStep 3: Run the update script using the below command.
xxxxxxxxxx./update-k8s.sh -v <version_to which_you want_to_update>xxxxxxxxxx./update-k8s.sh -v 5.3.1.6Step 4: You will receive a "Enter N to skip running the above command to upgrade the helm deployment." message. If you want to run helm upgrade manually, then type N and press Enter. There is a 30-second timeout set to abandon the deployment of the upgraded version. If no input is received within the timeout duration, the deployment is triggered.
xxxxxxxxxxEnter N to skip running the above command to upgrade the helm deployment. (timeout: 30 seconds): YRollback
Prerequisites
Ensure the current deployment’s chart is present in /opt/infoworks.
- Ensure the current deployment’s chart is present in Infoworks Home Directory (${IW_HOME})
- Validate that the version of the old chart is 5.3.1.6
To downgrade from 5.3.1.6 to 5.3.1, execute the following commands:
xxxxxxxxxxcat /opt/infoworks/iw-k8s-installer/infoworks/Chart.yaml | grep appVersionxxxxxxxxxxappVersion: 5.3.1Rollback Instructions
To downgrade from 5.3.1.6 to 5.3.1, execute the following commands:
Step 1: Download the rollback-k8s.sh script using the below command
xxxxxxxxxxwget https://iw-saas-setup.s3.us-west-2.amazonaws.com/5.3/rollback-k8s.shStep 2: Give executable permission to the rollback-k8s.sh script
xxxxxxxxxxchmod +x rollback-k8s.shStep 3: Run the rollback script using the below command.
xxxxxxxxxx./rollback-k8s.sh -v 5.3.1Step 4: You will receive a "Enter N to skip running the above command to upgrade the helm deployment." message. If you want to run helm upgrade manually, then type N and press Enter. There is a 30-second timeout set to abandon the deployment of the upgraded version. If no input is received within the timeout duration, the deployment is triggered.
xxxxxxxxxxEnter N to skip running the above command to upgrade the helm deployment. (timeout: 30 seconds): Y