Unsolved
4 Posts
0
1780
September 30th, 2021 09:00
VxRail Upgrade from 4.7.531 to 7.0.240 and now to 7.0.241 Issues
I have just completed upgrading my system from 4.7.531 to 7.0.240 and due to vmware newest security advisory I would also like to immediately proceed to upgrade to 7.0.241 but I am running into a issue where after precheck completes and I hit step three which is "Scanning for components. Please wait a moment to view the scan results" the system hangs on that step with 0% progress. Since from what I can find i am not able to find any logs in regards to this issue on any of appliances and I am not able to find any articles about this either. So I am just reaching out to community to see if they ever encounter this issue and if so what do you recommend my next steps be.
No Events found!
DELL-Sam L
Moderator
•
7.5K Posts
0
September 30th, 2021 16:00
Hello Vistul,
Have you tried to reboot the node then tried to do the upgrade again?
Vistul
4 Posts
0
October 1st, 2021 04:00
Hello Sam L,
I did reboot vcenter appliance and vxrail manager appliance. And no dice. I have done further troubleshooting and discovered when I manually ran vxverify script I have been given a warning on each esxi node that states the following.
pconf: No bind entry found in platform.conf. KB Article 000191765.
Test name and Test Aim Detail - pconf | Tests Bind IP in platform.conf compared to node FQDN.
So naturally I went to the kb article and appears the article was just recently created and provided no details on resolving the issue but following the steps i open /etc/config/vxrail/platform.conf on esxi box and got the following
Line 1: [general]: not found
Line 2: log_level: not found
Line 3: log_target: not found
Line 4: listener_type: not found
Line 5: listener_address: not found
Line 7: [backend]: not found
Line 8: max_workers: not found
Line 10: [restservice]: not found
Line 11: bind: not found
I have feeling I would most like likely need to open a support case.
DELL-Sam L
Moderator
•
7.5K Posts
0
October 1st, 2021 08:00
Hello Vistul,
I would agree that at this point you will need to open a support case so that we can see all that is going on and resolve your issue.