Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Additional actions after the patch upgrade

The following defects require additional actions if you upgrade from the provided or earlier versions of BMC Release Process Management:

Defect

Description

Upgrade from version

DE93258

When you upgrade from version 4.6.00 on a system with a Postgres database with large amounts of data, a 500 Internal server error appears when you open the Currently Running Steps sub-tab from the Dashboard or Request tab.

4.6.00

DE88874

In database, there are duplicated records for the same version tag.

4.4.00

DE82434

When you use LDAP for authorization, users cannot access the assigned requests and steps until you update their user roles.

4.4.00

DE88790

When you use integration with BMC Release Package and Deployment for managing NSH server and use NSH user name and password in BMC Release Process Management automation steps, the NSH user password is saved as not encrypted text in BMC Release Package and Deployment logs.

Warning: The updated automation scripts work only if you integrate BMC Release Process Management version 4.4.00.03 or later with BMC Release Package and Deployment version 4.4.00.03 or later. After you install version 4.4.00.03 or later for both BMC Release Process Management and BMC Release Package and Deployment, update the automation scripts for BMC Release Package and Deployment.

4.4.00.02

DE89692

When you use automation scripts in a step, the automation keeps a reference to this steps after you delete this step.
 After upgrading to BMC Release Process Management version 4.4.00.04 or later, run the app:remove_deleted_steps_automation_reference rake task to remove references from the deleted steps to automations from your previous BMC Release Process Management version.

4.4.00.03

DE89044

When in a step of a request, you use the BMC Release Package and Deployment automation script and this step fails, the step log contains link to the last successful deployment log instead of the failed deployment log.

4.4.00.04

To apply updates

To update the BMC Release Process Management application, complete the following actions:

  1. Stop the BMC Release Process Management service for the current version.
  2. Navigate to RLMhome\bin and run the following executable file:
    • (Windows) setenv.bat

    • (UNIX) setenv.sh

      Note

       On UNIX, run the file with the following command:
      . ./setenv.sh

  3. Navigate to RLMhome\releases\<your current version>\RPM\config and perform the following actions:

    • To remove duplicated records for the version tag, run the following rake task:

      jruby –S rake version_tags:clear_duplicates

    • To fix the access for requests and steps for the LDAP users, run the following rake task:

      jruby -S rake user:assigned_apps:update_roles RAILS_ENV=production

    • To remove references from the deleted steps to automations, run the following rake task:

      jruby -S rake --verbose app:remove_deleted_steps_automation_reference


    • To update automation scripts for BMC Release Package and Deployment automatically, run the following rake task:

      Note

      If you made changes to the default automation scripts, and then you apply an automatic update for these scripts, your changes are not saved during the automatic scripts update.

      jruby -S rake --verbose scripts:automation:rlm_update

    • To update automation scripts for BMC Release Package and Deployment manually, open the automation scripts in a text editor, and then change the following code lines:

      write_to("Setting value for property: #{k.gsub("DE_", "")}")
      RlmUtilities.rlm_set_q_property_value(RLM_BASE_URL, RLM_USERNAME, RLM_PASSWORD, package_id, "package property add", k.gsub("DE_", ""), v)

      with these code lines:

      write_to("Setting value for property: #{k.gsub("DE_", "")}")
      encrypt = params["#{k}_encrypt"]
      RlmUtilities.rlm_set_q_property_value(RLM_BASE_URL, RLM_USERNAME, RLM_PASSWORD, package_id, "package property add", k.gsub("DE_", ""), v, encrypt)

      Note

      Click here to see the scripts to change.

      autoLib.PNG
       

    • To clean up old roles implementations leftover from the previous release, run the following rake task:

      jruby -S bundle exec rake app:update_step_frozen_owner
  4. Start the BMC Release Process Management service.

Related topics

Known-and-corrected-issues

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*