Description of problem: Wrong message appers after not permitted action is done. Version-Release number of selected component (if applicable): sf17 How reproducible: always Steps to Reproduce: 1. Set DC to enforced mode. 2. Create quota with RAM limit to 512MB. 3. Create vmpool with vms with 1024MB RAM. 4. Add user UserRole to vmpool. 5. Login as user. And allocate vm from pool. Actual results: Error while executing action: portaluser2.eng.brq.redhat.com: Cannot ${action} ${type}. Quota has no sufficient cluster resources Expected results: Error while executing action: portaluser2.eng.brq.redhat.com: Cannot allocate vm. Quota has no sufficient cluster resources Additional info: String "Cannot ${action} ${type}." Also appears when user is trying to allocate vm from pool which has not quota assigned in enforced mode. And this message is also return via API.
This bug was fixed and is slated to be in the upcoming version. As we are focusing our testing at this phase on severe bugs, this bug was closed without going through its verification step. If you think this bug should be verified by QE, please set its severity to high and move it back to ON_QA
Verified is11. When user try to allocate vm from pool which has not quota assinged, msg is: * Cannot allocate and run VM from VM-Pool. Quota is not valid. When user try to allocate vm from pool which has not enough resources, msg is: * Cannot allocate and run VM from VM-Pool. Quota has no sufficient cluster resources.
Closing - RHEV 3.3 Released