Bug 1203154
| Summary: | [RHEVM-RHS] Red Hat Gluster Storage Node status is shown UP, when glusterd was actually DOWN | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | SATHEESARAN <sasundar> | ||||
| Component: | ovirt-engine-webadmin-portal | Assignee: | Darshan <dnarayan> | ||||
| Status: | CLOSED UPSTREAM | QA Contact: | SATHEESARAN <sasundar> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 3.5.1 | CC: | amureini, ecohen, gklein, lsurette, rbalakri, Rhev-m-bugs, sabose, yeylon, ylavi | ||||
| Target Milestone: | --- | Keywords: | Regression | ||||
| Target Release: | 3.5.3 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | gluster | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: |
rhevm-gluster integration
|
|||||
| Last Closed: | 2015-04-06 08:52:26 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1207150 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
This issue is not seen in previous releases but with RHEVM 3.5 marking this bug for REGRESSION |
Created attachment 1003106 [details] attaching the log file from engine Description of problem: ----------------------- 'glusterd' is the management daemon running in each one of the Red Hat Gluster Storage Node. When the 'glusterd' is not running, the RH Gluster Node status should turn to 'DOWN'. This was the behaviour of RH Gluster Storage Node in gluster enabled cluster in RHEVM in earlier releases. But with RHEVM 3.5, the behavior is not just as expected. Version-Release number of selected component (if applicable): ------------------------------------------------------------- RHEVM 3.5 ( 3.5.1-0.1.el6ev ) RHS 3.0.4 Candidate ( glusterfs-3.6.0.52-1.el6rhs ) vdsm-4.16.8.1-6.2.el6rhs.x86_64 How reproducible: ----------------- Consistent, Always Steps to Reproduce: ------------------- 1. Create a RHEVM 3.5 DC with 3.5 compatibility 2. Create a gluster cluster of 3.5 compatibility 3. Add a RH Gluster Storage Node 4. Once the status in RHEVM shows UP, stop glusterd from gluster-cli 5. Check the status of RH Gluster Storage Node in RHEVM UI Actual results: --------------- RH Gluster Storage Node is shown UP with green colored icon Expected results: ----------------- RH Gluster Storage Node status should be DOWN with red colored icon Additional info: