Details
-
Bug
-
Resolution: Fixed
-
Critical
-
4.6.2
-
Untriaged
-
Unknown
Description
5.0.0-3078 - Steps followed:
1. Configure a backup repo
2. Take 3 incremental backups - copy range.json for each backup to different location
3. Merge backup - copy range.josn file to different location
range1. json:
"1": {
"last": {
"snap_end": 0,
"snap_start": 0,
"seqno": 0,
"purge_seqno": 0,
"log": {
"log": [
],
"size": 1
}
},
"current": {
"seqno": 0,
"purge_seqno": 0,
"log": {
"log": [
],
"size": 1
}
}
},
range3.json:
"1": {
"last": {
"snap_end": 0,
"snap_start": 0,
"seqno": 0,
"purge_seqno": 0,
"log": {
"log": [
],
"size": 1
}
},
"current": {
"seqno": 0,
"purge_seqno": 0,
"log": {
"log": [
],
"size": 1
}
}
},
range4.json:
"1": {
"last": {
"snap_end": 0,
"snap_start": 0,
"seqno": 0,
"purge_seqno": 0,
"log": {
"log": [
],
"size": 1
}
},
"current": {
"seqno": 0,
"purge_seqno": 0,
"log": {
"log": [
],
"size": 1
}
}
},
Note that in range4.json uuid is 0 in current where as it is expected to be 267608282516981 - this behaviour is observed only when seqno of current in last json file is 0 - otherwise it is reflecting expected behaviour - attaching all json files and backup logs