Group - Image Association overrides other group image
-
Hi all,
I have version 1.5.7 installed and its working fine for me if I make single deployments to each host. But always to change the image to each host is inkonvenient so I tested with groups.
For different trainings I created for my 16 laptops two groups with all 16 hosts, only difference is the name of the group and the image file (other fields are blank in the create group settings).
If I associate to the
GroupA the Group Image: ImageA (4)
and assign to
GroupB the Group Image : ImageB (5)
the Image in GroupA is set to ImageB too.I found in the wiki with modus “last saved”, but actually it makes no sense to me, if the groups are not independent from each other?
My goal would be, to click on “List All Groups” to the deploy button in the specific row and that’s it.
Any ideas or is there a configuration to change this?
Thanks in advance.
Stefan -
@stefan said in Group - Image Association overrides other group image:
I created for my 16 laptops two groups with all 16 hosts, only difference is the name of the group and the image file (other fields are blank in the create group settings).
That is expected behavior. Actions performed on a group act on all hosts that are members of that group at that time. If all 16 machines are in both group A and group B, any action performed on either group will affect all 16 machines. Can you explain what behavior you are wanting to see?
-
Hi Daniel,
thanks for your reply.
The applying to the hosts works, but the second group image is overwriting the image association of the first group.My procedure:
- Create a Group (GroupNameA) with all 16 hosts
- Assign to this Group ImageA (4)
- Create a second Group (GroupNameB) with all 16 hosts
- Assign to this second Group ImageB (5)
If I click on “List all Groups” and than on GroupNameA, the Image of the second Group is assigned to the first Group too.
I made quickly a test of 2 hosts and made some screenshots
Do I made something wrong?
Thanks!
-
@stefan FOG does not have persistent settings as you might expect. Groups are more or less a tool to push settings to a group of hosts instead of manually setting for each individually.
-
@Sebastian-Roth
Thank you Sebastian for your reply.Sorry for bugging you, but this setting is not clear to me.
Why is the image assignment of a second group influencing the first group?This makes no sense to me. And regarding persistent settings, the setting of one group with an image assigned is persistent isn’t it?
Thanks.
Stefan -
@stefan said in Group - Image Association overrides other group image:
And regarding persistent settings, the setting of one group with an image assigned is persistent isn’t it?
No, group settings are not persistent in FOG. The settings are only pushed to the host objects but never stored for the group object. Search the forum for persistent groups and read about it. There is a topic on how to manually add this feature to FOG but not officially supported.
I will try to replicate your example of two groups.
-
@stefan said in Group - Image Association overrides other group image:
Why is the image assignment of a second group influencing the first group?
Now I see what you mean. What you see here is that the image selected in the Image Association tab is pre-selected from the last time you used it. It might look like groupA has imageB set but it really isn’t because FOG doesn’t have persistent groups. Read about it in the forums.
-
As @Sebastian-Roth has suggested, by default groups in fog are nothing more than a means to apply settings to multiple hosts at once.
So taking your example, if you apply image a in group a and refresh the page, you will see group a maintains image a as it’s set.
If you then go to group b and it contains all the same hosts as in group a, then apply group b image to image b, it will have set image b to all hosts in group a. So if you go back to group a, it will show image b as being set.
The way these fields are displayed, if all hosts in the group have the same image defined, it will display that image as being selected.
Groups in fog were not designed to be persistent.this is why you can associate a host to multiple groups at the same time.
