Unable to See/Access “My Services” after a Provisioning Event. Environment: VSphere 5.5U2 Authentication Active Directory Tennant 1 = “QA” Tennant 2 = “Development” Service Name “RHEL 7” Role(s) = VM and Template Access Restriction = NONE Steps: 1. Create a Service Catalog Item – Vmware Provision 2. Verify Provisioning Scope is to All 3. Log-in as a non admin user (e.g. Clouduser1) under Tennant “Development” 4. Log into Services, Launch Service containing RHEL Image. Result: Service Provisions Vmware image. However, when clicking “My Services” as the User “Cloud User1” you are unable to see the service. You can, however, click Infrastructure-VMs and see the VM. User Permissions reflect as CloudUser1, Group=cfgroup2 (Note CFGROUP2 is from Active Directory. This is mapped to Tennant) .
More information: If I create the Service as the intended Tennant User, "My Services" displays the VM. When I create the service under the usual "admin" account; "My services" is not displayed. Is this by design or a bug?
I can confirm that this is an issue in my environment too.
The issue here is that the service was assigned to the root tenant after is was created. The following PR should address this issue: https://github.com/ManageIQ/manageiq/pull/6209
Created attachment 1116173 [details] Hotfix for POCs Copy bz-1297539-service-under-tenant.tar to /var/www/miq/vmdb and unpack from that directory: cd /var/www/miq/vmdb tar -xvf bz-1297539-service-under-tenant.tar Restart EVM
I just reviewed this bug on 5.6.0.7 per some field feedback. Using the same steps I used for the cloud version of this bug, it's not working. Logged in as admin Create new group called QE Create new user called QEUser in group QE Logged out and in as QEUser From Computer\Infrastructure\VM I created a new VM. It showed up fine. However, when I expanded VMs and clicked on VMs | Own, the list was blank. When I do this from Services, I ordered an (azure) catalog item. Got some coffee Went to cloud instances and it showed all of them. Expanded Instances Selected Instances | Own It showed only the new instance I had created. Feel free to use this already configured instance https://10.16.6.106/vm_infra/explorer user qeuser, password qeuser
I want to add that this isn't perhaps entirely the same thing, but it's being blended together in the field, and the fact remains the VM does not contain an owner. I'm open to the possibility of closing this and adding a new issue, but perhaps it's a quick fix.
Here was the 5.5.4 variation of what I think is the same issue. https://bugzilla.redhat.com/show_bug.cgi?id=1318753 Not clear to me what was changed to fix it.
I changed my mind. This issue is closed per the original description. And that VM finally did show up in the list under that owner. My guess is it didn't set the owner until the actual request was verified. I think it's related to tags instead. I'll open a new bz in a bit.
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