I am trying to update the VCSA from 6.5 to 6.5 U2b.

To begin, I took a snapshot of the current VCSA.

I uploaded the patch ISO (VMware-vCenter-Server-Appliance-6.5.0.21000-8815520-patch-FP) to the local ESXi Datastore and attached it to the VCSA CD.

I logged into the vCenter Appliance and attempted the update and it failed.

I reverted back the snapshot and tried again using the method of logging into the appliance and using the software-packages utility.

It looks good until the end and I see the following:

ISO unmounted successfully

Running test transaction

Running pre-install script

Al VMware services stopped

Upgrading software packages

Package update failed

Starting all services

Installation failed

I rebooted the VCSA but cannot login, get a 503 service unavailable

I reverted back to the snapshot and can login to the 6.5.41000 version of VCSA

Any ideas as to what I should try next for an attempted upgrade?

Hi all,

I have a VCSA 6.5 VM in which I have set up AD authentication from an external AD server.

The upgrade instructions are pretty clear but I want to find out if my AD authentication would still work after the new VCSA 6.7 is deployed?

Anyone had experience in this?

Thanks

Hello community,

I trying to install from cero (I was a problem updating) vCenter v6.7 last release (9232925) but, in the second stage at 60% crash with the message:

Error: VMware VirtualCenter failed firstboot. The instalation of vCenter Server failed due to an internal error.

Resolution: Please serach for these symptoms in the VMware Knowledge.....

I try to retry, but the error still there...

Error: A problem ocurred during setup. Services might not be working as expected.

I was download the logs....But I don't undertand the logs.... are attached in this post... please can some one help me?

PS. I trying to install without DNS Server with a static IP address.

Hi All,

We currently have 5 servers, 1 * management server and 4 * production servers (physical hosts) running 33 vms. We alsouse VDP and Site recovery. We are going to be purchasing a new managements server and 4 * replacement physical hosts. We will also be upgrading from VMware version 5.5 - 6.5. Storage is on Equalogic SAN.

What is the best way to approach/ accomplish this. Will we need extra licences during the upgrade? Is it better to upgrade or install a fresh. If a fresh install how do we move our existing vms?

Thankyou for your help.

Kind Regards,

Paul

We have 15 ESXihosts, and we are on the process of upgrading hosts to 6.5. One host does not give me an option to upgrade. The installer boots and detects the SD card, if I query the SD card using F1 for details it detected 5.5 installed, but when I select the SD card it goes straight to the language selection for installing ESXI, No upgrade option.

I verified the bootbank and altboot bank both have same number of files/data. Is there a possibility to findout what causing the issue without reinsatalling the host?

Thanks in advance...

Hello.

I have a big doubt. On vsphere products What is the difference between version and releases? what is a major and minor version?

- Vcenter 5.0, 6.0 are versions or major versions? 5.1, 5.5, 5.8, 6.5 and 6.7 are releases or minor versions?

-By example, to use vsphere replication with two sites, I have read "To replicate between vCenters, vSphere Replication requires the same major version (eg. 5.5.x > 5.5.x) of vCenter and vSphere Replication at both source and target.", so my doubt is; do I need vcenter 6.0 on both sites? or can be vcenter 6.0 and vcenter 6.5? and to vsphere replication should be 6.1.2 on both sites or 6.1.1 and 6.1.2, or 8.1 on both sites??

I hope your support.

Thank you.

Problem:

1. booting a 6.5 image and selecting to upgrade does not list the SATA-Bootdevice for installation

2. putting a 6.5 image into a datastore and upgrading via esxcli software profile upgrade -d ... -p ... works as intended

2a. first restart after upgrade is successful - works as intended

every next restart starts the esxi 5.5 again

...and i can upgrade this "old" 5.5 back to the 6.5 until the next but one reboot

Host is in the current state: 5.5 -> upgrade via esxcli -> 6.5 -> upgrade via esxcli -> 6.5U2 -> restart -> keep it running, dont touch it.

Boot device is an "ATP IG SATA DOM"

esxcli storage core device list:

t10.ATA_____ATP_IG_SATA_DOM_________________________99001130903030000004

on a 

lspci -v | grep "Class 0106" -B 1

0000:00:1f.2 SATA controller Mass storage controller: Intel Corporation Patsburg 6 Port SATA AHCI Controller [vmhba0]

esxcli storage filesystem list:  missing the device and datastore

