Bug 2142601
| Summary: | Cluster upgrade role fails on wrong correlation_id | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Barbora Dolezalova <bdolezal> |
| Component: | ovirt-ansible-collection | Assignee: | Martin Necas <mnecas> |
| Status: | CLOSED ERRATA | QA Contact: | Barbora Dolezalova <bdolezal> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.5.3 | CC: | emarcus, mavital, michal.skrivanek, mnecas, mperina |
| Target Milestone: | ovirt-4.5.3-async | Keywords: | AutomationBlocker, Regression |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-ansible-collection-2.4.1 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, if a user did not specify the correlationId as part of the cluster_upgrade playbook, the cluster upgrade failed.
In this release, if a correlationId is not specified, a random correlationId is generated to ensure that the whole cluster upgrade process can be filtered in RHV Events using this correlationId.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-11-30 07:53:23 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: | |||
This bug has low overall severity and is not going to be further verified by QE. If you believe special care is required, feel free to properly align relevant severity, flags and keywords to raise PM_Score or use one of the Bumps ('PrioBumpField', 'PrioBumpGSS', 'PrioBumpPM', 'PrioBumpQA') in Keywords to raise it's PM_Score above verification threashold (1000).
The cluster upgrade role still fails with the same error in ovirt-ansible-collection-2.4.0-1.el8ev.noarch.
The bug fix is there (in defaults/main.yml - engine_correlation_id: "{{ 99999999 | random | to_uuid }}") but it is not doing what is supposed to do. If the engine_correlation_id is specified as extra_var in ansible-playbook cmd line then it works.
The cluster upgrade role succeeds with working engine_correlation_id. Verified in ovirt-ansible-collection-2.4.1-1.el8ev.noarch Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (RHV Engine and Host Common Packages update [ovirt-4.5.3-2]), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:8696 |
Description of problem: When running cluster upgrade role without specifying correlation_id, the cluster upgrade fails on wrong correlation_id. When the correlation_id is specified the cluster upgrade role does not fail. 2022-11-11 14:29:06,574+02 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-263) [] Operation Failed: [Cannot update progress, given correlation id does not match the current update correlation id.] Version-Release number of selected component (if applicable): ovirt-ansible-collection-2.3.0-1.el8ev.noarch How reproducible: Every time Steps to Reproduce: 1. Run cluster upgrade role: cluster_upgrade playbook: - hosts: localhost gather_facts: false remote_user: root roles: - cluster_upgrade collections: - redhat.rhv extra_vars.json without correlation_id: {"engine_url": "https://<engine>/ovirt-engine/api", "engine_user": "admin@internal", "engine_password": "<password>", "engine_insecure": "yes", "cluster_name": "golden_env_mixed_1", "data_center_name": "golden_env_mixed"} Actual results: The cluster upgrade fails Expected results: The cluster upgrade succeeds Additional information: Correlation_id specified extra_vars.json with correlation_id: {"engine_url": "https://<engine>/ovirt-engine/api", "engine_user": "admin@internal", "engine_password": "<password>", "engine_insecure": "yes", "cluster_name": "golden_env_mixed_1", "data_center_name": "golden_env_mixed", "engine_correlation_id": "Hello"}