CloudPlatform fails to add new hosts to existing cluster after upgrading from 4.5.1 to 4.7

Problem

 

CloudPlatform fails to add new hosts to existing cluster after upgrading from 4.5.1 to 4.7

Steps to Reproduce the problem

  1. Upgrade ACP deployment having version 4.5.1 with ESXi cluster to ACP 4.7
  2. Add a new host to the existing ESXi cluster using ACP.
  3. ACP fails to add the host

Root Cause

While adding host, Cloud Platform is trying to get the guest and public vswitch types from the addHost API parameters (which are null) instead of fetching them from the cluster details in database.

Required Modification

Fetch the guest and public vswitch types from the cluster details in database rather than addHost API call paramters

Reason for Modification

Admin should be able to add a new host to existing ESXi cluster by design, but it was failing due to a defect in CloudPlatform. 

Resolution/Workaround

 

ACP code has been fixed to fetch the guest and public vswitch types from the cluster details in database.

Verification

  1. Upgrade ACP deployment having version 4.5.1 with ESXi cluster to ACP 4.7
  2. Add a new host to the existing ESXi cluster using ACP.
  3. ACP successfully adds the host.

Impact on Existing System

Fixes the ACP code to ensure that an ESXi host can be added to a cluster created in an older version of ACP.

 

Potential Adverse Effect

 

There is no known adverse effect on the system.

Document ID:
214442366

Product:
CloudPlatform

Version:
4.7

Reference Jira ID:
CS-47601

 
Have more questions? Submit a request

Comments