Bug 1414787
| Summary: | Hide tracebacks in engine.log by upgrading non responsive host | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Lucie Leistnerova <lleistne> | ||||||
| Component: | Backend.Core | Assignee: | Ravi Nori <rnori> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Lucie Leistnerova <lleistne> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 4.1.0 | CC: | bugs, lleistne, lsvaty, mgoldboi, mperina, oourfali, stirabos | ||||||
| Target Milestone: | ovirt-4.1.3 | Flags: | rule-engine:
ovirt-4.1+
mgoldboi: planning_ack+ mperina: devel_ack+ lsvaty: testing_ack+ |
||||||
| Target Release: | 4.1.3.3 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2017-07-06 13:15:59 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Lucie Leistnerova
2017-01-19 12:49:41 UTC
If host is in Maintenance, then check for upgrades should not be executed? What are exact reproducing steps for it? It is not the check for upgrade, but upgrade itself. In General tab there is an Upgrade link and after clicking on it the error appears in engine log. Re opening the bug, seems that while the trace from 'org.ovirt.engine.core.bll.host.HostUpgradeManager' doesn't appear in engine.log (without debug mode), some other traces now appear as can be seen in the attached engine.log. The action's invocation time stamp in the log is: 15:43:12,435+02 INFO. Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. Created attachment 1258112 [details]
engine log
Traceback in org.ovirt.engine.core.bll.host.HostUpgradeManager is hidden, but in org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase still visible Steps to reproduce: 1. add newest repo to host 2. in engine on host Installation -> Check for upgrade, in General tab is Upgrade link available 3. put host to maintenance 4. stop sshd on host 5. try to upgrade host from engine engine.log attached tested in ovirt-engine-4.1.2-0.1.el7.noarch Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. Created attachment 1275870 [details]
engine.log.2
Moving back to 4.1.4 as it's part of 4.1.3.2 build INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Tag 'ovirt-engine-4.1.3.4' doesn't contain patch 'https://gerrit.ovirt.org/71813'] gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.1.3.4 For more info please contact: infra (In reply to rhev-integ from comment #10) > INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following > reason: > > [Tag 'ovirt-engine-4.1.3.4' doesn't contain patch > 'https://gerrit.ovirt.org/71813'] > gitweb: > https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ > ovirt-engine-4.1.3.4 > > For more info please contact: infra Not true, all attached pacthes have been merged to ovirt-engine-4.1 branch before June 1st traceback in org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase is also hidden verified in ovirt-engine-4.1.3.4-0.1.el7.noarch |