Description of problem: Unable to set template group ownership to "No Group" Version-Release number of selected component (if applicable): cfme-5.5.0.13-2.el7cf.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install a CFME 5.5 in VMware vsphere 5.5 2. Set the ownership to "No Group" Actual results: The ownership doesn't change, but remain "Tenant [My Company] Access" Expected results: The ownership should be set to "No Group" Additional info: CFME 3.2 version doesn't encounter this problem. (There is no group called Tenant My Company Access )
Looked into this issue, it seems that removing group ownership is not working for all entities. UI code seems to be sending up correct values (in this case nil to remove assigned group for a VM) to model method set_ownership in app/models/mixins/ownership_mixin.rb. Tried following commands in UI to verify that group is not getting cleared out for a VM, these commands might be helpful to write a spec test to recreate the issue: vm = Vm.first vm.miq_group.name vm.miq_group=nil vm.save vm.miq_group.name Let me know if more info on this is needed. ~Harpreet
This will not work. A vm has to have both a group and tenant owner. If there is not group, then it will just assigned the tenant's default group. Since there are no users in the tenant's default group, there will be no changes to access. What are you trying to do? Why do you want no group?
Given: We need to fix the ui and remove "Set group to no group". But what I want to know is why the customer wants to set it to no group? What are they hoping to achieve? I'm hoping we can understand this and potentially update the UI to fix any confusion that we are causing the customers.
*** Bug 1303507 has been marked as a duplicate of this bug. ***
This has been on master since before 5.6 was cut. To test, you will notice that there should not be a "set group to nil" for a vm anymore.
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/RHBA-2016:1348
closed and shipped. clearing the need info