Bug 1432326
Summary: | Network goes out of sync when glusternw is associated with gluster IP. | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | RamaKasturi <knarra> |
Component: | BLL.Gluster | Assignee: | Sahina Bose <sabose> |
Status: | CLOSED WONTFIX | QA Contact: | SATHEESARAN <sasundar> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.1.0.3 | CC: | bugs |
Target Milestone: | --- | Flags: | sbonazzo:
ovirt-4.2-
|
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
When the Gluster network was associated with a new node's network interface, the Gluster network entered an out of sync state. This no longer occurs in Red Hat Hyperconverged Infrastructure for Virtualization 1.8.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-11-21 06:41:52 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: | |||
Bug Blocks: | 1277939, 1433896 |
Description
RamaKasturi
2017-03-15 06:42:12 UTC
(In reply to RamaKasturi from comment #0) > Description of problem: > I see that when user tries to attach glusternw to glusterIP, network goes > outofsync. After running refresh capabilities on the host network comes back > up fine. > > Version-Release number of selected component (if applicable): > ovirt-engine-4.1.0.3-0.1.el7.noarch > > How reproducible: > Always > > Steps to Reproduce: > 1. Install grafton setup. > 2. Now click on the Network Interfaces tab, select setup Host Networks, drag > and drop glusternw to the glusterIP > 3. click 'OK' > > Actual results: > I see that glusternw goes 'out of sync' and running refresh capabilities on > the host makes the network fine. > > Expected results: > when glusternw is associated to gluster IP it should not go out of sync. > > Additional info: Closing this as there's a workaround associated with it, and is low impact. This issue no longer observed with RHHI-V 1.8 environment |