-
Notifications
You must be signed in to change notification settings - Fork 171
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
[Customer]Postscripts set in groups don't apply correctly to nodes inheriting postscripts from multiple groups #115
Comments
@samveen You should take a look of the code in table.pm->getNodeAttribs_nosub_returnany() |
Do you know the background that why xCAT group mechanism did not consider to concatenate attributes, but just select one of them? I saw there was code logic to handle the keyword 'NEXTRECORD' which can be used to do the similar thing to append attribute value to another from group, do you know the use case of this feature? |
@daniceexi @jjohnson42 |
Possible design:
|
Hi @samveen , if you set group attribute of I prepare to add a site variable Does this solve your problem ? |
@chenglch , Yes, I think that would solve my problems very well. The design I proposed was just an idea, and I think that your approach to make this a more general design for all attributes is a great improvement to the design I proposed. |
'heirarchicalattrs' is added in site table to apply attributes from multiple groups in order. close-issue xcat2#115
@chenglch Elegantly done. @daniceexi This can be closed at your convenience. |
👍 nice |
Postscript definitions for relevant groups:
Relevant node fields:
Changing the post scripts:
Relevant postscripts after changes to group:
Change back to old config:
Expected value is that the postscripts for all the node's groups should be applied to the node in the groups' order, not just the first group with poscripts.
This problem may apply to other fields which should combine values from multiple groups, and may be a consequence of fields that must not be overridden (as in, later groups shouldn't be able to override prior values, set by higher priority/earlier groups).
NOTE: Due to the nature of the problem, this may actually be a feature request instead of a bug report. I'm investigating the code to see if I can figure out a solution.
The text was updated successfully, but these errors were encountered: