Bug 1279378 - [RFE] Add manual execution of 'Check for upgrades' into webadmin and RESTAPI
Summary: [RFE] Add manual execution of 'Check for upgrades' into webadmin and RESTAPI
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ovirt-4.1.0-alpha
: 4.1.0
Assignee: Ravi Nori
QA Contact: Jiri Belka
URL:
Whiteboard:
Depends On:
Blocks: 1427728
TreeView+ depends on / blocked
 
Reported: 2015-11-09 10:30 UTC by Barak Korren
Modified: 2017-03-01 01:35 UTC (History)
13 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-02-01 14:56:30 UTC
oVirt Team: Infra
Embargoed:
mperina: ovirt-4.1?
jbelka: testing_plan_complete+
rule-engine: planning_ack?
mperina: devel_ack+
pstehlik: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 62080 0 master MERGED engine, webadmin: Add manual execution of 'Check for upgrades' 2016-11-21 17:08:34 UTC
oVirt gerrit 62348 0 master MERGED restapi : Add manual execution of 'Check for upgrades' 2016-11-22 20:11:48 UTC
oVirt gerrit 67144 0 master MERGED engine : Remove event flood rate for HOST_AVAILABLE_UPDATES_FAILED 2016-11-22 05:48:19 UTC

Description Barak Korren 2015-11-09 10:30:07 UTC
Description of problem:
Querying the hosts to update the status of the "Update available" icon happens quite infrequently (once a day by default). This means it cannot be used as a feedback mechanism for a sysadmin performing a manual update.
Please make sure the icon status is also updated when bringing a host back from maintenance mode, or provide a way to manually refresh it.

Comment 1 Moti Asayag 2015-11-10 13:35:24 UTC
The functionality could be added as part of the 'refresh capabilities' action to allow the administrator to manually check for updates.

Comment 2 Red Hat Bugzilla Rules Engine 2015-11-30 22:37:37 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 3 Yaniv Kaul 2016-07-28 11:49:47 UTC
I'm not sure I see the point in real production environments. Once a day should suffice. We could do it once in every 12h, but we really don't have that many updates.

Comment 4 Martin Perina 2016-07-28 11:58:04 UTC
(In reply to Yaniv Kaul from comment #3)
> I'm not sure I see the point in real production environments. Once a day
> should suffice. We could do it once in every 12h, but we really don't have
> that many updates.

The main reason to allow that is following: you know that there's some important upgrade, so you want to do upgrade now and not wait until next 'check for upgrade' execution (by default once a day). Without at least 1 detected upgrade the 'Upgrade' button is disabled. So manual execution can be useful at urgent situations.

Comment 5 Sandro Bonazzola 2016-12-12 14:00:55 UTC
The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.

Comment 6 Jiri Belka 2016-12-19 10:11:04 UTC
ok, ovirt-engine-4.1.0-0.2.master.20161213231004.gitfdf720a.el7.centos.noarch


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