Deleting a plan in EPMC causes all plans' UUID values to shift

Products

• VMware Cloud PKS

Issue/Introduction

Symptoms:

• After deleting a plan in the EPMC UI and re-configuring, all plans' UUID values change and PKS clusters have the wrong plan attached
• The pks clusters command shows that the wrong plans are assigned to PKS clusters after removing a plan that was in the middle of the configuration menu in the EPMC UI or from the yaml config file.

Environment

VMware PKS 1.x

Resolution

​​​​​​This is a known issue affecting EPMC. There is currently no resolution.

Workaround:

• Identify what position/plan number the removed plan was in by looking at the current plan numbers in opsman and UUID using the pks clusters command.
• Export the yaml file of the current EPMC configuration then edit the yaml file with a placeholder plan or the plan information that was removed in the exact plan position that the original was removed from. Plan numbers are assigned starting at plan 1 on the top of the yaml and sequentially moving down each plan should have a predetermined UUID for the plan number.
• After yaml is complete import the yaml in the EPMC UI. Once the plan is in the replaced all cluster plans will be updated and can be verified using the pks clusters command

Additional Information

Impact/Risks:
If changes on previous provisioned clusters are applied after deleting a plan from EPMC manually, there is potential that those PKS cluster plans are going to change to new plans with incorrect resources or config.