SCS v3.1.48 enforces singleton jobs which may cause IP change and persistent disk deletion
Article ID: 297169
Updated On:
Products
Support Only for Spring
Issue/Introduction
SCS v3.1.48 enforces the spring-cloud-services vm to be recognized as a singleton job. This then enforces the spring-cloud-services vm to use the specified AZ for a singleton jobs, as is defined in the configuration of the tile.
If the spring-cloud-services vm currently is in wrong AZ, during the upgrade the vm will be recreated in singleton-jobs AZ and change the IP address. The persistent disk of the SCS vm will be deleted and the IP address change will break the connection from config-servers and mirror service.
If the spring-cloud-services vm currently is in wrong AZ, during the upgrade the vm will be recreated in singleton-jobs AZ and change the IP address. The persistent disk of the SCS vm will be deleted and the IP address change will break the connection from config-servers and mirror service.
Environment
Product Version: 3.1
Resolution
The tile is removed from Tanzunet.
If you did upgrade to SCS v3.1.48, the issue will only occur if the SCS vm is located in other AZ from what is set in the tile at Singleton jobs AZ.
In other case if the singleton AZ is the same as the AZ where SCS vm is running then there should be no changes.
If you upgraded to SCS v3.1.48 please contact support so we can check the environment.
If you did upgrade to SCS v3.1.48, the issue will only occur if the SCS vm is located in other AZ from what is set in the tile at Singleton jobs AZ.
In other case if the singleton AZ is the same as the AZ where SCS vm is running then there should be no changes.
If you upgraded to SCS v3.1.48 please contact support so we can check the environment.
Feedback
Yes
No
Powered by
