Cluster fails to create intermittently

[xlight05]

Description:
Message - Operation is not allowed: Another operation (nodepool1 - Creating) is in progress
https://github.com/ballerina-platform/ballerina-performance-cloud/actions/runs/1798592862
https://github.com/ballerina-platform/ballerina-performance-cloud/runs/5062754269?check_suite_focus=true

We need to look into this and see if we can fix this issue from ourend.

Steps to reproduce:

Affected Versions:

OS, DB, other environment details and versions:

Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

[dilanSachi]

Noticed the following as well in Create Cluster step.

WARNING: SSH key files '/home/runner/.ssh/id_rsa' and '/home/runner/.ssh/id_rsa.pub' have been generated under ~/.ssh to allow SSH access to the VM. If using machines without permanent storage like Azure Cloud Shell without an attached file share, back up your keys to a safe location
ERROR: (PropertyChangeNotAllowed) Changing property 'linuxProfile.ssh.publicKeys.keyData' is not allowed.
Code: PropertyChangeNotAllowed
Message: Changing property 'linuxProfile.ssh.publicKeys.keyData' is not allowed.
Target: linuxProfile.ssh.publicKeys.keyData

[xlight05]

Noticed the following as well in Create Cluster step.

WARNING: SSH key files '/home/runner/.ssh/id_rsa' and '/home/runner/.ssh/id_rsa.pub' have been generated under ~/.ssh to allow SSH access to the VM. If using machines without permanent storage like Azure Cloud Shell without an attached file share, back up your keys to a safe location
ERROR: (PropertyChangeNotAllowed) Changing property 'linuxProfile.ssh.publicKeys.keyData' is not allowed.
Code: PropertyChangeNotAllowed
Message: Changing property 'linuxProfile.ssh.publicKeys.keyData' is not allowed.
Target: linuxProfile.ssh.publicKeys.keyData

I've observed this happens when you already have a cluster running with the same name. If you want multiple runs for one stdlibs, you might need to append somekind of unique id for the cluster name.

The main issue is different

[dilanSachi]

Noticed the following as well in Create Cluster step.

WARNING: SSH key files '/home/runner/.ssh/id_rsa' and '/home/runner/.ssh/id_rsa.pub' have been generated under ~/.ssh to allow SSH access to the VM. If using machines without permanent storage like Azure Cloud Shell without an attached file share, back up your keys to a safe location
ERROR: (PropertyChangeNotAllowed) Changing property 'linuxProfile.ssh.publicKeys.keyData' is not allowed.
Code: PropertyChangeNotAllowed
Message: Changing property 'linuxProfile.ssh.publicKeys.keyData' is not allowed.
Target: linuxProfile.ssh.publicKeys.keyData

I've observed this happens when you already have a cluster running with the same name. If you want multiple runs for one stdlibs, you might need to append somekind of unique id for the cluster name.

The main issue is different

In stdlib case, we append the module name to each of the cluster names. So the name is unique. And only 1 load test runs at one time for 1 stdlib.