Release 1.1.9

DateVersion

 

1.1.9

Highlights

  • 1.1.9 is a bug fix release of following A-Stack Components
    • Monitoring Dashboard Application
    • Configurator Daemon

                                         

Steps to Upgrade from 1.1.8 to 1.1.9

Below are the steps to upgrade 1.1.8 to 1.1.9. Various components that can be upgraded are -

ComponentFromToScript Location
Configurator Daemon1.1.81.1.9Configurator Daemon Upgrade Script 1.1.8 to 1.1.9
Monitoring Dashboard1.1.81.1.9Monitoring Dashboard Upgrade Script 1.1.8 to 1.1.9

Pre-Steps

  1. Go to the installed folder of “A-StackConfigurator” OR “A-StackMonitoringDashboard” on VM where these components are installed
  2. Installed path can be checked by executing '$echo $TQL_HOME' command.
  3. It will return running path of TQL engine as below: /home/ec2-user/ConfiguratorUI/  Note: Path may be different
  4. Take a backup of A-StackConfigurator OR A-StackMonitoringDashboard's installed folder by executing following commands: 
    1. $ mkdir ConfiguratorUI_bkp
    2. $cp –avr ConfiguratorUI_bkp/ ConfiguratorUI/

Upgrade Steps

  1. Go to installed path of A-StackConfigurator OR A-StackMonitoringDashboard by following command: $ cd /home/ec2-user/ConfiguratorUI/ 
  2. Copy Script file into installed directory from location as specified in above table
    1. If A-StackMonitoringDashboard is used then, use ‘A-StackMonitoringDashboard-Upgrade.sh
    2. If A-StackConfigurator is used then, use ‘A-StackConfigurator-Upgrade.sh’
  3. Execute the following command:
    1. If A-StackMonitoringDashboard: $ sh A-StackMonitoringDashboard-Upgrade.sh
    2. If A-StackConfigurator: $ sh A-StackConfigurator-Upgrade.sh

Verify Upgrade Successful

On successful execution, success message will be displayed on the output console and Upgrade process is complete.

“Upgrade Completed”
“Upgrade script ended.”

How to Rollback

  1. If any error occurs then following message will be displayed:
    1. “Download failed. Please verify the Path”
    2. “Upgrade script ended..”
  2. Then delete the existing folder (/home/ec2-user/ConfiguratorUI/)
  3. And change the name of the directory '(/home/ec2-user/ConfiguratorUI_bkp' to '(/home/ec2-user /ConfiguratorUI'.
  4. Follow the same steps again from Upgrade Steps from 1.1.8 build to 1.1.9.

Note:  Folder name may vary as per installed folder.


Detailed List 

A-Stack 1.1.9 Jira List

JIRA-IDComponentTypeDescription
TQLPROD-1765Monitoring Dashboard, Configurator DaemonBugIssues in loading Alarms when Cluster has multiple VMs

Known Issues

JIRA-IDComponentTypeDescription
TQLPROD-1770Monitoring DashboardBugBy deleting alarm conditions using delete command- alarm conditions are still showing on UI has been successfully created.