Question

2
Replies
41
Views
Li Li (LiL95470)
W&W

W&W
US
LiL95470 Member since 2015 15 posts
W&W
Posted: January 28, 2021
Last activity: January 29, 2021
Posted: 28 Jan 2021 11:55 EST
Last activity: 29 Jan 2021 4:11 EST

Pega Deployment Manager Access Group doesnot exist in QA because it's name has been changed

Hi, we have this senario.

the Application XY-010101 has been deployed on QA System via the Pipeline XY-010101 with this AccessGroup: XY:Administrators, it pointes

And now we will use a dedicated Access Group for Deployment Manager, i.e. XY:DeploymentManager, it pointes also XY-010101, then we updated the Pipeline XY-010101 with this new access Group, but during diagnose we got this error: the Access Group does not exist on QA. 

i understood this error, the access Group does not exist on QA. But i wonder, why will DM force this Access Group be avaiable on all candidate systems?

And if we deploy a brand-new application, the access group is also not on QA. But in this case the diagnose is successful.

Anyway, does some have an idea, how could we solve this issue.

Pega Platform 8.4.1 DevOps