Bug 1458713 – [RFE][RHV] Host refresh enhancement

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1458713 - [RFE][RHV] Host refresh enhancement

Summary:	[RFE][RHV] Host refresh enhancement

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat CloudForms Management Engine
Classification:	Red Hat
Component:	Providers (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	MVP
Target Release:	5.9.0
Assigned To:	Piotr Kliczewski
QA Contact:	Ilanit Stein
Docs Contact:

URL:
Whiteboard:	rhev
Keywords:	FutureFeature, RFE

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-06-05 05:52 EDT by Piotr Kliczewski
Modified:	2018-03-01 08:12 EST (History)
CC List:	8 users (show)

See Also:
Fixed In Version:	5.9.0.1
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-03-01 08:12:59 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	RHEVM

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Github	ManageIQ/manageiq-content/pull/144	None	None	None	2017-07-18 06:34 EDT
Github	ManageIQ/manageiq-content/pull/145	None	None	None	2017-07-18 08:55 EDT
Github	ManageIQ/manageiq-content/pull/146	None	None	None	2017-07-18 09:08 EDT
Red Hat Product Errata	RHSA-2018:0380	normal	SHIPPED_LIVE	Moderate: Red Hat CloudForms security, bug fix, and enhancement update	2018-03-01 13:37:12 EST

Groups: None (edit)

Description Piotr Kliczewski 2017-06-05 05:52:23 EDT

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 04:40:47 EST

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 05:44:45 EST

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 08:34:20 EST

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 03:53:17 EST

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 05:15:44 EST

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 08:12:59 EST

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.