VCSA Upgrade from 6.5 to 6.7U2c failed at "Starting VMWare vSphere Server"

[JuergenBischof]

Hello,

I try to upgrade our VCSA to the current version but get an error during the migration Step when the new VCSA is starting the services.

The source VCSA has the version: 6.5.0.30100 and I use the image VMware-VCSA-all-6.7.0-14070457.iso.

After the successfull deployment the migration step starts without errors when collection all the data of the source system.

But when the new applicance starts the services I got the error at 60 %.

Ein interner Fehler ist aufgetreten. Traceback (most recent call last): File "/usr/lib/vmware-content-library/firstboot/content-library-firstboot.py", line 219, in Main vdc_fb.register_cis() File "/usr/lib/vmware-content-library/firstboot/content-library-firstboot.py", line 77, in register_cis self._reg_info.registerAll(self.get_soluser_id(), self.get_soluser_ownerId()) File "/usr/lib/vmware-content-library/install_lib/cis_register.py", line 368, in registerAll self.registerUserAndService(user_name, user_id, service) File "/usr/lib/vmware-content-library/install_lib/cis_register.py", line 395, in registerUserAndService add_vmtx_privileges(self.vdc_cfg_dir) File "/usr/lib/vmware-content-library/install_lib/add_vmtx_privileges_after_fb.py", line 105, in add_vmtx_privileges log("Adding privileges [%s] to role %s" % (' '.join(VMTX_SYNC_PRIVILEGES), cls_admin_role.name)) AttributeError: 'NoneType' object has no attribute 'name'

I searched for the error message but did not find a solution.

Can you have a look at the attached logs, please?

Maybe someone will have an idea and can help me to solve the upgrade problem.

Thanks for your help.

Let me know, if you need any more information.

Regards

Jürgen

[MartinGustafsso · Accepted solution]

Hi Jürgen,

This issue occurs when 'Content library administrator' role is missing on the source vCenter server.

The process to fix this is to manually add/change the content library admin id Role using jExplorer on the vCenter.

It's a bit tricky. I would suggest you open a service request so GSS can help you resolve this.

-----------------------------------------

Was it helpful? Let us know by completing this short survey here.

[JuergenBischof]

Hi Martin,

thanks a lot for your help.

I created the missing role and the migration worked fine.

Regards

Jürgen

[mr_bib]

Hi Jürgen,

We are seeing this exact same issue.

Can you advise how you created the missing role? Did you use jXplorer as sugested by Martin, or just create it by hand in vCenter?

Many thanks,

David

[mr_bib]

For anyone else who stumbles upon this thread, here is the solution that worked for us.

Before proceeding, a warning to make sure that you have backups of your VCSA/PSC platforms before proceeding!

As mentioned above, the reason for the error is that the default "Content library administrators (sample)" role seems to be required to complete the upgrade. If this role has been removed the upgrade will fail.

To rectify this, create a new role in vCenter, call it anything you like ("CLAdmin Temp") for example, and add all Content Library permissions to the role.

Then, you will need an LDAP editor (jXplorer is mentioned above and there is a post here to get connected with it: https://www.virtuallyghetto.com/2015/05/vcenter-server-6-0-tidbits-part-7-connecting-to-ssopsc-using...)

Once connected to your PSC (embedded or external) navigate to Services > VmwAuthz > RoleModel and expand. You will see a list of nodes with numbers, one for each role in your vCenter. Select the first of these and find the "vmwAuthzRoleName" attribute in the table on the right. Skip through each role until you find the new role you just created above.

Once you have found your new role, edit the vmwAuthzRoleName attribute for it to read exactly "com.vmware.Content.Admin". Once modified, you are done with your LDAP editor.

Finally, reboot your VCSA (and PSC if External). When you log back in to vCenter navigate to the Role definitions and your new role should now be called "Content library administrator (sample)"

Your upgrade will now work!

If in doubt with any of the above, obviously get in touch with VMware support. Hopefully the above will help someone stumbling upon this though.