Bug 1856671
| Summary: | [RFE] Expose the "reinstallation required" flag of the hosts in the API | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Juan Orti <jortialc> |
| Component: | ovirt-engine | Assignee: | Ori Liel <oliel> |
| Status: | CLOSED ERRATA | QA Contact: | Guilherme Santos <gdeolive> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.3.10 | CC: | ahadas, aperotti, dfodor, mavital, michal.skrivanek, mperina, mtessun |
| Target Milestone: | ovirt-4.4.3 | Keywords: | FutureFeature, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | rhv-4.4.3-8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-24 13:09:25 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: | |||
|
Description
Juan Orti
2020-07-14 08:10:22 UTC
This is a simple frontend alert derived from other properties changes. I would recommend to watch those other properties instead Verified on:
ovirt-engine-4.4.3.8-0.1.el8ev.noarch
Steps:
1. # curl -k -u admin@internal:<psswd> https://<engine-fqdn>/ovirt-engine/api/hosts/<host-uid> | grep reinstallation_required
<reinstallation_required>false</reinstallation_required>
Results:
reinstallation_required flag exposed on API
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 (Low: Red Hat Virtualization security, bug fix, and enhancement update), 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/RHSA-2020:5179 Due to QE capacity, we are not going to cover this issue in our automation |