Created attachment 1569529 [details] vmware_name_screenshot Description of problem: VMware providers, are saved under names, that are too long. When they are picked from the list of the remembered providers, their name cannot be fully viewed (see attached screenshot) Version-Release number of selected component (if applicable): hco_tag: v.2.0.0-12 How reproducible: 100% Expected results: Save VMware providers under a shorter name, that can be fully seen in the UI.
This identifies the vcenter. We could either - show a tooltip with the full name - add option to name the vcenters with a custom name when saving the secret
The best option here is in new field with predefined value but allowing the user to provide whatever name (s)he likes. That can be seen as a new feature and we are in bug-fixing phase now. So to fix, I propose no aditional changes to the UI but generate the name differently: The name is no longer than 35 letters. Composed as: [USERNAME]-[URL]-[UNIQUE] where USERNAME - prefix of VMware username - up to 15 letters before '@' (shortened if needed) URL - prefix of VMware URL, up to "30 - USERNAME.length" characters UNIQUE - 5 auto generated characters
+1, sounds good
Patch: https://github.com/kubevirt/web-ui-components/pull/530
Since the v2v has been removed from 2.1.0, retargeting bugs to 2.1.1 to make sure they will be verified on the right version.
Moving to ON_QA.
please add fixed in version
The change was merged on Jul 30
Created attachment 1643860 [details] Screenshot (fixed) Verified as fixed in version: CNV 2.2.0-10 vCenter instance is identified as described in comment #2: The name is no longer than 35 letters. Composed as: [USERNAME]-[URL]-[UNIQUE] where USERNAME - prefix of VMware username - up to 15 letters before '@' (shortened if needed) URL - prefix of VMware URL, up to "30 - USERNAME.length" characters UNIQUE - 5 auto generated characters
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/RHEA-2020:0307