Upgrading Gateways from v15.0.0 to v15.1.0

Known Issues in v15.0.0 to v15.1.0 upgrade

We are aware of a known issue in the v15.0.0 NextGen gateway. Few customers encountered difficulties upgrading their gateways from v15.0.0 to v15.1.0 through the OpsRamp UI. However, we have successfully addressed this issue in v15.1.0. To perform the upgrade from v15.0.0 to v15.1.0, customers are advised to manually upgrade their gateways using any one of the following solutions:

Note

Customer needs to allow the upgrade in the OpsRamp UI.

Solution 1:

Login to OpsRamp portal and navigate to Automation > scripts section.
Create a category (global or specific partner/client based on the required scope).
Create a script by selecting the below mentioned drop-down:
- Select Script Type > Global Script / Partner or Client Script (Based on the required scope of the script).
- Execution Type > SHELL
- Platform > Supported on Linux and provide other required details.
Add the following script in the Script field:

#!/usr/bin/sh 

logFileName="/tmp/ondemand-job.log" 

echo "$(date) : Creating yaml file" >> $logFileName 

kubectl get cm vprobe-updater-cm -n $1 -o jsonpath='{.data.ondemand-job\.yaml}' > /tmp/ondemand-job.yaml 

  

if [ $? -eq 0 ]; then 

        echo "$(date) : Successfully created yaml file" >> $logFileName 

        echo "$(date) : Creating  on-demand job" >> $logFileName 

        kubectl apply -f /tmp/ondemand-job.yaml -n $1 

        if [ $? -eq 0 ]; then 

                 echo "$(date) : Successfully created on-demand job" >> $logFileName 

        else 

                 echo "$(date) : Failed to  created on-demand job" >> $logFileName 

        fi 

else 

       echo "$(date) : Failed to create yaml file" >> $logFileName 

fi

Add the following parameters to the script


Functionality	Description
Name	Enter the name for the configuration.
Description	Provide a description for the configuration.
Default Value	Enter a default value for the configuration.
Type	Select the type from the drop-down list box.
Data Type	Select the data type from the drop-down listbox.

Go to your script and click the Apply scripts to devices option.

Select following data:


Functionality	Description
Client Name	Your client name
Group Name	Gateway
Devices	Select your gateway profile name.
Parameters	Please pass your gateway namespace(by default it will be default).

Click Run Now.

To check the successful execution of script verify /tmp/ondemand-job.log file.

tail -f /tmp/ondemand-job.log

Verify ondemand pod status
podname: nextgen-gw-updater-ondemand-jon-*

kubectl get pods

Solution 2:

If the gateway is not having an OpsRamp agent. Run the upgrade-gateway.sh script to upgrade gateways from v15.0.0 to v15.1.0.

Launch the gateway SSH console.
Create upgrade-gateway.sh file, add following content:

#!/usr/bin/sh 

logFileName="/tmp/ondemand-job.log" 

echo "$(date) : Creating yaml file" >> $logFileName 

kubectl get cm vprobe-updater-cm -n $1 -o jsonpath='{.data.ondemand-job\.yaml}' > /tmp/ondemand-job.yaml 

  

if [ $? -eq 0 ]; then 

        echo "$(date) : Successfully created yaml file" >> $logFileName 

        echo "$(date) : Creating  on-demand job" >> $logFileName 

        kubectl apply -f /tmp/ondemand-job.yaml -n $1 

        if [ $? -eq 0 ]; then 

                 echo "$(date) : Successfully created on-demand job" >> $logFileName 

        else 

                 echo "$(date) : Failed to  created on-demand job" >> $logFileName 

        fi 

else 

       echo "$(date) : Failed to create yaml file" >> $logFileName 

fi

Save the script and click Run.

sh upgrade-gateway.sh default

Note

If the gateway is running on another namespace, we recommend the namespace to be changed.

sh upgrade-gateway.sh {NAME SPACE}

Verify /tmp/ondemand-job.log file, to check the successful execution of script.

tail -f /tmp/ondemand-job.log

Verify the ondemand pod status.
podname: nextgen-gw-updater-ondemand-jon-*

kubectl get pods