BSA 8.9.02 Rolling Update 1 (RU1)
This topic contains instructions for downloading and installing Rolling Update 1 on BMC Server Automation (BSA) 8.9 SP2. A Rolling Update provides product fixes by updating specific files in existing BSA components, thus delivering the latest product fixes without having to upgrade the entire product. Rolling Updates are installed on top of a service pack without affecting the product version or build number.
The Rolling Updates discussed in this page can only be installed on BMC Server Automation 8.9 SP2. Do not install the updates on any other release of BMC Server Automation.
Rolling Updates available for 8.9 SP2
The following table lists the Rolling Updates provided for BMC Server Automation 8.9 SP1 along with their release dates.
|Base Release||Build number||Rolling Update||Release date|
Service Pack 2 for BMC Server Automation 8.9
|Rolling Update (RU) 1||March 16, 2018|
Preparing for installation
Before you begin installing the Rolling Update, check the following prerequisite:
- BMC recommends that you to go through the list of product fixes mentioned here.
Download the latest available Rolling Update
You can access and download the installation files for RU 1 from the following FTP location:
You must be logged on to this page to view the FTP URL.
Verify the downloaded content by using the following check sums:
Linux Application Server files
Windows Application Server files
File Path and Name
Download and extract the required zip packages on your Application Servers as described below:
- Downloading the files on your Application Servers
Depending on the type of operating system running on your Application Servers, download either of the following zip packages from the FTP location.
Copy and extract the zip package to temporary folder (for example /tmp on Linux or C:\temp on Windows) on your Application Servers.
Step 1: Installing on all Application Servers in your environment
Perform the following steps on all Application Servers in your BMC Server Automation environment:
Log on to your Application Server with a user having root or Administrator privileges.
- Navigate to the temporary location where you have extracted the installation files, as described in this step.
Execute the rollingUpdateInstaller.nsh script using the following command in cmd or shell terminal:
The Application Server will restart twice for the installation to complete successfully.
The following message is displayed:
#### Rolling Updatation Completed Successfully ####
Repeat the above steps on all other Application Servers in your environment.
Wait for the installation process to complete successfully on one Application Server, before beginning the installation process on another Application Server. Running installations on different Application Servers simultaneously will result in errors during installation.
Verify whether all Application Servers have been updated successfully by using both the following options:
By checking the Rolling Update version in the RU_Version file at the following application server location:
Microsoft Windows C:\Program Files\BMC Software\BladeLogic\RU_Version Linux /opt/bmc/bladelogic/RU_Version
By running the following SQL query in your database:
Select ID, RU_VERSION, STATUS, APPSERVER_NAME, EXECUTION_TIME from ROLLING_UPDATE;
ID RU_VERSION STATUS APPSERVER_NAME EXECUTION_TIME ---------- ---------------- ----------------------------------------------------------------- 1 8.9.02.329-RU1 success bsaappserverhost01 09-MAR-18 04.10.53.634000 PM
BSA Rolling Updates are cumulative type of updates. When you install a particular Rolling Update, product fixes from earlier updates are also added to the product. For example, when you install RU 3, all product fixes added in RU 1 and RU 2 will also be installed along with RU 3 product fixes. See the below table for a list of product fixes and the Rolling Update that they were corrected in.
|Defect ID||Category||Description||Corrected in|
When you run multiple Update Server Property jobs with same set of targets in parallel, this leads to database deadlock.
When you use json as input parameter in POST method, you receive the following error message:
For Agent Installer Jobs, you got connection timeout error message instead of connection lost message because of hard coded list.
If there is a heavy load on the application server, NSH script job stops responding and still shows in running state even after JOB_TIMEOUT is reached.
|QM002369864||Application Server||The License Utility BLCLI command does not provide full data.||RU1|
|QM002371390||Application Server||BLCLI server does not handle inputs that contains Microsoft windows EOL characters.||RU1|
The I/O releated error messages in the BLCLI server are confusing.
When you open a Solaris patch, Is Reboot Required field is not set as expected.
In SUSE, zypper-based analysis is not populating the count of installed rpms (rpm -qa) in BL_PATCH_RES_DEVICE_CNT table as expected.
When patching multiple servers simultaneously, you receive the following error message on BMC Server Automation servers:
In BMC Server Automation 8.9.00, Compliance Run Result from RCP export is significantly slower than BLCLI export.
When you try to create an empty NSH script for the second time, you receive the following error message: