diff options
| author | Amar Tumballi <amarts@redhat.com> | 2018-12-17 14:16:21 +0530 |
|---|---|---|
| committer | Atin Mukherjee <amukherj@redhat.com> | 2019-02-04 03:47:15 +0000 |
| commit | ec05f3a21f44e1fd5e089b7a0fffd5265b67cdfc (patch) | |
| tree | de539a2f5b744f704a9c0bbbbb2f6a3ce4406796 /tests/bugs/snapshot/bug-1227646.t | |
| parent | da5ae3afcd1b16bb0f2f9bffc1878b17b75429ed (diff) | |
glusterd: manage upgrade to current master
Scenarios tested:
* Upgrade the node when there are stripe / tiering and regular
type of volumes are present.
- All volumes are started fine (as the change was not on brick volfile)
- For tier, the functionality may not even work, as changetimerecorder
is not present.
- 'gluster volume info' properly shows as 'NOT SUPPORTED' for stripe and
tier type of volume.
* Upgrade in a rolling upgrade scenario, where an old version is
able to connect to higher master.
- on a normal volume, if the volfile-server was new, the newer client
volfiles needed to have utime xlator conditionally.
- with this one change, all other changes seem to work fine.
Change-Id: Ib2d3b69dafa02b2c695a735b13c1aa70aba07cb8
updates: bz#1635688
Signed-off-by: Amar Tumballi <amarts@redhat.com>
Diffstat (limited to 'tests/bugs/snapshot/bug-1227646.t')
| -rw-r--r-- | tests/bugs/snapshot/bug-1227646.t | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/tests/bugs/snapshot/bug-1227646.t b/tests/bugs/snapshot/bug-1227646.t index a16a8c270da..9b73dfdb32f 100644 --- a/tests/bugs/snapshot/bug-1227646.t +++ b/tests/bugs/snapshot/bug-1227646.t @@ -20,7 +20,6 @@ TEST $CLI snapshot create snap1 $V0 no-timestamp; TEST $CLI volume stop $V0 TEST $CLI snapshot restore snap1; TEST $CLI volume start $V0 -TEST $CLI volume tier $V0 attach $H0:$L1 $H0:$L2 TEST pkill gluster TEST glusterd |