VMware Cloud Community
gradinka
VMware Employee
VMware Employee

Known issues to consider *before* upgrading to vRA 7.4

Folks-

as vRA 7.4 has been out for more than a month now, few trending issues have surfaced which are of importance to consider when planning your upgrades. Below the current list.
As a general rule, I would suggest to:
- keep an eye on the "known issues" section in release notes which is updated regularly -> vRealize Automation 7.4 Release Notes
- download and follow the upgrade guide - there are changes and refinements to the process as well as many troubleshooting  steps added

- Pre-upgrade:

  • When upgrading vRealize Automation appliances, you might experience failures related to duplicates in the database for the vRealize Orchestrator service.
    This is especially valid if the "Vmware Horizon View" plugin for vRO is present
    Resolution: See knowledge base article 54982.

  • After upgrading to vRealize Automation 7.4, no users can be synced from AD to the embedded IDM, if the 'MaxValRange' property on AD/LDAP side is set to 0 (zero).

        Resolution: Not yet available - contact vmware support.

- Post upgrade:

  • After upgrade, getting "HTTP Status 502 – Bad Gateway” in the UI when accessing Containers tab shows error “
    Resolution: Contact vmware support. (KB being drafted)

Tags (1)
11 Replies
daphnissov
Immortal
Immortal

Do you know if any of these known issues are also relevant to new installs of 7.4? If so, could you point them out?

Reply
0 Kudos
daphnissov
Immortal
Immortal

Another known issue to point out in vRA 7.4:

js-io-rights.conf resets to factory defaults after a restart of Control Center. This is not observed in earlier versions and will wipe out any changes made after a restart of the service (or the appliance). Issue has been logged in SR 18809267105.

daphnissov
Immortal
Immortal

It seems this is a known "issue" or, rather, design decision. Here's the response from support on how to work around it:

In vRO 7.4 there are changes in regards to the way the configuration synchronization is done. Configuration changes done through the control center are going to be "permanent" and going to be replicated to the other nodes as well. Changes done manually like through editing a file by a test editor are going to be overwritten with the latest configuration.
Therefore if you make manual changes like editing the js-io-rights file you need to execute the following cli command to apply the changes to the latest configuration which going to be replicated.
you should do the following

  1. stop the control center
  2. make manual changes
  3. execute /var/lib/vco/tools/configuration-cli/bin/vro-configure.sh sync-local
  4. start control center
Reply
0 Kudos
EStacey87
Contributor
Contributor

Just a note from our recent jump to 7.4, but this probably applies to any version until Microsoft gets this fixed.

- System Center Operations Manager 2016 (or build 1801 still so far)  has a bug with some .Net applications via IIS (so all of the IaaS servers)  and the APM portion of SCOM.  Here is some info in regards to this bug and how it affect SharePoint SCOM 2016 APM Linked to IIS Application Pool Failures. - MrChiyo.com   it was first reported to just be an issue with .Net 2.0 sites but like the link shows can also occur with v4.0.

    As far as i have seen, the SCOM agent just causes errors during the upgrade (sorry i forgot to save the logs before snapping back the install attempt) so  you can either try with the NOAPM flag set to 1 like the post above says,  or in my case we have just removed SCOM for the time being from our IaaS servers.

oh and also i had to revert our default tenant for vRO back to vsphere.local or vRO wouldn't start after the upgrade of the appliances.  Then just set it back after the upgrade was complete.

Reply
0 Kudos
ishaarora3
Enthusiast
Enthusiast

I am facing this issue on a new install on vra 7.4

I went over the response you mentioned from the support team. What manual changes do we need to make? Could you please elaborate.

Thanks!

Reply
0 Kudos
daphnissov
Immortal
Immortal

What are you asking about? js-io-rights.conf file updates?

Reply
0 Kudos
ishaarora3
Enthusiast
Enthusiast

I read this response from you above,

you should do the following

  1. stop the control center
  2. make manual changes
  3. execute /var/lib/vco/tools/configuration-cli/bin/vro-configure.sh sync-local
  4. start control center

What manual changes do we need to make here?

I am seeing bad gateway error in Containers tab with a new install of vRA 7.4

Correct me if this response was not for the same issue.

Thanks

Reply
0 Kudos
daphnissov
Immortal
Immortal

That is not related to the issue you're mentioning.

Reply
0 Kudos
ishaarora3
Enthusiast
Enthusiast

thanks. I was going with this line mentioned in the very first message of this discussion,

  • After upgrade, getting "HTTP Status 502 – Bad Gateway” in the UI when accessing Containers tab shows error “
    Resolution: Contact vmware support. (KB being drafted)

I am trying to reach out to support as well if they can help here. Please let me know if you know any solution to this error.

Thanks

Reply
0 Kudos
daphnissov
Immortal
Immortal

I think it's best if you open a separate thread and state your problem. This one is more informative as to the outstanding issues in 7.4.

Reply
0 Kudos