Space remains in stopped state after network reconnection

Description

As expected, after network disconnects, the primary Space is suspended, and when network reconnects the primary identifies that another primary Space has been elected, and moves to "stopped" state. The GSM is responsible, through its fault-detection mechanism to shutdown the stopped Space, and thus resolving extra Space instances.

In some circumstances, timing of reconnect and allocation of new instance, causes Space to remain in "stopped" state instead of shutting down

Workaround

None

Acceptance Test

suites: manager, disconnect, service-grid

Assignee

Meron Avigdor

Reporter

Meron Avigdor

Labels

None

Priority

Medium

SalesForce Case ID

None

Fix versions

Commitment Version/s

None

Due date

None

Product

XAP

Edition

Enterprise

Platform

All
Configure