Summary: | [downstream clone - 4.2.8] Command entities left in ACTIVE state after HostUpgradeCheckCommand | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | RHV bug bot <rhv-bugzilla-bot> |
Component: | ovirt-engine | Assignee: | Ravi Nori <rnori> |
Status: | CLOSED ERRATA | QA Contact: | Petr Matyáš <pmatyas> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.2.5 | CC: | lleistne, lsvaty, mgoldboi, mkalinin, mperina, ratamir, Rhev-m-bugs, rnori |
Target Milestone: | ovirt-4.2.8 | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ovirt-engine-4.2.8.1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1648417 | Environment: | |
Last Closed: | 2019-01-22 12:44:51 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Bug Depends On: | 1648417 | ||
Bug Blocks: |
Description
RHV bug bot
2018-11-30 14:34:34 UTC
Hi Ravi, can you please provide reproduction steps here? (Originally by Lukas Svaty) Reproduction steps From webadmin start "Check for Upgrade". After the check for upgrade finishes no command entities should be left in the command_entities table related to the check for upgrade command which should be command_type 141 and 142. (Originally by Ravi Shankar Nori) WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.2.z': '?'}', ] For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.2.z': '?'}', ] For more info please contact: rhv-devops (Originally by rhv-bugzilla-bot) Verified on ovirt-engine-4.2.8.1-0.1.el7ev.noarch 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/RHBA-2019:0121 |