New Change Requests become stuck at every Approval Node regardless of Approval status in RSA Identity Governance & Lifecycle
RSA Product Set: RSA Identity Governance & Lifecycle RSA Version/Condition: All Platform/Application Server: WildFly Platform: SUSE Linux Enterprise Server (SLES)
New Change Requests become stuck at each node of the Approval Workflow even if the request has been approved or no approval is required.The Change Request remains in the Approval phase long after all needed approvals have been completed and eventually moves to the Fulfillment phase, possibly more than a day later.
There is a time difference between the WildFly application server and the Oracle database.
To resolve this issue, login to the RSA Identity Governance & Lifecycle server as the oracle user and follow the below steps to adjust the time.
Stop RSA Identity Governance & Lifecycle and the Oracle services:
Switch to the root user and set the correct time zone. This step may be skipped if the configured timezone is correct.
If /etc/localtime is NOT a symbolic link:
Check the contents of /etc/localtime to verify if the timezone is already correct. If it is, then skip to Step 3.
Backup the currently configured timezone:
cp /etc/localtime /etc/localtime.backup_<date>
Find your correct timezone in /usr/share/zoneinfo. An example would be /usr/share/zoneinfo/US/Eastern.
Replace the currently configured timezone with the correct one.
cp <new_timezone> /etc/localtime
cp /usr/share/zoneinfo/US/Eastern /etc/localtime
If /etc/localtime is a symbolic link:
Check the link to verify if the timezone is already correct. If it is, then skip to Step 3.