expected behaviour or bug?

Elleni

Renowned Member
Jul 6, 2020
241
25
68
52
I stumbled across the following Problem:

- I had renamed a security Group lets say named: TestBla and had assigned it to some guests. While on Datacenter / Firewall / Security Group it created it with all small - no capital - letters like this: testbla, on the guests that already had assigned this group before renaming, it was still named TestBla.

I spent hours in trying to modify the security group, but my changes were ignored, until I realized that the name was not the correct one. Going to the guest and doubleklicking on the said security rule, I discovered that I only had the name to chose from without capital letter. Once I did chose that one, my changes were not ignored anymore. Further testing revealed theat while renaming with capital letters is ignored on the datacenter while creating or renaming the security group, in the guests which already have assigned said group, while the rename with capital letters is ignored on the datacenter level, it is not ignored on the guests / Firewall windows where one can either add local rules or security groups defined in datacenter / Firewall / SecurityGroups.

Guests:

1762184862602.png

Datacenter / Firewall /SecurityGroups:

1762184953679.png
 
Last edited:
anyone? I mean I searched for the described probem but didnt see a clear answer:
here
 
Last edited:
I stopped using Security Groups because of those kind of little surprises. I don't have enough VMs that share the same firewall rules that need to change semi-regularly and in unison. It's just too easy to make mistakes or move a VM to another cluster or restore an old VM and have the Security Groups not match. It's also hard to find which VM/CT uses which Security Group (using the web GUI).
 
  • Like
Reactions: Elleni