Skip to content

Failed to push vROps policies which are pulled from another vROps server #898

@stanislav-skkolev-spec

Description

@stanislav-skkolev-spec

Description

The issue is that when policies are exported (pulled) from one vROps server and if the policies are children of "Default Policy" (built-in policy in vROps) and if the "Default Policy" is with different id (99% of the cases) the child policies are not imported in the target vROps server, the API request for importing policy from .zip appears to work (returns 200 status) but the actual response reveals that no policies are neither created nor updated and the rest of the import (push) process fails due to the absence of the policies.

Steps to Reproduce

  1. Create a vROps project in VSCode (with vROps archetype)
  2. Create a policy under the "Default Policy" in one vROps server
  3. Pull with BTVA - mvn vrops:pull -Pprofile
  4. Describe the policy in the content.yaml
  5. Push the content to another vROps server

Preconditions: Policies created under Default Policy

Expected behavior: All policies and their child policies are imported to any vROps server

Actual behavior: The import fails

Reproduces how often: Always

Component/s: Affected components from BTVA: /common/artifact-manager

Affects Build/s: 4.13.0

Environment

  • Build Tools for VMware Aria Version: 4.13.0
  • Visual Studio Code Version: 1.92.2
  • OS Version: all

Dependencies

Run: curl -o- https://raw.githubusercontent.com/vmware/build-tools-for-vmware-aria/main/health.sh | bash and paste the output here:

Server

  • vRealize Operations Version: 8.18.3

Failure Logs

Image

Related issues and PRs

Additional Context

Image

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions