Failed to Load Vmware Vsphere Content Pack From Marketplace Please Try Again Later

VMware vRealize Orchestrator 8.6.2 | 18 Jan 2022

Cheque for additions and updates to these release notes.

Release Versions

VMware vRealize Orchestrator eight.6.ii | 18 January 2022 vRealize Orchestrator viii.6.2 Appliance build 19108182 VRealize Orchestrator 8.vi.2 Update Repository build 19108182

Updates made to this certificate:

Appointment	Description of update	Blazon
01/18/2022	Initial publishing.
03/02/2022	Added link to KB workaround used to resolve upgrade failure related to the log4j vulnerabilities.

Of import

Log4J vulnerabilities

The Apache Log4j utility is now updated to version 2.17 to resolve CVE-2021-44228 and CVE-2021-45046. For more information on these vulnerabilities and their affect on VMware products, please see VMSA-2021-0028.

Upgrade failure subsequently performing steps in KB 87120

Performing the instructions used to address the CVE-2021-44228 and CVE-2021-45046 log4j vulnerabilities described in KB 87120 tin can cause upgrade failures for vRealize Automation and vRealize Orchestrator viii.half dozen.two or earlier. For a workaround, meet KB 87794.

What's New in vRealize Orchestrator eight.half-dozen.2

• The vRealize Log Insight content pack for vRealize Orchestrator v8.3+ is at present bachelor.

  The VMware vRealize Orchestrator content pack compliments the vSphere content pack and provides a consolidated summary of log events beyond all vRealize Orchestrator components in the environs. The vRealize Orchestrator content pack for Log Insight provides you lot with important information beyond all components of your vRealize Orchestrator 8.iii+ environment.

  The content pack enables:

  • Proactive monitoring of your vRealize Orchestrator viii.3+ environment.
  • Server overview dashboards.
  • Authorization related details.
  • Configuration and content audit dashboards.
  • Workflow related dashboards that include information on failures, logs, and statistics.
  • Metrics dashboards that include Residual API logs and JVM log details.
  • Request-based tracing across vRealize Orchestrator eight.x services using trace IDs.
  • Troubleshooting and aid during root-cause analysis.

  The vRealize Log Insight content pack can be constitute in the VMware Marketplace.

  NOTE: This version of the content pack is now bachelor and is designed specifically for vRealize Orchestrator 8.3 and above. Information technology is non compatible with earlier versions of vRealize Orchestrator.

• Plug-in API compatibility updates for VUM (VMware vSphere Update Managing director) plug-in (update to latest vSphere APIs).

  In previous versions, the VUM plug-in supported only the vSphere 6.five API. Now the VUM plug-in is updated to support vSphere versions vi.7, 7.0, seven.0 U1, and 7.0 U2 (with backwards compatibility to 6.0 on vCenter 6.7). With the VUM plug-in, you can perform the following tasks:

  • Upgrade and patch ESXi hosts.
  • Install and update third-party software on hosts.
  • Upgrade virtual machine hardware and VMware Tools.

  The assortment of SDK objects in the plug-in is changed to exist a multi value picker. However, the action used in vRealize Automation forms is not supported by vRealize Orchestrator.

  For more data on the VUM plug-in, see Using the vRealize Orchestrator Plug-In for VMware vSphere Update Manager.

• Changes to cluster health and synchronization condition monitoring.

  In previous releases of vRealize Orchestrator, you could monitor the health and synchronization status of your cluster from the Orchestrator Cluster Management and Validate Configuration pages of the Command Center. You can no longer use these pages to monitor the status of your cluster.

  The new recommended approach for monitoring the health and synchronization status of your cluster is to log in to the vRealize Orchestrator Client and navigate to the System tab of the dashboard. Alternatively, if the vRealize Orchestrator Client is unavailable, you tin can also check the status of your cluster by running the kubectl become pods -n prelude control from the vRealize Orchestrator Apparatus control line.

Deploying the vRealize Orchestrator Appliance

The vRealize Orchestrator Appliance is a VMware Photon Bone-based appliance distributed as an OVA file. It is prebuilt and preconfigured with an internal PostgreSQL database, and it tin can be deployed with vCenter Server six.0 or later.

The vRealize Orchestrator Appliance is a fast, easy to utilize, and more affordable way to integrate the VMware deject stack, including vRealize Automation and vCenter Server, with your IT processes and environs.

For instructions nigh deploying the vRealize Orchestrator Appliance, see Download and Deploy the vRealize Orchestrator Appliance.

For information about configuring the vRealize Orchestrator Appliance server, run into Configuring a Standalone vRealize Orchestrator Server.

Upgrading and Migrating vRealize Orchestrator

You can upgrade a standalone or clustered vRealize Orchestrator 8.x deployment to the latest production version by using a mounted ISO prototype.

For more information about upgrading the vRealize Orchestrator Appliance, meet Upgrading vRealize Orchestrator.

You can migrate a standalone vRealize Orchestrator case authenticated with vSphere or vRealize Automation to vRealize Orchestrator 8.6.ii. Product versions of vRealize Orchestrator seven.x supported for migration include versions 7.three to 7.vi. The migration of amassed vRealize Orchestrator 7.x deployments is non supported.