bootbank points to /tmp

no altbootbank

Why is the device available at the first restart but not on any other restart?

Which logfile is recommended to look at?

What command gives clues?

Any chance to get it running again?

Thanks in advance!

Hi everyone, I would check if this is the best way to upgrade one environment 5.5 (VC Windows) to 6.7 (VCSA).

1- upgrade VC Win 55 to VCSA 60 using VCS60 migration tool

2- upgrade ESX 55 to ESX 60

3- upgrade VCSA60 to VCSA 67

4- upgrade ESX60 to ESX67

*maybe it is better to change WINVC to VCSA during step3 insthead of step1?

thank you all

have they released beta for vsphere 6.7 u1?

Hi All,

We have recently purchased 5 HP ProLiant G10 DL380 servers. One of which we intend to use for the vcenter appliance and the other 4 for vsphere 6.5 physical hosts. Each server will have two hard drives mirrored. Can I use the in built RAID controller / software to setup the raid config and the appliance/vsphere will recognise this, or do I need ti use another utility? (I have read online that if using the microserver you have to use the marvel utility otherwise esxi wont recognise the raid setup)

Sorry for the newbie question.

Kind Regards,

Paul

Hi,

Our current setup has 4 vCenters 5.5 (Windows), 2 VMs running SSO role on Windows and 1 VM running the WebClient on Windows. We will be upgrading this month (finally) and we're moving to the vCenter appliance. Desired config will be two appliances running PSC / SSO and the four vCenters will be appliances running just vCenter. We have no longer need for a separate web client.

Now the big question: When and how in the upgrade path do I remove the webclient VM? Is that after the last vCenter Server has been upgraded? How do I remove it properly, just a normal uninstall?

when entering the username and password vmware vsphere client connects but after 20 seconds it is disconnected and one of the errors sent to me is the following call "EventManager.CreateCollector" for the object "EventManager" in vCenter Server.

also when I want to connect again this dialog box appears

thank you, you can help me.

Hi,

During update to ESXi 6.5, I have a warning about a possible compatibility issue with my processor (Intel(R) Xeon(R) CPU X5450). I cancelled the update. It works fine right now with ESXi 6.0. Is there really a risk to make the update ? Is there a temporary issue or the compatibility with the process has been removed ?

Hello everyone,

***If this is for some reason, not the correct place/forum to start such a thread, I would be glad if you could point me somewhere where this fits in better***

I am working now for about a year in my company and I am responsable for a our virtualization environment which was created by my predecessor. I am currently thinking about updating everything to 6.7 and may need some opinions on that. Before asking questions I want to share some information about the environment:

We currently have two Clusters consisting of 1 vCenter Server Appliance running on a host of the cluster and 3 ESXI-Hosts in each cluster. Everything is on Version 6.0.0. Additionally we have 3 stand-alone ESXIs on Version 6.5.0. But as they are standalone, I am not that concerned about updating them.

All in all our environment looks sime kind of like this:

All of the ESXIs have local storage attached to a RAID Controller and Running in RAID 10. In fact, here is an image of the Hardware used:

From me research this hardware is actually not supported by VMWare, at least I did not find everything on https://www.vmware.com/resources/compatibility/search.php?deviceCategory=io&details=1&partner=221&releases=369,408,367,338,276,275,274,273&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc. CPU seems fine, RAID Controller is definitely not supported by VMWare. I was not able to find a list of supported Mainboards, RAM and HDDs. Whats not on the image is the SSD which holds the ESXI OS.

Regarding network access, each Host has 4 1GB NICs, 3 of them are in our development network and 1 is in a management network which consists of a RIS/WDS-Server to get some images. I am currently not sure if the 3 NICs are some kind of teamed/trunked, the config says "Load Balancing by Port-ID"?:

Besides the Hardware and ESXI Versions there are the two vCenter Server Appliances and one Platform Service Controller running as VMs on the Hosts. I think the two vCSAs are running in "Link Mode" as I can see them both when loggin into the webinterface of one of them:

Also, what is probably notable, we have a Single-Sign-On running using our company domain.

Now, what I would like to do is:

• First, update the first vCenter to 6.7. As I read on https://www.vladan.fr/upgrading-vcsa-6-5-to-6-7/ this can be done by just installing a new 6.7 vCSA and during the wizard it will copy the config.
  • My questions here are if I need to need something special as I have these two vCSAs in "Link mode" and if I still need the PSC afterwards (I think I read somewhere that it is not needed anymore in 6.7)
• After that I want to update the second one
• If that is succesfull, I want to upgrade one ESXI host after another. As we are cheap and dont have vMotion, I have to shut down the VMs for that.
  • My question here is if it would be better to try to install 6.7 ontop of 6.0 or, my currently prefered Idea, to install 6.7 to a fresh SSD and switching them out?
  • I know that I have to integrate the driver for our RAID-Controller into the ESXI Image. I have that done once before with 6.5 and assume that it will work similar with 6.7. But are there any other things that I probably have to think about?
• If the update process is done, I would like to think about some minor stuff like the NIC Teaming/Trunking and if it is good as it is or if I can enhance it.
  • Any suggestions here?
  • Also I would be glad for some other suggestions of "nice to have" features I should configure

Some minor information I want to mention: All of our Hosts are some kind of a Lab-Environment for our Development, so there is no VM that has to run 24/7 or which is production critical. I can shutdown any VM and the worst thing that happens is that 1 or 2 devs are complaining that they cant test their code. Also I have only about 10% of my worktime availiable for tasks regarding the virtualization environment. I know it could be in a better state but I was busy getting warm with my job first.

If there are any questions or suggestions I am will try to answer them asap. Also I can provide any more information anyone needs (as long as they are not confidential).

So far, thanks in advance,

Niklas

i will migrate from vcenter 5.5 to 6.5 . some user using web client console for vm. after 6.5 user will use HTML5, but i wonder that how can I check if their computers support html5 before upgrading

I want to upgrade my vmware infrastructure 5.5 to 6.5 so I need a excel document . how to make the steps I'll show my boss. upgrade documents like excel

i asked this question but want to ask agin because i didnt understand sorry. my questions is that i want to upgarde/migrate my vcenter 6.0 to 6.5 but i have nsx, vsphere replication and VMware vCenter plug-in ( emc , etc.. ) How to upgrade the process. first time and then which one to do. what information do I need in such a process ? I have read some documents, but it only writes vcenter and esxi, for example when I vcenter and esxi to upgarde nsx will continue to work or plug-ins will be a problem. couldn't understand them. Is there a certain order of operations and how can I do . thanks for helping

i get this message when i try to download VMware Fusion 10.0.0 (for Intel-based Macs)

i'm from egypt

Your download request has been received and is under review for download eligibility.

Confirm that you provided a valid first name, last name, address, and country when you registered. If you did not, update your My VMware profile and try to download again.

If you do not receive an update after 3 business days, please try again.

Contact us if you have any questions. Quote Message ID 621 and provide the email address you used when registering.

Thank you,

VMware Customer Service

Hi, we plan to upgrade the current ESXi 5.5 3b to 6.5 U1 as the 5.5 going to end for the support this month. Our current host is HP Proliant DL380P Gen 8 connected to the HP P2000 storage. After checked in the VMware compatibility guide, it shows that HP P2000 storage is not support for upgrade. Anyone here try to upgrade to 6.0 or 6.5 without issue before?

Hi all,

trying to upgrade external PSC from 6.0.0.20000 to 6.5 U2, the new appliance is deployed, but then the upgrade process fails during the pre-upgrade check.

using cli-installer:

Precheck error: 1. Title: Internal error occurs during pre-upgrade checks.

Precheck error: 1. Suggested Resolution: Please search for these symptoms in the

VMware Knowledge Base for any known issues and possible resolutions. If none can

be found, collect a support bundle and open a support request.

Failed normalizing ip: psc04.vlab.local

