Bug 1341076
| Summary: | NGN always wait for vm shutdown although vm is shutdown after deploy HE. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-node | Reporter: | cshao <cshao> | ||||||
| Component: | UI | Assignee: | Ryan Barry <rbarry> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | cshao <cshao> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 4.0 | CC: | bugs, dfediuck, huzhao, leiwang, rbarry, weiwang, yaniwang, ycui | ||||||
| Target Milestone: | ovirt-4.0.0-rc | Keywords: | Regression | ||||||
| Target Release: | 4.0 | Flags: | rule-engine:
ovirt-4.0.0+
rule-engine: blocker+ rule-engine: planning_ack+ fdeutsch: devel_ack+ cshao: testing_ack+ |
||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | cockpit-ovirt-dashboard-0.10.2-0.0.1.el7ev | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-07-05 07:50:21 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | 1344900 | ||||||||
| Bug Blocks: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1163080 [details]
all log info
Add keyword "regression" due to no such issue on rhev-hypervisor7-ng-3.6-20160518.0.x86_64, so this is a regression bug. The question is if it's an issue in trhe UI or if he-setup is waiting. 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. This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP. I wasn't actually able to reproduce this, but the attached patch will catch it in any case. Ryan, can you add a reference to the relevant patch? (In reply to Doron Fediuck from comment #7) > Ryan, can you add a reference to the relevant patch? Added. The bug-url was in the commit. I suppose that the gerrit hooks must not have automatically added it to this bug... blocker by bug 1344900, I will verify this bug after bug 1344900 fixed. Test version: rhev-hypervisor7-ng-4.0-20160616.0.x86_64 ovirt-hosted-engine-ha-2.0.0-1.el7ev.noarch ovirt-hosted-engine-setup-2.0.0.2-1.el7ev.noarch imgbased-0.7.0-0.1.el7ev.noarch redhat-release-rhev-hypervisor-4.0-0.7.el7.x86_64 cockpit-ovirt-dashboard-0.10.4-0.0.1.el7ev.noarch Test steps: 1. Install NGN 2. Config network and deploy HE with correct steps. 3. Try to finish HE setup process. 4. Register Host to Engine. 5. Shutdown the HE vm after pop-up shut-down info. Test result: NGN can identify the HE status after the VM is shut-down. Change bug status to VERIFIED. oVirt 4.0.0 has been released, closing current release. |
Created attachment 1163079 [details] HE-VM-SHUTDOWN Description of problem: NGN always wait for vm shutdown although vm is shutdown after deploy HE. Version-Release number of selected component (if applicable): rhev-hypervisor7-ng-4.0-20160527.0.x86_64 imgbased-0.7.0-0.1.el7ev.noarch cockpit-0.103-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install NGN 2. Config network and deploy HE with correct steps. 3. Try to finish HE setup process. 4. Register Host to Engine. 5. Shutdown the HE vm after pop-up shut-down info. Actual results: After step5, It always show "The system will wait until the VM is down" Expected results: NGN can identify the HE status after the VM is shut-down. Additional info: No such issue on rhev-hypervisor7-ng-3.6-20160518.0.x86_64, so this is a regression bug.