For more information nearly migrating the vRealize Orchestrator Appliance, meet Migrating vRealize Orchestrator.

Plug-ins Installed with vRealize Orchestrator 8.6.ii

The following plug-ins are installed by default with vRealize Orchestrator viii.6.2:

• vRealize Orchestrator vCenter Server Plug-In vii.0.0
• vRealize Orchestrator Post Plug-In 8.0.one
• vRealize Orchestrator SQL Plug-In 1.1.9
• vRealize Orchestrator SSH Plug-In 7.three.0
• vRealize Orchestrator SOAP Plug-In 2.0.6
• vRealize Orchestrator HTTP-REST Plug-In 2.4.1
• vRealize Orchestrator Plug-In for Microsoft Active Directory 3.0.xi
• vRealize Orchestrator AMQP Plug-In i.0.6
• vRealize Orchestrator SNMP Plug-In 1.0.three
• vRealize Orchestrator PowerShell Plug-In ane.0.xx
• vRealize Orchestrator Multi-Node Plug-In 8.vi.2
• vRealize Orchestrator Dynamic Types 1.3.half-dozen
• vRealize Orchestrator vCloud Suite API (vAPI) Plug-In seven.5.2
• VMware vSphere Update Manager Plug-in 7.0.0

Before Releases of vRealize Orchestrator

Resolved Problems

• Changes to the status codes from the Content Service.

  For the Residual API workflow service you wait the 409 lawmaking but receive a 202 Accustomed:nil code instead. The following API changes are applied to the Content Service:

  Service name	Content Service
  API version	All versions
  External or Internal facing API	External
  Change description	Changes to the API status code.
  Changes between the current release and previous releases	The success code is changed from 200 to 202.

• After upgrading from vRealize Orchestrator 8.4.0 to vRealize Orchestrator eight.5.1, you lot are unable to load the vRealize Orchestrator Client when you are logged in as a not-default tenant, simply yous tin can log in every bit a default tenant.

  A subtenant is unable to use the embedded vRealize Orchestrator Client in vRealize Automation even if the client is registered as an integration for that specific vRealize Automation tenant. When attempting to log in to the vRealize Orchestrator Client, subtenants receive the post-obit mistake bulletin: O, Unknown error.

• Users cannot browse the vRealize Orchestrator inventory tree if the domain name contains the api string.

  When the domain name contains the api string, users receive an error when they try to scan the inventory tree. This issue is caused past asking existence fabricated to a broken URL.

• In vRealize Automation, the vro-amanuensis container is unable to create a dump file for the 2nd time if the file already exists.

  When a dump file is created it cannot exist overwritten when needed.

• The ResourceElement#reload() scripting API does not reload the bodily content from the database.

  vRealize Orchestrator provides a ResourceElement#reload() scripting API that allows scripting content authors to retrieve the latest version of the resources element content from the database in cases where the content of the resources element is updated independently. This can include scenarios, such as the content being updated by some other workflow or activity running in parallel with the current object. This issue causes the scripting API to go on the old content instead of retrieving the updated content, which tin can cause various errors in any inventory objects that utilize the specific resource element.

• Unable to move a workflow to another folder.

  Changing the current folder of a workflow from the editor view in the vRealize Orchestrator Client leads to a merge conflict when attempting to save the workflow.

• The API Explorer incorrectly displays array types.

  Scripting object methods, which render array types, are displayed every bit returning simple non-array types. This outcome can be encountered, for case, in the getRESTAuthentications method used by the RESTAuthenticationManager object included in the Balance plug-in. In this example case, the method returns a String array but is displayed as a simple String. The same issue is encountered for method parameters of the assortment blazon. For case, the createAuthentication method of the same scripting object has a parameter named params. The parameter is a String array, merely the API Explorer displays it equally a simple String. The issue is also encountered in properties and attributes. For instance, RESTAuthentication#rawAuthProperties is a Cord assortment but it is also displayed equally a simple String. This result tin can also be encountered in plug-ins other than the REST plug-in.

Known Issues

• The following error message is displayed above the workflow input grade when using the RUN AGAIN functionality to start a new workflow run: Some information cannot be retrieved. If the trouble persists, contact your system administrator.;.

  The value of an input field of the uncomplicated assortment type of non object types such equally Array/number or Array/cord is wrongly evaluated and passed to an external source action that is used to populate the value of another input form field.

  Workaround: Employ the RUN workflow functionality instead of RUN Again.

• Pushing commits to a protected Git branch fails.

  If the configured Git co-operative is protected, the push operation fails consistently, but the message that appears indicates that the push button is successful.

  Workaround: The decision was taken not to set this issue in the current or upcoming releases of vRealize Orchestrator. This known issue entry is going to be deleted from the release notes for the next release.

• Local changes are non bachelor after duplicating and deleting a workflow.

  Y'all duplicate a workflow and and so delete it. In the Git History page, there is no local modify for the deleted workflow.

  No workaround.

