vmwarereqtool does not retain metadata

Description

vmwarereqtool does not retain metadata on provisoned nodes.
If you define metadata on a existing imported VM guest or host node and run vmwarereqtool the user-defined metadata is lost in result from vmwarereqtool.

With provisiond all is fine since

 

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Christian Pape April 6, 2021 at 12:48 PM

I agreed with the reporter that the mentioned behavior is normal and not a bug.

Christian Pape March 22, 2021 at 11:51 AM
Edited

As far as I know, the generated XML-file just contains information from the requisition source, so the VMware vCenter server. The meta-data already added to the nodes is persisted in the database and will not be populated back into the requisition's XML-file. So, after importing the process is basically the same as for requisitions defined in the provisiond-configuration.xml. So, are you just missing the meta-data entries in the XML-file (which is normal behaviour) or is the meta-data deleted on a requisition's XML-file reimport (which should not happen)?

Martin Lärcher March 15, 2021 at 3:22 PM

We use vmwarereqtool with the same vmware connection string configured in provisiond-configuration.xml.

Example:

In the result you can see manual configured services for nodes in requisition and also the modified asset.

But not the manually added meta-data in requisition.

Or has this behaviour fundamentally changed?

we expect somethine like this:

Christian Pape March 12, 2021 at 11:17 AM

Can you please provide an example of how you use vmwarereqtool and how we can reproduce this problem in order to further narrowing the problem?

Not a Bug

Details

Assignee

Reporter

HB Grooming Date

HB Backlog Status

Components

Sprint

Fix versions

Affects versions

Priority

PagerDuty

Created February 23, 2021 at 12:08 PM
Updated April 6, 2021 at 9:36 PM
Resolved April 6, 2021 at 12:48 PM