Server roles R and O are not taken over correctly after primary fails

book

Article ID: 87645

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION

Issue/Introduction

Error Message :
N/A

Server Role R and O not taken over after stop of PWP.

Scenario / reproduction:
 
1. Run a System with at least 4 WPs
2. Check via System Overview which one is the primary and which one have roles R and O. The roles should be on different WPs.

<Please see attached file for image>

0EMb0000001QOli.png
3. Kill the Primary WP process (e.g. via Task Manager)
4. Wait until you can refresh System Overview.
5. Primary is greyed out now
6. Another on is Primary but also R and O. And these roles stay at this WP "forever"

<Please see attached file for image>

0EMb0000001QOlx.png
7. Start the former primary again
8. As soon it runs, it receives role R, O stays at the current primary

<Please see attached file for image>

0EMb0000001QOm2.png

Cause

Cause type:
Defect
Root Cause: Error in code.

Environment

Release: AUTWAB99000-11.0-Automic Workload Automation-Base Edition
Component:

Resolution

This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.

Fix Version(s):
AE Server and Initialdata 11.2.2 of Automation.Engine - already available
AE Server and Initialdata 12 of Automation.Engine - already available

Additional Information

Workaround :
N/A

Attachments

1558692591129000087645_sktwi1f5rjvs16lrs.png get_app
1558692589436000087645_sktwi1f5rjvs16lrr.png get_app
1558692586480000087645_sktwi1f5rjvs16lrq.png get_app