Loading...
Loading...
ESXi host added to vCenter with Fully Qualified Hostname (FQDN). example:esxi-01.xxxxx.com New service or Add existing service. When RCM Upgrade is initiated using PowerFlex Manager, PowerFlex Manager sees short ESXi hostname in service which is compared to ESXi hostname in vCenter inventory. PowerFlex Manager cannot match the name, and therefore fails with the following error. Error: /Stage[main]/Asm::Resource_wrapper/Asm::Server_update[rackserver-61krtq2]/Asm::Server_update_esx[server_update_esx]/Esx_maintmode[enable]: Could not evaluate: Could not de termine maintenance mode state: An invalid host name or IP address is entered. Enter the correct host name and IP address. /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/errors.rb:157:in `fail' [delladmin@znardcvxflex01 Job-ed286352-4259-451a-a028-9b366de7a25e-0-0]$ Error: /Stage[main]/Asm::Resource_wrapper/Asm::Server_update[rackserver-61krtq2]/Asm::Server_update_esx[s erver_update_esx]/Esx_maintmode[enable]: Could not evaluate: Could not determine maintenance mode state: An invalid host name or IP address is entered. Enter the correct host nam e and IP address. bash: Error:: command not found it Could not resolve hostname: esxi-01 error: DNS result has no information for esxi-01
1. ESXi hosts are added to vCenter with the Fully Qualified Hostname. 2. PowerFlex Manager sees the short hostname in the service and inventory. The deployment.json file registers the short hostname in the field called esx_hostname. 3. PowerFlex Manager checks vCenter for an exact match to the esx_hostname field, and it cannot find it because vCenter only sees the FQDN. 4. Error appears and the upgrade is stopped.
Option1: Upgrade to the latest PFxM version 3.7 or later releases to have the fix. Option2: In PowerFlex Manager, in the service pane, select the Service > click Remove the service from PowerFlex manager. In PowerFlex Manager, under Setting > Networks > select Network type Hypervisor Management > click Edit . Under DNS Suffix , remove the DNS Suffix > click Save . Rerun inventory and wait until it gets to succeed. Add service back as existing service. Once service is added back and is green, continue with the RCM upgrade.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.