(u'Failed to uninstall %(rpm)s on %(host)s: %(error)s', {'host':

u'psc04.vlab.local', 'rpm': u'vmware-upgrade-requirements-*', 'error':

CommandError(u"Failed to run and wait for command in guest with error 'Command

'/bin/rpm' exited with non-zero status 1'",)})

Collecting support bundle from source VM psc04.vlab.local ...

Failed normalizing ip: psc04.vlab.local

Collecting the support bundle from the deployed appliance...

Got error while running OVF Tool command: Errors encountered during the precheck

process. Correct the errors and provide a new appliance name in the template,

because you must deploy a new appliance.

using gui-installer:

Checked /var/log/vmware/upgrade on the source and see a bunch of sso errors and not a lot of other clues. Any idea how to overcome this issue?

/var/log/vmware/upgrade/requirements-upgrade-runner.log

...

2018-09-26T17:41:48.945Z ERROR bindings.sso_binding Cannot log-in to SSO admin service, because of Error: (vmodl.fault.InvalidRequest) {

   dynamicType = <unset>,

   dynamicProperty = (vmodl.DynamicProperty) [],

   msg = "Request version 'urn:sso/version3_5' and namespace 'urn:sso' are not supported",

   faultCause = <unset>,

   faultMessage = (vmodl.LocalizableMessage) []

}.

Traceback (most recent call last):

  File "/var/tmp/vmware-upgrade-requirements/cis-upgrade-runner/py/bindings/sso_binding.py", line 138, in createSession

    content = si.RetrieveServiceContent()

  File "/var/tmp/vmware-upgrade-requirements/cis-upgrade-runner/libs/pyVmomi.zip/pyVmomi/VmomiSupport.py", line 557, in <lambda>

    self.f(*(self.args + (obj,) + args), **kwargs)

  File "/var/tmp/vmware-upgrade-requirements/cis-upgrade-runner/libs/pyVmomi.zip/pyVmomi/VmomiSupport.py", line 363, in _InvokeMethod

    return self._stub.InvokeMethod(self, info, args)

  File "/var/tmp/vmware-upgrade-requirements/cis-upgrade-runner/libs/pyVmomi.zip/pyVmomi/SoapAdapter.py", line 1338, in InvokeMethod

    raise obj # pylint: disable-msg=E0702

vmodl.fault.InvalidRequest: (vmodl.fault.InvalidRequest) {

   dynamicType = <unset>,

   dynamicProperty = (vmodl.DynamicProperty) [],

   msg = "Request version 'urn:sso/version3_5' and namespace 'urn:sso' are not supported",

   faultCause = <unset>,

   faultMessage = (vmodl.LocalizableMessage) []

}

2018-09-26T17:41:48.948Z WARNING bindings.sso_binding Could not retrieve service instance from SSO component using API version 'sso.version.version3_5'. Falling back to API version 'sso.version.version1'.

...

Other errors and warnings from requirements-upgrade-runner.log that might be relevant.

psc04:/var/log/vmware/upgrade # grep -iHE "error|warning" *

requirements-upgrade-runner.log:2018-09-26T17:39:33.286Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:39:33.287Z ERROR utils.featureState_utils Can not get AUTOMATED_VUM_UPGRADE feature state, default will be used

requirements-upgrade-runner.log:ImportError: No module named featureState

requirements-upgrade-runner.log:2018-09-26T17:39:33.302Z ERROR bindings.sso_binding Cannot log-in to SSO admin service, because of Error: (vmodl.fault.InvalidRequest) {

requirements-upgrade-runner.log:2018-09-26T17:39:33.305Z WARNING bindings.sso_binding Could not retrieve service instance from SSO component using API version 'sso.version.version3_5'. Falling back to API version 'sso.version.version1'.

requirements-upgrade-runner.log:2018-09-26T17:39:33.845Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:39:33.860Z ERROR bindings.sso_binding Cannot log-in to SSO admin service, because of Error: (vmodl.fault.InvalidRequest) {

requirements-upgrade-runner.log:2018-09-26T17:39:33.861Z WARNING bindings.sso_binding Could not retrieve service instance from SSO component using API version 'sso.version.version3_5'. Falling back to API version 'sso.version.version1'.

requirements-upgrade-runner.log:2018-09-26T17:39:33.948Z WARNING model.components_metadata Cannot find matching source metadata for provided:platform=Linux, version=6.0 and source-metadata=[{u'export-after': [u'vpxd'], u'platform': [u'Windows'], u'version': [u'5.5'], u'export-from': [u'com.vmware.vpxd']}]

requirements-upgrade-runner.log:2018-09-26T17:39:33.948Z WARNING model.components_metadata Invalid metadata: {u'destination-system': [{u'upgrade-script': u'vco', u'description': u'VMware vCenter Orchestrator component', u'component-display-name': u'VMware vCenter Orchestrator', u'platform': [u'Windows', u'Linux'], u'version': u'6.1', u'component-name': u'vco', u'optional': True}], u'source-system': [{u'export-after': [u'vpxd'], u'platform': [u'Windows'], u'version': [u'5.5'], u'export-from': [u'com.vmware.vpxd']}]}

requirements-upgrade-runner.log:2018-09-26T17:39:33.950Z WARNING model.components_graph Component com.vmware.sso depends on follow components set([u'com.vmware.common_logging', u'com.vmware.rdb']) but the system does not have metadata for them.

requirements-upgrade-runner.log:2018-09-26T17:39:33.951Z WARNING model.components_graph Component com.vmware.vmafd depends on follow components set([u'com.vmware.common_logging', u'com.vmware.rdb']) but the system does not have metadata for them.

requirements-upgrade-runner.log:2018-09-26T17:39:33.958Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:39:33.959Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:39:33.959Z WARNING model.components Component com.vmware.rbd won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:39:33.959Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:39:33.960Z WARNING model.components Component com.vmware.vpxd won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:39:33.960Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:39:33.960Z WARNING model.components Component com.vmware.vcdb won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:39:33.960Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:39:33.961Z WARNING model.components Component com.vmware.eam won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:39:33.961Z WARNING model.components Component com.vmware.ngc won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:39:33.961Z WARNING model.components Component com.vmware.netdump won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:39:33.962Z WARNING model.components Component com.vmware.is won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:39:33.962Z WARNING model.components Component com.vmware.vsan-health won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:39:33.962Z WARNING model.components Component com.vmware.vcIntegrity won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:39:33.962Z WARNING model.components Component com.vmware.sps won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:39:33.963Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:39:33.963Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:39:33.964Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:39:33.964Z WARNING model.components Component com.vmware.cls won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:39:33.977Z ERROR bindings.sso_binding Cannot log-in to SSO admin service, because of Error: (vmodl.fault.InvalidRequest) {

requirements-upgrade-runner.log:2018-09-26T17:39:33.978Z WARNING bindings.sso_binding Could not retrieve service instance from SSO component using API version 'sso.version.version3_5'. Falling back to API version 'sso.version.version1'.

requirements-upgrade-runner.log:2018-09-26T17:39:34.43Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:39:52.466Z WARNING upgrade.states.preupgrade_state vpxd_servicecfg does not exist, assume local storage

requirements-upgrade-runner.log:2018-09-26T17:39:52.466Z WARNING upgrade.states.preupgrade_state vpxd_servicecfg does not exist, assume local storage

requirements-upgrade-runner.log:2018-09-26T17:39:52.638Z WARNING deployer.migration_env_deployer Could not unregister component com.vmware.migrate-connector.127.0.0.1 located on localhost as extension. Exception: -- 'NoneType' object has no attribute 'content'

requirements-upgrade-runner.log:2018-09-26T17:41:33.413Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:41:33.414Z ERROR utils.featureState_utils Can not get AUTOMATED_VUM_UPGRADE feature state, default will be used

requirements-upgrade-runner.log:ImportError: No module named featureState

requirements-upgrade-runner.log:2018-09-26T17:41:33.432Z ERROR bindings.sso_binding Cannot log-in to SSO admin service, because of Error: (vmodl.fault.InvalidRequest) {

requirements-upgrade-runner.log:2018-09-26T17:41:33.435Z WARNING bindings.sso_binding Could not retrieve service instance from SSO component using API version 'sso.version.version3_5'. Falling back to API version 'sso.version.version1'.

requirements-upgrade-runner.log:2018-09-26T17:41:33.685Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:41:33.703Z ERROR bindings.sso_binding Cannot log-in to SSO admin service, because of Error: (vmodl.fault.InvalidRequest) {

requirements-upgrade-runner.log:2018-09-26T17:41:33.705Z WARNING bindings.sso_binding Could not retrieve service instance from SSO component using API version 'sso.version.version3_5'. Falling back to API version 'sso.version.version1'.

requirements-upgrade-runner.log:2018-09-26T17:41:33.797Z WARNING model.components_metadata Cannot find matching source metadata for provided:platform=Linux, version=6.0 and source-metadata=[{u'export-after': [u'vpxd'], u'platform': [u'Windows'], u'version': [u'5.5'], u'export-from': [u'com.vmware.vpxd']}]

requirements-upgrade-runner.log:2018-09-26T17:41:33.798Z WARNING model.components_metadata Invalid metadata: {u'destination-system': [{u'upgrade-script': u'vco', u'description': u'VMware vCenter Orchestrator component', u'component-display-name': u'VMware vCenter Orchestrator', u'platform': [u'Windows', u'Linux'], u'version': u'6.1', u'component-name': u'vco', u'optional': True}], u'source-system': [{u'export-after': [u'vpxd'], u'platform': [u'Windows'], u'version': [u'5.5'], u'export-from': [u'com.vmware.vpxd']}]}

requirements-upgrade-runner.log:2018-09-26T17:41:33.799Z WARNING model.components_graph Component com.vmware.sso depends on follow components set([u'com.vmware.common_logging', u'com.vmware.rdb']) but the system does not have metadata for them.

requirements-upgrade-runner.log:2018-09-26T17:41:33.800Z WARNING model.components_graph Component com.vmware.vmafd depends on follow components set([u'com.vmware.common_logging', u'com.vmware.rdb']) but the system does not have metadata for them.

requirements-upgrade-runner.log:2018-09-26T17:41:33.807Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:41:33.807Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:41:33.808Z WARNING model.components Component com.vmware.rbd won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:41:33.808Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:41:33.808Z WARNING model.components Component com.vmware.vpxd won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:41:33.809Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:41:33.809Z WARNING model.components Component com.vmware.vcdb won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:41:33.809Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:41:33.809Z WARNING model.components Component com.vmware.eam won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:41:33.810Z WARNING model.components Component com.vmware.ngc won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:41:33.810Z WARNING model.components Component com.vmware.netdump won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:41:33.810Z WARNING model.components Component com.vmware.is won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:41:33.810Z WARNING model.components Component com.vmware.vsan-health won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:41:33.811Z WARNING model.components Component com.vmware.vcIntegrity won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:41:33.811Z WARNING model.components Component com.vmware.sps won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:41:33.811Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:41:33.812Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:41:33.812Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:41:33.812Z WARNING model.components Component com.vmware.cls won't be upgraded

requirements-upgrade-runner.log:2018-09-26T17:41:33.825Z ERROR bindings.sso_binding Cannot log-in to SSO admin service, because of Error: (vmodl.fault.InvalidRequest) {

requirements-upgrade-runner.log:2018-09-26T17:41:33.826Z WARNING bindings.sso_binding Could not retrieve service instance from SSO component using API version 'sso.version.version3_5'. Falling back to API version 'sso.version.version1'.

requirements-upgrade-runner.log:2018-09-26T17:41:33.888Z WARNING networking_utils Could not find address info for 127.0.0.1

requirements-upgrade-runner.log:2018-09-26T17:41:47.190Z WARNING upgrade.states.preupgrade_state vpxd_servicecfg does not exist, assume local storage

requirements-upgrade-runner.log:2018-09-26T17:41:47.190Z WARNING upgrade.states.preupgrade_state vpxd_servicecfg does not exist, assume local storage

requirements-upgrade-runner.log:2018-09-26T17:41:47.356Z WARNING deployer.migration_env_deployer Could not unregister component com.vmware.migrate-connector.127.0.0.1 located on localhost as extension. Exception: -- 'NoneType' object has no attribute 'content'

upgrade-linux-requirements.log:2018-09-26T17:39:30.649Z ERROR utils.featureState_utils Can not get AUTOMATED_VUM_UPGRADE feature state, default will be used

upgrade-linux-requirements.log:ImportError: No module named featureState

upgrade-linux-requirements.log:2018-09-26T17:39:54.513Z ERROR bindings.sso_binding Cannot log-in to SSO admin service, because of Error: (vmodl.fault.InvalidRequest) {

upgrade-linux-requirements.log:2018-09-26T17:39:54.527Z WARNING bindings.sso_binding Could not retrieve service instance from SSO component using API version 'sso.version.version3_5'. Falling back to API version 'sso.version.version1'.

upgrade-linux-requirements.log:2018-09-26T17:41:31.706Z ERROR utils.featureState_utils Can not get AUTOMATED_VUM_UPGRADE feature state, default will be used

upgrade-linux-requirements.log:ImportError: No module named featureState

upgrade-linux-requirements.log:2018-09-26T17:41:48.945Z ERROR bindings.sso_binding Cannot log-in to SSO admin service, because of Error: (vmodl.fault.InvalidRequest) {

upgrade-linux-requirements.log:2018-09-26T17:41:48.948Z WARNING bindings.sso_binding Could not retrieve service instance from SSO component using API version 'sso.version.version3_5'. Falling back to API version 'sso.version.version1'.