Bug 1928704 - Host deploy events does not have proper correlation-id
Summary: Host deploy events does not have proper correlation-id
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: ovirt-host-deploy-ansible
Version: 4.4.4.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.4.9
: 4.4.9
Assignee: Dana
QA Contact: Pavol Brilla
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-15 12:17 UTC by Martin Necas
Modified: 2021-11-20 08:04 UTC (History)
3 users (show)

Fixed In Version: ovirt-engine-4.4.9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-20 08:04:52 UTC
oVirt Team: Infra
Embargoed:
pm-rhel: ovirt-4.4+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 116166 0 master MERGED engine: correlation id that was passed via API is set for all host deploy events 2021-09-07 14:06:06 UTC
oVirt gerrit 116686 0 ovirt-engine-4.4 MERGED engine: correlation id that was passed via API is set for all host deploy events 2021-09-14 10:39:01 UTC

Description Martin Necas 2021-02-15 12:17:06 UTC
Description of problem:
Hi,
when forcing the correlation-id from API and running the host deploy the created events do not have the same correlation id which was passed.
This does not happen every time for example host upgrade, removal looked fine but I was able to find it on host deploy maybe more have the same issue. 

Version-Release number of selected component (if applicable):


How reproducible:

Probably the easiest way to reproduce it is by running the ansible-playbook with a correlation-id example:
```
- hosts: localhost
  tasks:
    - name: Login to oVirt
      ovirt.ovirt.ovirt_auth:
        url: "URL"
        username: "admin@internal"
        password: "PASS"
        headers:
          correlation-id: "test2"
    - ovirt.ovirt.ovirt_host:
        auth: "{{ ovirt_auth }}"
        cluster: Default
        name: vhost
        address: address
        password: pass
        state: present
```

Steps to Reproduce:
1. Run the playbook specified above.
2. Checkout the event logs in advanced view so you can see the correlation-id
3.

Actual results:
Few logs do have correct but those around host deploy do have a different id.

Expected results:
The logs should have the same ID.

Additional info:

Comment 2 Dana 2021-07-20 13:22:49 UTC
After investigating, the different correlation ids are created for different commands:
The first correlation id is a part of 'AddVdsCommand', whereas the other is a part of 'InstallVdsInternalCommand' parameters.
This is the same behavior when installing a host via the webadmin, screenshots attached.

Comment 4 Pavol Brilla 2021-10-27 09:56:02 UTC
correlation-id stays same during whole deployment phase

ovirt-engine.noarch                                            4.4.9.3-0.3.el8ev

Comment 5 Sandro Bonazzola 2021-11-20 08:04:52 UTC
This bugzilla is included in oVirt 4.4.9 release, published on October 20th 2021.

Since the problem described in this bug report should be resolved in oVirt 4.4.9 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.