Bug 1458713 - [RFE][RHV] Host refresh enhancement
Summary: [RFE][RHV] Host refresh enhancement
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: MVP
: 5.9.0
Assignee: Piotr Kliczewski
QA Contact: Angelina Vasileva
URL:
Whiteboard: rhev
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-05 09:52 UTC by Piotr Kliczewski
Modified: 2019-06-06 11:12 UTC (History)
8 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-01 13:12:59 UTC
Category: ---
Cloudforms Team: RHEVM
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ManageIQ manageiq-content pull 144 0 None None None 2017-07-18 10:34:01 UTC
Github ManageIQ manageiq-content pull 145 0 None None None 2017-07-18 12:55:48 UTC
Github ManageIQ manageiq-content pull 146 0 None None None 2017-07-18 13:08:13 UTC
Red Hat Product Errata RHSA-2018:0380 0 normal SHIPPED_LIVE Moderate: Red Hat CloudForms security, bug fix, and enhancement update 2018-03-01 18:37:12 UTC

Description Piotr Kliczewski 2017-06-05 09:52:23 UTC
During host refresh we run full refresh for specific events:

- HOST_DETECTED
- HOST_INSTALL
- USER_ADD_HOST
- USER_REMOVE_HOST
- USER_UPDATE_HOST

We need to make sure to run targeted refresh instead.

Comment 2 Jan Zmeskal 2017-11-09 09:40:47 UTC
Could you please provide basic reproduction steps? Is there something specific in emv.log that tells which kind of refresh was executed?

Comment 3 Piotr Kliczewski 2017-11-09 10:44:45 UTC
In order to reproduce it you need to add, update or remove a host. In the emv log you need to check which refresh type was triggered for events specified in comment #1.

Comment 4 Ilanit Stein 2017-12-10 13:34:20 UTC
Piotr,

As it seems there are more hosts related events 
(host status status changes, like move host to maintenance maybe),
that may trigger host target refresh,
Would you please list all those additional events 
(in addition to those mentioned in this RFE description), 
so we will be able to cover them in the feature test plan?

Thanks.

Comment 5 Piotr Kliczewski 2017-12-11 08:53:17 UTC
Ilanit,

All 5 events mentioned in comment #1 were not targeted. All the other based on the code are but I will list them for you:

HOST_ACTIVATE, HOST_ACTIVATE_FAILED, HOST_DETECTED, HOST_FAILURE, HOST_INITIATED_RUN_VM, HOST_INSTALL, HOST_MAINTENANCE, HOST_MAINTENANCE_FAILED, HOST_RECOVER, HOST_RECOVER_FAILED, HOST_REGISTER_SUCCEEDED, SYSTEM_HOST_RESTART, USER_ADD_HOST, USER_HOST_MAINTENANCE, USER_HOST_RESTART, USER_HOST_SHUTDOWN, USER_HOST_START, USER_HOST_STOP, USER_INITIATED_RUN_VM_FAILED, USER_INITIATED_SHUTDOWN_VM

Comment 6 Ilanit Stein 2017-12-18 10:15:44 UTC
Verified on CFME-5.9.0.12/RHV-4.1.8.

Those host events were tested:
- HOST_DETECTED
- HOST_INSTALL
- USER_ADD_HOST
- USER_REMOVE_HOST
- USER_UPDATE_HOST

Test plan run: 
RHEVM3/testrun?id=4_1_targeted_refresh_for_host_events_cfme_5_9_0_12_rhv_4_1_8

Comment 9 errata-xmlrpc 2018-03-01 13:12:59 UTC
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, 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-2018:0380


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