Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to select child resource groups in vSphere node template dropdown by fullpath #24507

Closed
axeal opened this issue Dec 10, 2019 · 6 comments
Assignees
Labels
area/ui-for-api internal kind/bug Issues that are defects reported by users or that we know have reached a real release
Milestone

Comments

@axeal
Copy link
Contributor

axeal commented Dec 10, 2019

What kind of request is this (question/bug/enhancement/feature request):

Bug

Steps to reproduce (least amount of steps as possible):

  1. Provision a Rancher v2.3.3 instance with cloud credentials for a vsphere cluster
  2. Add a nested child resource group within vSphere under a top-level resource group
  3. Attempt to add a vSphere node template in the Rancher v2.3.3 UI, and observe you cannot select the nested child resource group by full path, only the name of the resource group is shown. As a result you cannot differentiate multiple resource groups with the same name.

Other details that may be helpful:

In Rancher < v2.3.3 the resource group was a free text field, so a user could configure a nested resource group via the UI with the full path, this is no longer possible in v2.3.3. In v2.3.3, the workaround is to first create the Node Template via the UI, then edit via the API to add the nested child to the resource group path.

Environment information

  • Rancher v2.3.3

gzrancher/rancher#8920

gzrancher/rancher#7460

@axeal axeal added kind/bug Issues that are defects reported by users or that we know have reached a real release area/ui-for-api internal labels Dec 10, 2019
@axeal axeal changed the title Unable to select child resource groups in vSphere node template dropdown Unable to select child resource groups in vSphere node template dropdown by fullpath Dec 10, 2019
@maggieliu maggieliu added this to the v2.4 milestone Jan 20, 2020
@maggieliu maggieliu modified the milestones: v2.4, v2.4.x Feb 10, 2020
@zube zube bot removed the [zube]: Backlog label Mar 26, 2020
@luthermonson
Copy link
Contributor

@axeal some renewed interest in this lately, my test shows a sub resource pool shows up in the drop down just only lists the name and not that it's a sub, see the screen shot of the options in the select where i have luther and luther/testerrrr

https://gyazo.com/43b7e0a12195f99f4976f5e9cdb437ac

Check again if this is an issue or perhaps we can fix UI to show it's a sub or the parent resource pool

@axeal
Copy link
Contributor Author

axeal commented Jul 2, 2020

@luthermonson Agreed, looks like just a UI fix to indicate it is a sub-pool of the parent

@bmdepesa
Copy link
Member

Reproduced in v2.4.5

As @luthermonson stated, the subpools are listed, but the UI does not show the full path.

Screen Shot 2020-07-13 at 2 35 45 PM
Screen Shot 2020-07-13 at 2 35 51 PM

@westlywright
Copy link
Contributor

Available in latest-2.4. latest-2.5 and master incoming.

@bmdepesa
Copy link
Member

rancher/rancher:v2.4-3974-head

  • Create a vsphere node template
  • Subpools have the full path listed in the dropdown

Screen Shot 2020-10-16 at 5 01 13 PM

Leaving open until tested on v2.5/master lines

@bmdepesa
Copy link
Member

master-head 68042fa
v2.5-head 9d38821

  • Create a vsphere node template
  • Subpools have the full path listed in the dropdown

@zube zube bot removed the [zube]: Done label Jan 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ui-for-api internal kind/bug Issues that are defects reported by users or that we know have reached a real release
Projects
None yet
Development

No branches or pull requests

6 participants