Bug 1279378
| Summary: | [RFE] Add manual execution of 'Check for upgrades' into webadmin and RESTAPI | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Barak Korren <bkorren> |
| Component: | BLL.Infra | Assignee: | Ravi Nori <rnori> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jiri Belka <jbelka> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 3.6.0 | CC: | bugs, gklein, jbelka, lsurette, masayag, melewis, mperina, oourfali, pstehlik, rbalakri, Rhev-m-bugs, srevivo, ykaul |
| Target Milestone: | ovirt-4.1.0-alpha | Keywords: | FutureFeature |
| Target Release: | 4.1.0 | Flags: | mperina:
ovirt-4.1?
jbelka: testing_plan_complete+ rule-engine: planning_ack? mperina: devel_ack+ pstehlik: testing_ack+ |
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
With this update, a new option to check for upgrades has been added when installing a host. In the Administration Portal this is available in the host installation menu and it can be triggered by using the hosts upgradecheck endpoint in the REST API.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-02-01 14:56:30 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1427728 | ||
|
Description
Barak Korren
2015-11-09 10:30:07 UTC
The functionality could be added as part of the 'refresh capabilities' action to allow the administrator to manually check for updates. 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. 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. (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. 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. ok, ovirt-engine-4.1.0-0.2.master.20161213231004.gitfdf720a.el7.centos.noarch |