Unbinding and binding the same SG for k8s is failing

[emanoelxavier]

Description

Unbinding and re-biding a Kubernetes is failing due to redundant create of a security group in the appliance manager.

Expected Behavior

Unbinding and re-binding a k8s security group should work consistently.

Actual Behavior

Unbinding and re-binding a k8s security group triggers a synchronization job which is failing with the message "Security group with name xxx already exists"

Steps to Reproduce

1. Create a SG, DA and DS for Kubernetes using the OSC REST Apis.
2. Bind the SG to the VS using the OSC REST Apis. Payload example:

[
	  {
	    "virtualSystemId": 2,
	    "name": "sgbind2",
	    "policyIds": [
	      1
	    ],
	    "order": 0,
	    "markedForDeletion": false,
	    "isBinded": true
	  }
]

3. Unbind the SG from the VS using the OSC UI (or REST APIs).
4. Bind the SG to the VS using the OSC REST Apis.
5. Observe the job failure.

Additional Information

Workaround

Force delete the unbound security group and create a new one with a different name and same member labels. The new one can then be successfully bound.

Environment

• OSC Version/Build: Build:100-g2bfbb51
• Cloud Provider Info: K8s v1.6
• Plugin Info: ISM and NSC plugin.
• Other:

Status

• Reproduced
• In Progress
• Validated => Verified in Version/Build: Version: 1.0.0-SNAPSHOT (Build:122-gcf03e6a, 2017-10-17T18:58:35Z)