Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
In the Events and Notifications view of the Cloud Director Availability Provider Portal, Settings and Events sections are missing and you see an error similar to: Unexpected VMware Cloud Director error. [ UI-240237dd-3a8c-4870-8d95-398c8a6f9218-mH-5dbbbc15-083c-4344-8390-fc21150286ed ] This operation is denied. In the /opt/vmware/h4/cloud/log/cloud.log file on the Cloud Replication Management Appliance, you see entries similar to: 2021-01-27 08:50:32.012 DEBUG - [19cc1d95-a5d1-4439-b4ba-4d8092cc1091] [health-check-5] h.c.s.VcloudSessionHealthCheckingService : Initiating vCD sessions health check. 2021-01-27 08:50:38.139 ERROR - [UI-240237dd-3a8c-4870-8d95-398c8a6f9218-mH] [https-jsse-nio-8443-exec-9] c.v.h.c.c.error.ExceptionAdvisorBase : A GET request from user[IP Address] to /config/notifications/provider failed. com.vmware.vcloud.client.exception.VcloudException: (Major code = 403, minor code = ACCESS_TO_RESOURCE_IS_FORBIDDEN) - [ UI-240237dd-3a8c-4870-8d95-398c8a6f9218-mH-5dbbbc15-083c-4344-8390-fc21150286ed ] This operation is denied. at com.vmware.vcloud.client.VcloudClient.lambda$defaultErrorDeserializer$0(VcloudClient.java:247) at com.vmware.rest.client.AbstractRestClient.convert(AbstractRestClient.java:225) at com.vmware.vcloud.client.XmlRestClient.exchange(XmlRestClient.java:92) ... In the /opt/vmware/vcloud-director/logs/vcloud-container-debug.log file on the Cloud Director cell, you see entries similar to: 2021-01-27 10:50:38,122 | DEBUG | pool-jetty-289322 | CSecurityManager | Building security context for user [loginUserId = 156ec36f-a3ce-4cfa-bae2-ec2d312504bb, operatingOrgId = a93c9db9-7471-3192-8d09-a8f7eeda85f9, isSystemAdministrator = true, canSwitchOrgContext= true] | requestId=UI-240237dd-3a8c-4870-8d95-398c8a6f9218-mH-5dbbbc15-083c-4344-8390-fc21150286ed,request=GET https://vcd_address/api/admin/user/ff079561-2630-495d-ab49-310a6e0076b1/grantedRights,requestTime=1611737438099,remoteAddress=10.204.98.47:48638,userAgent=Apache-HttpClient/4.5.13 (Java/11.0.9),accept=application/*+xml;version 31.02021-01-27 10:50:38,130 | DEBUG | pool-jetty-289322 | CSecurityManager | Access attempted for disabled userid = 156ec36f-a3ce-4cfa-bae2-ec2d312504bb. | requestId=UI-240237dd-3a8c-4870-8d95-398c8a6f9218-mH-5dbbbc15-083c-4344-8390-fc21150286ed,request=GET https://vcd_address/api/admin/user/ff079561-2630-495d-ab49-310a6e0076b1/grantedRights,requestTime=1611737438099,remoteAddress=<VCDA_IP>:48638,userAgent=Apache-HttpClient/4.5.13 (Java/11.0.9),accept=application/*+xml;version 31.0 Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
This issue can occur when you have configured Cloud Director email notifications in Cloud Director Availability and there are disabled System Administrator users in Cloud Director.When Cloud Director email notifications are enabled, Cloud Director Availability attempts to retrieve the email addresses for all Cloud Director System Administrator users. When there are disabled System Administrator users present, Cloud Director Availability is unable to retrieve their email addresses resulting in this behaviour.
This issue is resolved in Cloud Director Availability 4.2, available at VMware Downloads.
To work around this issue if you do not want to upgrade, enable all System Administrator users in Cloud Director.