Bug 1835574
| Summary: | Automate creation of gluster logical network | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | SATHEESARAN <sasundar> |
| Component: | gluster-ansible | Assignee: | Gobinda Das <godas> |
| Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | rhgs-3.5 | CC: | asakthiv, godas, pprakash, puebele, rhs-bugs, sabose, sasundar |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.5.z Batch Update 2 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | gluster-ansible-roles-1.0.5-12.el8rhgs | Doc Type: | Enhancement |
| Doc Text: |
Previously, after RHHI deployment, Gluster network was created manually through RHV-M User Interface.With this release, Ansible playbook creates a Gluster logical network so you don't need to create it manually
|
Story Points: | --- |
| Clone Of: | 1832966 | Environment: | |
| Last Closed: | 2020-06-16 05:57:32 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1832966 | ||
Verified with gluster-ansible-roles-1.0.5-12.el8rhgs 1. The playbook and inventory to create the gluster network is available [root@ ~]# ls /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/gluster_network_inventory.yml /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/gluster_network_inventory.yml [root@ ~]# ls /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/tasks/gluster_network_setup.yml /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/tasks/gluster_network_setup.yml 2. Run the playbook post RHHI-V deployment 3. New logical network is created and attached to all the hosts RDT looks good to me. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:2575 |
Description of problem: ----------------------- Creation of RHV logical network for gluster traffic is not automated and it stops with adding the additional hosts to the cluster. In addition to adding the additional hosts to the cluster, there should also be a automated task that creates the gluster logical network and attach that network to all the hosts, to the network interface connected to gluster network Only when there are dedicated networks for Storage and ovrtmgmt ( Remember cockpit plugin has a option to use the same network for both storage and public network), the following task should get kicked in. 1. Create a logical network with following properties: - Non VM network - VM Migration roles - Gluster role - Not required - Attached to 'Default' data center and 'Default' cluster 2. On all the hosts, attach this logical network to interface that's used for gluster network Version-Release number of selected component (if applicable): -------------------------------------------------------------- RHHI-V 1.8 How reproducible: ----------------- Always Steps to Reproduce: -------------------- 1. Complete RHHI-V deployment from web console ( cockpit ) Actual results: --------------- Logical network for gluster traffic is not created, and users had to create it manually Expected results: ----------------- Logical network for gluster traffic should be created automatically and attached to the corresponding network interface used for gluster traffic on all the hosts --- Additional comment from RHEL Program Management on 2020-05-07 14:29:32 UTC --- This bug is automatically being proposed for RHHI-V 1.8 release at Red Hat Hyperconverged Infrastructure for Virtualization product, by setting the release flag 'rhiv‑1.8' to '?'. If this bug should be proposed for a different release, please manually change the proposed release flag.