Bug 1928704
| Summary: | Host deploy events does not have proper correlation-id | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Martin Necas <mnecas> |
| Component: | ovirt-host-deploy-ansible | Assignee: | Dana <delfassy> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavol Brilla <pbrilla> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.4.4.4 | CC: | bugs, mnecas, mperina |
| Target Milestone: | ovirt-4.4.9 | Flags: | pm-rhel:
ovirt-4.4+
|
| Target Release: | 4.4.9 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine-4.4.9 | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-20 08:04:52 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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. correlation-id stays same during whole deployment phase ovirt-engine.noarch 4.4.9.3-0.3.el8ev 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. |
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: