Back to bug 1618669
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Dominik Holler | 2018-08-17 09:29:41 UTC | Blocks | 1403677 | |
| Atin Mukherjee | 2018-08-19 04:41:42 UTC | CC | dholler | |
| Flags | needinfo?(dholler) | |||
| Yaniv Lavi | 2018-08-19 13:08:39 UTC | CC | ylavi | |
| Yaniv Lavi | 2018-08-19 13:08:58 UTC | Priority | unspecified | high |
| Severity | unspecified | high | ||
| Atin Mukherjee | 2018-08-21 11:35:39 UTC | Keywords | FutureFeature | |
| Component | glusterd | core | ||
| Assignee | amukherj | atumball | ||
| QA Contact | bmekala | rhinduja | ||
| Amar Tumballi | 2018-08-24 05:19:56 UTC | CC | rkavunga | |
| Component | core | protocol | ||
| Assignee | atumball | mchangir | ||
| Dominik Holler | 2018-08-27 12:14:35 UTC | Summary | Test if gluster works in an IPv6 only scenario | [RFE] Enable gluster in IPv6 only scenarios |
| Flags | needinfo?(dholler) | |||
| liuwei | 2018-08-29 07:57:50 UTC | CC | wliu | |
| PnT Account Manager | 2018-11-05 23:16:32 UTC | CC | ylavi | |
| Amar Tumballi | 2018-11-20 05:47:29 UTC | CC | atumball | |
| Link ID | Github https://github.com/gluster/glusterfs/issues/192 | |||
| Assignee | mchangir | apaladug | ||
| Dominik Holler | 2018-12-18 11:20:09 UTC | Depends On | 1624708 | |
| Martin Tessun | 2018-12-18 11:21:00 UTC | CC | apaladug, mtessun, sbose | |
| Flags | needinfo?(sbose) needinfo?(apaladug) | |||
| Sumit Bose | 2018-12-18 12:12:36 UTC | CC | sabose | |
| Flags | needinfo?(sbose) needinfo?(apaladug) | |||
| Sumit Bose | 2018-12-18 12:13:36 UTC | Flags | needinfo?(apaladug) needinfo?(sabose) | |
| Dan Kenigsberg | 2018-12-18 12:58:47 UTC | CC | danken | |
| Rejy M Cyriac | 2018-12-20 08:37:11 UTC | Depends On | 1624708 | |
| Rejy M Cyriac | 2018-12-20 08:37:23 UTC | Blocks | 1624708 | |
| Dominik Holler | 2018-12-21 11:22:07 UTC | Blocks | 1403674 | |
| PnT Account Manager | 2018-12-27 22:29:39 UTC | CC | wliu | |
| Sahina Bose | 2019-01-09 09:51:09 UTC | Depends On | 1664590 | |
| Flags | needinfo?(sabose) | |||
| Rejy M Cyriac | 2019-01-17 04:11:51 UTC | CC | rcyriac | |
| Rejy M Cyriac | 2019-01-17 04:12:38 UTC | Assignee | apaladug | mchangir |
| Milind Changire | 2019-01-17 07:32:40 UTC | Status | NEW | ASSIGNED |
| Milind Changire | 2019-01-18 11:13:36 UTC | CC | mchangir | |
| Yaniv Kaul | 2019-01-30 13:57:06 UTC | Flags | needinfo?(mchangir) | |
| Milind Changire | 2019-01-30 14:08:52 UTC | Flags | needinfo?(apaladug) needinfo?(mchangir) | |
| Sachin P Mali | 2019-02-01 06:38:00 UTC | CC | smali | |
| Sunil Kumar Acharya | 2019-02-05 05:06:57 UTC | Status | ASSIGNED | POST |
| CC | sheggodu | |||
| Rejy M Cyriac | 2019-02-05 07:05:14 UTC | Keywords | ZStream | |
| Red Hat Bugzilla Rules Engine | 2019-02-05 07:05:26 UTC | Target Release | --- | RHGS 3.4.z Batch Update 4 |
| Dominik Holler | 2019-02-08 14:37:07 UTC | Blocks | 1403674 | |
| Milind Changire | 2019-02-10 05:43:16 UTC | Doc Text | Feature: Enable IPv6 communications in the Gluster cluster Reason: Users need ability to configure cluster with IPv6 Result: Users can now configure cluster with either IPv4 or IPv6 networking. Nodes can communicate with either IPv4 or IPv6 at any given time. There are two places that this option needs to be enabled: 1. /etc/glusterfs/glusterd.vol Vol-file option named transport.address-family needs to be added and set to "inet6" 2. mount command-line An xlator option needs to be passed to the mount command-line with any other options as: -o xlator-option="transport.address-family=inet6" | |
| Doc Type | If docs needed, set a value | Enhancement | ||
| Sunil Kumar Acharya | 2019-02-11 06:01:07 UTC | Status | POST | MODIFIED |
| Dominik Holler | 2019-02-11 07:59:50 UTC | CC | stirabos | |
| Flags | needinfo?(stirabos) | |||
| Simone Tiraboschi | 2019-02-11 09:24:14 UTC | Flags | needinfo?(stirabos) | needinfo?(sabose) |
| errata-xmlrpc | 2019-02-12 03:22:36 UTC | Status | MODIFIED | ON_QA |
| Sahina Bose | 2019-02-12 07:39:59 UTC | CC | godas | |
| Flags | needinfo?(sabose) | needinfo?(godas) | ||
| Gobinda Das | 2019-02-12 08:17:16 UTC | CC | surs | |
| Flags | needinfo?(godas) | needinfo?(surs) | ||
| Sachidananda Urs | 2019-02-12 08:34:55 UTC | Flags | needinfo?(surs) | |
| SATHEESARAN | 2019-02-12 09:21:49 UTC | CC | sasundar | |
| QA Contact | rhinduja | sasundar | ||
| Rejy M Cyriac | 2019-02-13 06:05:49 UTC | Blocks | 1676412 | |
| Sunil Kumar Acharya | 2019-02-13 13:49:57 UTC | Blocks | 1676886 | |
| Milind Changire | 2019-02-14 09:38:26 UTC | Fixed In Version | glusterfs-3.12.2-41 | |
| Anjana Suparna Sriram | 2019-02-25 11:52:22 UTC | Blocks | 1680596 | |
| SATHEESARAN | 2019-03-13 13:03:12 UTC | Status | ON_QA | VERIFIED |
| Anjana KD | 2019-03-25 13:41:31 UTC | CC | akrishna | |
| Doc Text | Feature: Enable IPv6 communications in the Gluster cluster Reason: Users need ability to configure cluster with IPv6 Result: Users can now configure cluster with either IPv4 or IPv6 networking. Nodes can communicate with either IPv4 or IPv6 at any given time. There are two places that this option needs to be enabled: 1. /etc/glusterfs/glusterd.vol Vol-file option named transport.address-family needs to be added and set to "inet6" 2. mount command-line An xlator option needs to be passed to the mount command-line with any other options as: -o xlator-option="transport.address-family=inet6" | With this update, users can configure cluster with either IPv4 or IPv6 networking. IPv6 support is available only for RHHI-V environments and not for RHGS standalone environments. Nodes can communicate with either IPv4 or IPv6 at any given time. | ||
| Flags | needinfo?(mchangir) | |||
| Milind Changire | 2019-03-25 13:53:11 UTC | Flags | needinfo?(mchangir) | |
| Anjana KD | 2019-03-25 14:13:30 UTC | Doc Text | With this update, users can configure cluster with either IPv4 or IPv6 networking. IPv6 support is available only for RHHI-V environments and not for RHGS standalone environments. Nodes can communicate with either IPv4 or IPv6 at any given time. | With this update, users can configure cluster with either IPv4 or IPv6 networking. IPv6 support is available only for Red Hat Hyperconverged Infrastructure for Virtualization environments and not for Red Hat Gluster storage standalone environments. Nodes can communicate with either IPv4 or IPv6 at any given time. |
| Anjana KD | 2019-03-25 17:35:36 UTC | Doc Text | With this update, users can configure cluster with either IPv4 or IPv6 networking. IPv6 support is available only for Red Hat Hyperconverged Infrastructure for Virtualization environments and not for Red Hat Gluster storage standalone environments. Nodes can communicate with either IPv4 or IPv6 at any given time. | With this update, users can configure cluster with either IPv4 or IPv6 networking. IPv6 support is available only for Red Hat Hyperconverged Infrastructure for Virtualization environments and not for Red Hat Gluster storage standalone environments. Nodes can communicate with either IPv4 or IPv6 at any given time, however, IPv6 support is for IPv6 only environments. For environments with both IPv4 and IPv6, IPv4 must be used. |
| errata-xmlrpc | 2019-03-27 00:07:27 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2019-03-27 03:43:39 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2019-03-27 03:43:39 UTC | |||
| errata-xmlrpc | 2019-03-27 03:44:56 UTC | Link ID | Red Hat Product Errata RHBA-2019:0658 |
Back to bug 1618669