summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRinku Kothiya <rkothiya@redhat.com>2019-10-10 10:20:30 +0000
committerRinku Kothiya <rkothiya@redhat.com>2019-10-10 10:24:43 +0000
commita92e9e8e8ae6b97db8e0c1fb8268aef734ab48b4 (patch)
tree9641917a6c4db7a6755826bd78c2a91bb6278ecb
parentbac5d7d60d14a190217fcd84fd0803a4d6a2e37d (diff)
doc: Updated release notes for release-7v7.0
updates: bz#1732875 Change-Id: Ie2fa04a76a1e36addff5f6bd6bd6b88aad2f948a Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>
-rw-r--r--doc/release-notes/7.0.md33
1 files changed, 32 insertions, 1 deletions
diff --git a/doc/release-notes/7.0.md b/doc/release-notes/7.0.md
index bb31433..2bcf4b2 100644
--- a/doc/release-notes/7.0.md
+++ b/doc/release-notes/7.0.md
@@ -17,7 +17,7 @@ A full list of bugs that have been addressed is included further below.
([reference](https://www.gluster.org/release-schedule/))
2. Release 7 will receive maintenance updates around the 10th of every month
-for the first 3 months post release (i.e Oct'19, Nov'19, Dec'19). Post the
+for the first 3 months post release (i.e Nov'19, Dec'19, Jan'20). Post the
initial 3 months, it will receive maintenance updates every 2 months till EOL.
@@ -56,6 +56,7 @@ Any new volumes created with the release will have the `fips-mode-rchecksum` vol
If a client older than glusterfs-4.x (i.e. 3.x clients) accesses a volume which has the `fips-mode-rchecksum` volume option enabled, it can cause erroneous checksum computation/ unwanted behaviour during afr self-heal. This option is to be enabled only when all clients are also >=4.x. So if you are using these older clients, please explicitly turn this option `off`.
+
## Bugs addressed
Bugs addressed since release-6 are listed below.
@@ -231,4 +232,34 @@ Bugs addressed since release-6 are listed below.
- [#1721441](https://bugzilla.redhat.com/1721441): geo-rep: Fix permissions for GEOREP_DIR in non-root setup
- [#1721601](https://bugzilla.redhat.com/1721601): [SHD] : logs of one volume are going to log file of other volume
- [#1722541](https://bugzilla.redhat.com/1722541): stale shd process files leading to heal timing out and heal deamon not coming up for all volumes
+- [#1703322](https://bugzilla.redhat.com/1703322): Need to document about fips-mode-rchecksum in gluster-7 release notes.
+- [#1722802](https://bugzilla.redhat.com/1722802): Incorrect power of two calculation in mem_pool_get_fn
+- [#1723890](https://bugzilla.redhat.com/1723890): Crash in glusterd when running test script bug-1699339.t
+- [#1728770](https://bugzilla.redhat.com/1728770): Failures in remove-brick due to [Input/output error] errors
+- [#1736481](https://bugzilla.redhat.com/1736481): capture stat failure error while setting the gfid
+- [#1739424](https://bugzilla.redhat.com/1739424): Disperse volume : data corruption with ftruncate data in 4+2 config
+- [#1739426](https://bugzilla.redhat.com/1739426): Open fd heal should filter O_APPEND/O_EXCL
+- [#1739427](https://bugzilla.redhat.com/1739427): An Input/Output error happens on a disperse volume when doing unaligned writes to a sparse file
+- [#1741041](https://bugzilla.redhat.com/1741041): atime/mtime is not restored after healing for entry self heals
+- [#1743200](https://bugzilla.redhat.com/1743200): ./tests/bugs/glusterd/bug-1595320.t is failing
+- [#1744874](https://bugzilla.redhat.com/1744874): interrupts leak memory
+- [#1745422](https://bugzilla.redhat.com/1745422): ./tests/bugs/glusterd/bug-1595320.t is failing
+- [#1745914](https://bugzilla.redhat.com/1745914): ESTALE change in fuse breaks get_real_filename implementation
+- [#1746142](https://bugzilla.redhat.com/1746142): ctime: If atime is updated via utimensat syscall ctime is not getting updated
+- [#1746145](https://bugzilla.redhat.com/1746145): CentOs 6 GlusterFS client creates files with time 01/01/1970
+- [#1747301](https://bugzilla.redhat.com/1747301): Setting cluster.heal-timeout requires volume restart
+- [#1747746](https://bugzilla.redhat.com/1747746): The result (hostname) of getnameinfo for all bricks (ipv6 addresses) are the same, while they are not.
+- [#1748448](https://bugzilla.redhat.com/1748448): syncop: Bail out if frame creation fails
+- [#1748774](https://bugzilla.redhat.com/1748774): Incorrect power of two calculation in mem_pool_get_fn
+- [#1749155](https://bugzilla.redhat.com/1749155): bug-1402841.t-mt-dir-scan-race.t fails spuriously
+- [#1749305](https://bugzilla.redhat.com/1749305): Failures in remove-brick due to [Input/output error] errors
+- [#1749664](https://bugzilla.redhat.com/1749664): The result (hostname) of getnameinfo for all bricks (ipv6 addresses) are the same, while they are not.
+- [#1751556](https://bugzilla.redhat.com/1751556): syncop: Bail out if frame creation fails
+- [#1752245](https://bugzilla.redhat.com/1752245): Crash in glusterd when running test script bug-1699339.t
+- [#1752429](https://bugzilla.redhat.com/1752429): Ctime: Cannot see the "trusted.glusterfs.mdata" xattr for directory on a new brick after rebalance
+- [#1755212](https://bugzilla.redhat.com/1755212): geo-rep: performance improvement while syncing heavy renames with existing destination
+- [#1755213](https://bugzilla.redhat.com/1755213): geo-rep: non-root session going fault due improper sub-command
+- [#1755678](https://bugzilla.redhat.com/1755678): Segmentation fault occurs while truncate file
+- [#1756002](https://bugzilla.redhat.com/1756002): git clone fails on gluster volumes exported via nfs-ganesha
+