Bug 1440071
| Summary: | Can't create gluster georeplication | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Johan Bernhardsson <johan> |
| Component: | BLL.Gluster | Assignee: | Sahina Bose <sabose> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | --- | CC: | amureini, bugs, sabose |
| Target Milestone: | ovirt-4.1.2 | Flags: | sabose:
ovirt-4.1?
sabose: planning_ack? sabose: devel_ack+ sasundar: testing_ack+ |
| Target Release: | 4.1.2.1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: UI fails to validate the selected destination gluster volume
Consequence: Geo-replication cannot be created from oVirt.
Fix: Removed unnecessary text validation of gluster volume
Result: Can successfully create the geo-replication session from UI
|
Story Points: | --- |
| Clone Of: | Environment: |
centos 7.3
|
|
| Last Closed: | 2017-05-23 08:14:00 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: | |||
|
Description
Johan Bernhardsson
2017-04-07 09:16:22 UTC
Apparently the gfapi.py was fixed in #1409052 but i did not find it at first. And it is not available on the centos 7.3 packages yet. But still cant click on ok to finalize the the creation of the geo replicated volume This was a UI issue on validation. If the checkbox "Show volumes eligible for geo-replication" is unchecked, the list of volumes is populated. When a volume is selected, the reasons why the volume is not eligible is listed. If user wishes to, they can go ahead and create the session ignoring these warnings. Tested with RHV-4.1.2.2 Verified that the issue is no longer observed with the following steps 1. Created 2 gluster clusters and added gluster nodes 2. Created a volume in each cluster. 3. When selecting the volume, and creating geo-replication, it lists the available volume in the other cluster. 4. Created the geo-replication session and started the sync, observed that all the files are synced |