Replies: 2 comments 3 replies
-
|
vCenter is the system of record/the definitive source of all data. When someone wants to modify the description on a Vm, we send that to vCenter, where it is changed and then propagated to us. Again, they are the system of record. So for a conflict, they win. I understand your request, just trying to highlight the logic in place. Hopefully understanding this will help us figure out a way to implement what you want. @agrare Did I describe this correctly? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I migrated my version from Ivanchuk to Radjabov, and everything worked fine, except that the descriptions I had were replaced by the notes from the VM in vCenter.
The tests I performed are as follows:
1. I created a new VM and added my custom description.

2. When I checked in ManageIQ, it was overwritten with:

3. I went into vCenter, changed the description

5. And I saw that the change was reflected in ManageIQ.

5. I edited the description from ManageIQ

6. But it was not replaced in the vCenter notes.

My concern is that I had maintained those descriptions for a long time, but now I’ve lost them.
Is there any way to prevent the descriptions from being replaced if they are modified from vCenter, and keep them in ManageIQ (as it used to work in Ivanchuk)?
Regards.
Beta Was this translation helpful? Give feedback.
All reactions