Open mann1mal opened 5 years ago
This is a known bug in PKS. Resize operations wipe out compute_profile metadata off the cluster. As a result CSE never gets the name of the compute profile on subsequent GET calls. Without this information CSE won't be able to determine on which org vdc the cluster is residing and hence no info on console either.
@rocknes This was fixed in PKS 1.4.1 release. But the change for that is the CSE needs to use new PKS api end point to resize the cluster. I don't know if changes were made by CSE for the same
After some additional testing stemming from issue #377 , I've found another issue when attempting to resize an Enterprise CSE cluster post provisioning.
Environment: vCD 9.7 PKS 1.4.0 NSX-T 2.4.1
Logged in as the org admin for my
cse-enterprise-org
, which is enabled for Enterprise CSE cluster creation and list the available OvDCs and clusters:No clusters have been provisioned in the OvDC, so I'll provision one and list it after the create is finished:
Cluster is available and tagged with the
cse-enterprise-org
org and thecse-ent-ovdc
virutal datacenter as expected. However, because of issue #377 , I need to resize my cluster to add a 3rd node as the cluster did not provision according to the PKS plan definition:When I go to view the status, no clusters are shown:
I'll log into the vcd as the
administrator
user and list clusters:The
scale-test
cluster is shown but with noorg
orvdc
designation. This means my users that need to access information about this cluster in thecse-enterprise-org
are no longer able to see the cluster after it has been resized.Please let me know if you require any additional logs/information.