• The interaction form for resuming a failed workflow does not display fields for all defined variables when one of the variables is of the Backdrop type. Inputs for variables coming after the variable of the Propertiestype will be hidden. The input fields of the Properties type are non populated.

  The variable blazon was not interpreted for the Backdrop type which causes problems during form rendering. The type is now used while generating the input form.

  No workaround.

• The VMware Update Director (VUM) plug-in has compatibility issues with vCenter vii.0 U3.

  The Export compliance report workflow is not usable considering of a VUM plug-in backend security outcome in vCenter vii.0.3 (builds 18700403 and 18778458).

  No workaround.

Previously Known Problems

This section contains previously known issues (known bug remaining from earlier releases of vRealize Orchestrator that still be in the product).

• During the installation of a plug-in in the vRealize Orchestrator Command Center, an mistake message appears.

  When you lot install a plug-in from the Manage Plug-Ins page in Command Eye, the following error bulletin appears: Plug-in 'name_of_the_plug-in' (plug-in_file_name) is not compatible with the electric current platform version. Supported platform versions are 'names_of_the_supported_versions'. Clicking on the 'Install' button will install it anyway.

  Workaround: Y'all tin can safely ignore this error and proceed with the installation of the plug-in.

• The vRealize Orchestrator authentication configuration might become invalid if the hallmark provider certificate changes or regenerates.

  When the SSL document of the vRealize Automation or vSphere instance that is configured as the authentication provider in Command Middle is changed or regenerated, the vRealize Orchestrator hallmark configuration becomes invalid, and the vRealize Orchestrator server cannot kickoff.

  Workaround: Import the new authentication provider certificate:

  1. Log in to Control Center every bit root.
  2. Click Certificates.
  3. Click the Import on the Trusted Certificates tab.
  4. Load the SSL certificate from a URL or a file.
  5. Click Import.

• The Lather plug-in cannot connect through an authenticated proxy server.

  When attempting to run the Add a Lather host workflow, y'all come across an issue with the proxy server hallmark.

  Workaround: When running the workflow, use a proxy server that does not crave authentication.

• If yous experience issues connecting to a SOAP or a REST host, or importing a document, you lot might accept to explicitly enable certain versions of SSL or TLS.

• The SSH plug-in encounters firewall connectivity bug.

  The SSH plug-in cannot connect to a Cisco Adaptive Security Appliance (ASA) firewall.

  Workaround: The SSH plug-in for vRealize Orchestrator 7.one does non support connectivity to a Cisco Adaptive Security Appliance (ASA) firewall.

• Problems handling non-ASCII characters in certain contexts.

  Using non-ASCII characters in input parameters results in wrong behavior in the following situations:

  • If you run the SCP put or SCP go workflows from the SSH folder on a file with a name that contains non-ASCII characters, the workflow runs merely the name of the resulting file on the destination machine is unreadable.
  • If you lot endeavour to insert not-ASCII characters into variable names, the characters practice not appear. This issue occurs for workflow variables and action variables.

  No workaround.

• The Storage VSAN workflows of the vCenter Server plug-in practise not support calculation Solid-State Drive (SSD) disks to an ESXi host.

  The Add disks to disk grouping and Remove disks from disk groups workflows practice not support adding SSD disks as capacity disks to ESXi hosts.

  No workaround.

• The RESTOperation ID does not initialize properly if the Residuum host instance is created by using a Swagger spec.

  In the HTTP-Rest plug-in, when the Balance host instance is created by a Swagger spec, the RESTOperation ID does non initialize properly and the getOperation method of the RESTHost object does not piece of work.

  No workaround.

• Adding values to vCenter Server information object backdrop of the Assortment blazon is not possible.

  When vRealize Orchestrator runs scripts, the vCenter Server plug-in converts JavaScript arrays to Java arrays of a stock-still size. As a result, you cannot add new values to vCenter Server data objects that take arrays as property values. You tin create an object that takes an assortment as a holding if you instantiate that object by passing it a pre-filled array. Withal, subsequently y'all instantiate the object, you cannot add together values to the assortment.

  For example, the following code does not work:

                    var spec = new VcVirtualMachineConfigSpec(); spec.deviceChange = []; spec.deviceChange[0] = new VcVirtualDeviceConfigSpec(); System.log(spec.deviceChange[0]);                

  In the to a higher place code, vRealize Orchestrator converts the empty spec.deviceChange JavaScript array into the fixed-size Java array VirtualDeviceConfigSpec[] before it calls setDeviceChange(). When calling spec.deviceChange[0] = new VcVirtualDeviceConfigSpec(), vRealize Orchestrator calls getDeviceChange() and the array remains a fixed, empty Java array. Calling southpec.deviceChange.add() results in the same beliefs.

  Workaround: Declare the assortment as a local variable:

                    var spec = new VcVirtualMachineConfigSpec(); var deviceSpec = []; deviceSpec[0] = new VcVirtualDeviceConfigSpec(); spec.deviceChange = deviceSpec; Organization.log(spec.deviceChange[0]);                

petersonhempring.blogspot.com

Source: https://docs.vmware.com/en/vRealize-Orchestrator/8.6.2/rn/vmware-vrealize-orchestrator-862-release-notes/index.html

Share this post