Bug 1510035
| Summary: | [RFE] Nodes tagging : better match nova flavors and ironic profiles in UI | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Ola Pavlenko <opavlenk> | ||||
| Component: | openstack-tripleo-ui | Assignee: | Jiri Tomasek <jtomasek> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Udi Kalifon <ukalifon> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 12.0 (Pike) | CC: | achernet, augol, beth.white, jjoyce, jrist, jschluet, jtomasek, sclewis, slinaber, tvignaud | ||||
| Target Milestone: | Upstream M1 | Keywords: | FutureFeature, Triaged | ||||
| Target Release: | 14.0 (Rocky) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | openstack-tripleo-ui-9.3.1-0.20180909174557.1a18ba7.el7ost | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-01-11 11:48:21 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Note that this is currently expected behaviour. Tagging the node does not explicitly mark the node for deployment. It just means that in case it gets deployed, it is going to be used for a role which profile matches the tagged profile of the node. Nodes are added for deployment by specifying the count on deployment page. This is completely separate step and IMHO it is a good thing -> user does not always want to deploy all the nodes available. Hi Jiri, Can you clarify from your above comment: is this therefore an unwanted feature that should be closed or is there a way to complete this RFE while keeping desired behaviours? Thanks, Beth IMHO this is unwanted feature as, as described above, the nodes tagging and assignment are two separate steps on purpose. Verified. The UI now checks for the roles with the profile that's configured as the flavor of the role (instead of just expecting the flavor name to always be the role name). The only known limitation is that the GUI expects the flavors' profiles to always be the same as the flavors' names. 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-2019:0045 |
Created attachment 1348638 [details] controller flavor Description of problem: Using custom profiles, node that tagged with profile X wan't assigned to a role with the same profile. Role counter wasn't updated. Version-Release number of selected component (if applicable): openstack-tripleo-ui-7.4.2-2.el7ost.noarch How reproducible: always Steps to Reproduce: 1. via UI, create a custom profile 2. tag a node with the custom profile 3. on deployment page, edit a roles flavor to match the custom profile Actual results: roles counter for # of assigned nodes to the role (with matching flavor) is not updated. Expected results: node tagged with the custom profile should be assigned to the role with matching profile. roles counter for # assigned nodes to the role was updated. Additional info: