# Revision history [back]

Hello,

We ran into the exact same problem. I'm not sure if there is an official solution, but this is what I did to get around this problem: It seems that the checkboxes where you select the security group have key/value pairs that are id/name. It saves the id into the template as an integer. However during validation and cluster creation a string value is expected instead, e.g. in the validation function there is a set allowed_values = ("1", "default"), and the validated value is 1 (and 1 != "1").

I looked around the dashboard files and found where this data was saved, and did a small change that seems to have worked. Under /openstack_dashboard/dashboards/project/data_processing/nodegroup_templates/workflows/create.py:113 modify

 security_group_list = [(sg.id, sg.name) for sg in groups]


to

 security_group_list = [(sg.name, sg.name) for sg in groups]


This is just a hack, so if you manage to find a proper solution please share it.

Hello,

We ran into the exact same problem. I'm not sure if there is an official solution, but this is what I did to get around this problem: It seems that the checkboxes where you select the security group have key/value pairs that are id/name. It saves the id into the template as an integer. However during validation and cluster creation a string value is expected instead, e.g. in the validation function there is a set allowed_values = ("1", "default"), and the validated value is 1 (and 1 != "1").

I looked around the dashboard files and found where this data was saved, and did a small change that seems to have worked. Under /openstack_dashboard/dashboards/project/data_processing/nodegroup_templates/workflows/create.py:113 modify

 security_group_list = [(sg.id, sg.name) for sg in groups]


to

 security_group_list = [(sg.name, sg.name) for sg in groups]


This is just a hack, hack (I'm not familiar enough with horizon to properly fix that), so if you manage to find a proper solution please share it.