ASAP and ROC Logout 404 Errors After Upgrade To 6.6

book

Article ID: 107010

calendar_today

Updated On:

Products

CA Release Automation - Release Operations Center (Nolio) CA Release Automation - DataManagement Server (Nolio)

Issue/Introduction

Upgraded the Release Automation from v 6.4 to v 6.6. After the upgrade an http 404 error is observed when:
  1. Clicking on the launch button and/or clicking on the cog icon to download the asap.jnlp java client.
  2. Clicking the logout button to logout of the ROC web UI.

 

Cause

These behaviors were observed after an upgrade that had failed. The reason why this upgrade failed is because the upgrade takes the values for the directory server from the distributed.properties file and puts it into the database - since 6.6 brings user and directory server management into the ROC UI. The problem is that the directory.server.admin_username column allows 100 characters and the value in this environment was 120 characters.


Log message found in the center_upgrade.log that showed the failure message at which point it completely stops the upgrade process:
2018-07-08 14:22:21,199 [localhost-startStop-1] ERROR (com.nolio.platform.server.dataservices.services.upgrade.UpgradeDBServiceImpl:244) - Upgrade failed - Exception caught during upgrade [String or binary data would be truncated.; SQL [n/a]; nested exception is org.hibernate.exception.DataException: String or binary data would be truncated.]. Please manually update the version table back to the previous version.
org.springframework.dao.DataIntegrityViolationException: String or binary data would be truncated.; SQL [n/a]; nested exception is org.hibernate.exception.DataException: String or binary data would be truncated.
        at org.springframework.orm.hibernate3.SessionFactoryUtils.convertHibernateAccessException(SessionFactoryUtils.java:663)
        at org.springframework.orm.hibernate3.HibernateAccessor.convertHibernateAccessException(HibernateAccessor.java:414)

 

Environment

Upgrade from 6.4.0.10072 to 6.6.0.9640

Resolution

  1. Stop the services on the management server.
  2. Restore the backups taken for the CA Release Automation file system and restore the database.
  3. Once the backups have been restored, review your distributed.properties file and determine if the username is using an appropriate value.
Note:
Active directory environments are expected to use the userPrincipalName attribute value (ex: [email protected]). Distinguished Name values are commonly used with non active directory ldap servers.
  1. If you are using a non active directory account with a DN value that is longer than 100 characters then you can temporarily set the username to a value that is shorter than 100 characters to get past the upgrade.
  2. Start the upgrade.
  3. After the upgrade you increase the size of the directory_server.admin_username column to a value that would accommodate your value.
  4. After increasing the size of your directory_server.admin_username column you can login to the ROC, goto Administration -> User Management -> Directory Servers and edit the username value to the appropriate value.