<?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 vCF 5, edge redeploy, password management failing in VMware Cloud Foundation Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Cloud-Foundation/vCF-5-edge-redeploy-password-management-failing/m-p/2986200#M1474</link>
    <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;Working with vCF 5 and needed to redeploy 2-failed edge nodes previously deployed with vCF/SDDC Manager. Upon remediation of the password, logs are pointing to:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Unable to create jsch CLI session:&lt;BR /&gt;com.jcraft.jsch.JSchException: HostKey has been changed:&lt;/LI&gt;&lt;LI&gt;Could not connect to the SSH server @ xxx&lt;BR /&gt;m.jcraft.jsch.JSchException: HostKey has been changed:&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I've noticed in the operationsmanager.log that the keys are different, as they should be. Though, I cannot find a method to update the KeySpec with vCF/SDDC Manager. Anyone know of a way to update the KeySpec, would this be a postgres edit?&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;I&amp;nbsp;&lt;SPAN&gt;have checked the known_hosts under /home/vcf/.ssh/known_hosts and removed previous key information.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;I have successfully ssh'ed from vCF to the ESG.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Note: This is only for the admin/audit accounts, root shows valid (not disconnected).&lt;/P&gt;</description>
    <pubDate>Mon, 11 Sep 2023 17:40:19 GMT</pubDate>
    <dc:creator>cynack</dc:creator>
    <dc:date>2023-09-11T17:40:19Z</dc:date>
    <item>
      <title>vCF 5, edge redeploy, password management failing</title>
      <link>https://communities.vmware.com/t5/VMware-Cloud-Foundation/vCF-5-edge-redeploy-password-management-failing/m-p/2986200#M1474</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;Working with vCF 5 and needed to redeploy 2-failed edge nodes previously deployed with vCF/SDDC Manager. Upon remediation of the password, logs are pointing to:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Unable to create jsch CLI session:&lt;BR /&gt;com.jcraft.jsch.JSchException: HostKey has been changed:&lt;/LI&gt;&lt;LI&gt;Could not connect to the SSH server @ xxx&lt;BR /&gt;m.jcraft.jsch.JSchException: HostKey has been changed:&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I've noticed in the operationsmanager.log that the keys are different, as they should be. Though, I cannot find a method to update the KeySpec with vCF/SDDC Manager. Anyone know of a way to update the KeySpec, would this be a postgres edit?&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;I&amp;nbsp;&lt;SPAN&gt;have checked the known_hosts under /home/vcf/.ssh/known_hosts and removed previous key information.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;I have successfully ssh'ed from vCF to the ESG.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Note: This is only for the admin/audit accounts, root shows valid (not disconnected).&lt;/P&gt;</description>
      <pubDate>Mon, 11 Sep 2023 17:40:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Cloud-Foundation/vCF-5-edge-redeploy-password-management-failing/m-p/2986200#M1474</guid>
      <dc:creator>cynack</dc:creator>
      <dc:date>2023-09-11T17:40:19Z</dc:date>
    </item>
    <item>
      <title>Re: vCF 5, edge redeploy, password management failing</title>
      <link>https://communities.vmware.com/t5/VMware-Cloud-Foundation/vCF-5-edge-redeploy-password-management-failing/m-p/2986403#M1476</link>
      <description>&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/87542" target="_blank"&gt;https://kb.vmware.com/s/article/87542&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Sep 2023 18:27:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Cloud-Foundation/vCF-5-edge-redeploy-password-management-failing/m-p/2986403#M1476</guid>
      <dc:creator>cynack</dc:creator>
      <dc:date>2023-09-12T18:27:29Z</dc:date>
    </item>
  </channel>
</rss>

