gluster/glusterd2: glusterd2/commands/snapshot/snapshot-status.go; 7 LoC

Found a possible issue in [gluster/glusterd2](https://www.github.com/gluster/glusterd2) at [glusterd2/commands/snapshot/snapshot-status.go](https://github.com/gluster/glusterd2/blob/54ce5f6f7a714b321b6fb74a34207f66277d64b6/glusterd2/commands/snapshot/snapshot-status.go#L139-L145)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

> reference to b was used in a composite literal at line 142

[Click here to see the code in its original context.](https://github.com/gluster/glusterd2/blob/54ce5f6f7a714b321b6fb74a34207f66277d64b6/glusterd2/commands/snapshot/snapshot-status.go#L139-L145)

Click here to show the 7 line(s) of Go which triggered the analyzer.

```go
for _, b := range vol.GetBricks() {
bmap[b.ID.String()] = api.SnapBrickStatus{
Brick: api.BrickStatus{
Info: brick.CreateBrickInfo(&b),
},
}
}

```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: 54ce5f6f7a714b321b6fb74a34207f66277d64b6

Read glusterd2/commands/snapshot/snapshot-status.go around lines 139-145 and inspect how GetBricks and CreateBrickInfo are used in the snapshot-status flow. Verify the analyzer finding against the intended per-brick status output; done means the status is correct for every brick and relevant tests pass.

Written by the indexing model from the issue text.