Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Descriptionmxie@redhat.com
2018-12-11 08:44:13 UTC
Can reproduce the problem on rhel7 with below builds:
libvirt-4.5.0-10.el7_6.2.x86_64
qemu-kvm-rhev-2.12.0-19.el7_6.2.x86_64
+++ This bug was initially created as a clone of Bug #1658038 +++
Description of problem:
Can't connect to vCenter6.7 with non-administrator user by virsh
Version-Release number of selected component (if applicable):
libvirt-4.5.0-15.module+el8+2285+e990ac42.x86_64
qemu-kvm-2.12.0-44.module+el8+2259+6d80f0a6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Check virt-v2v manual page about VCenter NON-ADMINISTRATOR ROLE
VCENTER: NON-ADMINISTRATOR ROLE
Instead of using the vCenter Administrator role, you can create a custom non-
administrator role to perform the conversion. You will however need to give
it a minimum set of permissions as follows:
1. Create a custom role in vCenter.
2. Enable (check) the following objects:
Datastore:
- Browse datastore
- Low level file operations
Sessions:
- Validate session
Virtual Machine:
Provisioning:
- Allow disk access
- Allow read-only disk access
- Guest Operating system management by VIX API
2. Create a custom permission role in vsphere 6.7 web client
Log into vsphere client web with administrator account -> open 'Home' interface -> Administrator->select "role" -> click "+" -> select related permission to enable the following objects:
Datastore:
- Browse datastore
- Low level file operations
Sessions:
- Validate session
Virtual Machine:
Provisioning:
- Allow disk access
- Allow read-only disk access
Interaction:
- Guest Operating system management by VIX API
3.Add a new user mxie and set password
3.1 From the Home menu, select Administration
3.2 Under Single Sign On, click Users and Groups,on the Users tab, click Add User.
3.3 Enter a user name and password for the new user.
4. Add the user "mxie" to role of step1
4.1 Go to vcenter's permission option, set role of step1 to the user
5.Use virsh to connect to vCenter6.7 with non-administrator user
# virsh -c vpx://vsphere.local%5cmxie.73.141/data/10.73.75.219/?no_verify=1
Enter vsphere.local\mxie's password for 10.73.73.141:
error: failed to connect to the hypervisor
error: internal error: Could not find datacenter specified in '/data/10.73.75.219/'
Actual results:
As above description
Expected results:
Can connect to vCenter6.7 with non-administrator user by virsh
Additional info:
1.Can connect to vCenter6.7 with administrator user by virsh
2.Can connect to vCenter6.0 with non-administrator user by virsh
3.Can reproduce the problem on rhel7 with below builds:
libvirt-4.5.0-10.el7_6.2.x86_64
qemu-kvm-rhev-2.12.0-19.el7_6.2.x86_64
As discussed in bug 1658038, the issue was the lack of recursive changes of the roles of the newly created user to all the objects in the VMware installation.
Hence, closing as NOTABUG.