Description of problem: Repeated entries in evm.log with WARN of "Forbidden to read the project:" Version-Release number of selected component (if applicable): 5.9.0.22 How reproducible: everytime at Cu environment Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Hi Nikhil, That's great, thanks guys.This only occurs when there are no stacks in the environment anywhere. Having even a single one works around that problem. I'll test and follow-up for back-port.
Hi Gilles, Could you supply steps to verify this bug Thanks
Hi Jadh, The customer is facing warnings when CloudForms Inventory is trying to access Orchestration stacks. And assuming there are no tasks (the default for the overcloud) which makes "openstack stack list" CLI return with an empty list. From CloudForm just register against an OSP instance using default admin user and monitor the evm.log file for the warning messages containing: "WARN -- : MIQ(OpenstackHandle::OrchestrationDelegate#handled_list) Forbidden to read the project: admin, for collection type: stacks, in provider:" Please let me know if you need more details. Regards
(In reply to Gilles Dubreuil from comment #18) > Hi Jadh, > > The customer is facing warnings when CloudForms Inventory is trying to > access Orchestration stacks. And assuming there are no tasks (the default > for the overcloud) which makes "openstack stack list" CLI return with an > empty list. > > From CloudForm just register against an OSP instance using default admin > user and monitor the evm.log file for the warning messages containing: > > "WARN -- : MIQ(OpenstackHandle::OrchestrationDelegate#handled_list) > Forbidden to read the project: admin, for collection type: stacks, in > provider:" > > Please let me know if you need more details. > > Regards Thnaks a lot, that was helpful
Verified on 5.10.0.28
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:0212