Bug 1374593
| Summary: | After updating the node from UI, the node becomes active but still in 'Local maintenance' | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | SATHEESARAN <sasundar> |
| Component: | Frontend.WebAdmin | Assignee: | bugs <bugs> |
| Status: | CLOSED DUPLICATE | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.0.3 | CC: | bugs, knarra, sabose, stirabos |
| Target Milestone: | --- | Flags: | sasundar:
planning_ack?
sasundar: devel_ack? sasundar: testing_ack? |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
HC
|
|
| Last Closed: | 2016-09-09 15:52:48 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Looks like this bug is the consequence of the issue reported in the bug - https://bugzilla.redhat.com/show_bug.cgi?id=1353600 *** This bug has been marked as a duplicate of bug 1370907 *** |
Description of problem: ----------------------- Installed hyperconverged setup with RHEL 7.2, RHGS 3.1.3, RHV 4.0.3. I observed there is a update available for the node, when clicked on the node and did a upgrade from UI. The node moved in to maintenance, then the update started. Post the update, the became active once again, but the node was still marked as 'Local maintenance' Version-Release number of selected component (if applicable): ------------------------------------------------------------- RHV 4.0.3 RHGS 3.1.3 ( glusterfs-3.7.9-12.el7rhgs ) RHEL 7.2 How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Install HC with RHGS 3.1.3 ( note- this deployment has self-hosted engine) 2. Once there are 3 nodes available in gluster + virt enabled gluster, make sure to note the status of the nodes 3. When there is update icon available on the nodes, click on the node to update 4. Check for the status of the host post update Actual results: --------------- Hosts become active post update, but it is marked as 'Local Maintenance' Expected results: ----------------- Hosts should become active and should not be marked as 'Local Mainenance' Additional info: ---------------- post update : --== Host 3 status ==-- Status up-to-date : True Hostname : tettnang.lab.eng.blr.redhat.com Host ID : 3 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"} Score : 0 stopped : False Local maintenance : True crc32 : c9af6654 Host timestamp : 17575 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=17575 (Fri Sep 9 13:05:24 2016) host-id=3 score=0 maintenance=True state=LocalMaintenance stopped=False