Description of problem: The RedHat domain /Infrastructure/VM/Provisioning/Placement/redhat_best_placement_with_scope method does not use the RBACed eligible methods which can cause an error when setting the storage(prov.set_storage) if the storage is not available using the RBAC filter. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Setting storage results in log message "not an eligible resource for this provisioning instance" Expected results: Selected storage should be RBAC enabled. Additional info:
This ticket opened as a result of discussions here: https://bugzilla.redhat.com/show_bug.cgi?id=1684472
Automate methods are not RBAC enabled by default. The Redhat domain vmware_best_placement_with_scope placement method iterates through the hosts and storages and could potentially select a host and/or storage that is not available due to RBAC filtering. The method does a prov.set_storage on the selected storage, and an error is issued if the storage is not eligible due to the RBAC filtering. The workaround is to enable/disable RBAC in the placement method as shown in this example: https://github.com/ManageIQ/manageiq-content/issues/297#issuecomment-389914285
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition. If it's something like a tracker bug where it doesn't matter, please set the severity to Low.
Based on comment #3 should this ticket be closed "working as designed" and/or converted into an RFE?
Hi Dennis, Converting the ticket to an RFE. Thanks, Tina
Thank you Jaroslav for working with Patrik to validate this issue.