Error when using Capacity Director to plan a host decommission (4378295)

In using Capacity Director to plan a host decommission, error "Host HOSTNAME is already scheduled for decommission" is displayed even though no hosts are listed under the Planned Changes pane.

Click To See Full Image.

Topology objects related to a previously planned host decommission for the same host exist but are not listed in the Planned Changes pane from the Capacity Director dashboard.

WORKAROUND 1

From the Capacity Director dashboard modify the time range to include additional historical data; for example: "This year" or "Last Year".

If the hosts are listed in the Planned Changes pane after the change they can edited or deleted as required.

WORKAROUND 2

Manually remove objects from previously planned host decommissions:

1. Go to the Script Console dashboard and search for object instances of type CapHostRemoval.
2. Select, the ESX host and copy the object ID (uniqueId).
3. The below script can be used to delete the single object; click on "Add" from the "Scripts" tab to run it:

   ts = server["TopologyService"];
   obj1 = ts.getObject("PasteObjectIDHere");
   ts.deleteObject(obj1);

Note: This will not delete the ESX host object but only the object instance for the planned change that has the host in it. When going to the ESX Host dashboard, the host would still be listed.

For more information about deleting objects from the Script Console refer to How to delete objects from Foglight using the Script Console (4288125).