RollbackExecutor pauses the cluster for every rollback execution. This is excessive as it is only necessary to pause the cluster for upgrade rollbacks. Pausing the cluster causes certain platform features, such as previewing/committing update sets, to be disabled.

Steps to Reproduce

  1. Run an ATF test that creates or updates a large quantity of data.
  2. At the end of the test, while the lengthy rollback is taking place, attempt to preview/commit an update set.
  3. Observe the system will not allow you to do so.


This problem is under review. You can Subscribe to this article to receive notifications when more information will become available.

If you are certain the cluster is not paused for an upgrade or upgrade rollback, you can un-pause the cluster by running gs.resume(); from the Scripts - Background module.

Check sys_rollback_context for records with a state of "Reverting" to see what is being rolled back. To verify there is no upgrade in progress, check the Upgrade Monitor module and the worker threads on all nodes.


Related Problem: PRB1307843

Seen In

SR - IntegrationHub - Jenkins Integration r1 - v1.2.0
SR - IntegrationHub - JIRA Service Desk Integration r2 - v2.0.0
SR - ITOM - CMDB CI Class Models - 201907
SR - ITOM - Discovery and Service Mapping - v1.0.35
SR - PAR - Performance Analytics Content Pack for Service Portal - v1.0
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - VR - Qualys - New York 2019 Q3
SR - VR - Shodan Exploit - New York 2019 Q3
SR - VR - Solution Management Madrid Q2
SR - VR - Vulnerability Response - New York 2019 Q3
SR - VR - Vulnerability Response PA Content - Madrid 2019 Q2

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-02-04 04:04:23