<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: NSX-V delete controller stuck at REMOVING in VMware NSX Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-V-delete-controller-stuck-at-REMOVING/m-p/2909227#M14736</link>
    <description>&lt;P&gt;Thanks, that did the trick indeed.&lt;/P&gt;</description>
    <pubDate>Mon, 16 May 2022 11:55:41 GMT</pubDate>
    <dc:creator>ppgdtap</dc:creator>
    <dc:date>2022-05-16T11:55:41Z</dc:date>
    <item>
      <title>NSX-V delete controller stuck at REMOVING</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-V-delete-controller-stuck-at-REMOVING/m-p/2908917#M14727</link>
      <description>&lt;P&gt;I started the task with the&amp;nbsp;forceRemoval option, but it appears to have shutdown the controller VM only and is stuck on REMOVING.&lt;/P&gt;&lt;P&gt;An extract from&amp;nbsp;&lt;A href="https://msx-mgr-ip/api/2.0/vdn/controller" target="_blank"&gt;https://msx-mgr-ip/api/2.0/vdn/controller&lt;/A&gt;:&lt;/P&gt;&lt;P&gt;&amp;lt;status&amp;gt;REMOVING&amp;lt;/status&amp;gt;&lt;BR /&gt;&amp;lt;upgradeStatus&amp;gt;UPGRADED&amp;lt;/upgradeStatus&amp;gt;&lt;BR /&gt;&amp;lt;version&amp;gt;6.3.7073587&amp;lt;/version&amp;gt;&lt;BR /&gt;&amp;lt;upgradeAvailable&amp;gt;false&amp;lt;/upgradeAvailable&amp;gt;&lt;/P&gt;&lt;P&gt;I think the corresponding log entry is this:&lt;/P&gt;&lt;P&gt;"ERROR TaskFrameworkExecutor-3 ControllerRemovalTask:324 - cannot get controller node uuid / remove node from cluster"&lt;/P&gt;&lt;P&gt;any idea how I can bypass this and delete the controller? this is an old test environment where all controllers were showing disconnected and I need to redeploy...&lt;/P&gt;</description>
      <pubDate>Fri, 13 May 2022 13:05:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-V-delete-controller-stuck-at-REMOVING/m-p/2908917#M14727</guid>
      <dc:creator>ppgdtap</dc:creator>
      <dc:date>2022-05-13T13:05:43Z</dc:date>
    </item>
    <item>
      <title>Re: NSX-V delete controller stuck at REMOVING</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-V-delete-controller-stuck-at-REMOVING/m-p/2909042#M14729</link>
      <description>&lt;P&gt;VMware actually updated their docs to show the API call to force a delete recently!&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.4/com.vmware.nsx.troubleshooting.doc/GUID-794D77A1-BB77-4B02-ABB6-3FE2930677B0.html" target="_blank"&gt;https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.4/com.vmware.nsx.troubleshooting.doc/GUID-794D77A1-BB77-4B02-ABB6-3FE2930677B0.html&lt;/A&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;DELETE /2.0/vdn/controller/{controllerId}?forceRemoval=true&lt;/LI-CODE&gt;&lt;P&gt;You were pretty close! Just use the parameter and you should be good to go.&lt;/P&gt;</description>
      <pubDate>Sat, 14 May 2022 15:10:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-V-delete-controller-stuck-at-REMOVING/m-p/2909042#M14729</guid>
      <dc:creator>engyak</dc:creator>
      <dc:date>2022-05-14T15:10:57Z</dc:date>
    </item>
    <item>
      <title>Re: NSX-V delete controller stuck at REMOVING</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-V-delete-controller-stuck-at-REMOVING/m-p/2909227#M14736</link>
      <description>&lt;P&gt;Thanks, that did the trick indeed.&lt;/P&gt;</description>
      <pubDate>Mon, 16 May 2022 11:55:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-V-delete-controller-stuck-at-REMOVING/m-p/2909227#M14736</guid>
      <dc:creator>ppgdtap</dc:creator>
      <dc:date>2022-05-16T11:55:41Z</dc:date>
    </item>
  </channel>
</rss>

