pfnet-research/node-operation-controller: controllers/noderemediationtemplate_controller.go; 3 LoC

Found a possible issue in [pfnet-research/node-operation-controller](https://www.github.com/pfnet-research/node-operation-controller) at [controllers/noderemediationtemplate_controller.go](https://github.com/pfnet-research/node-operation-controller/blob/773a4d0c15327ada43b00c3d8f3a1dfb797234e8/controllers/noderemediationtemplate_controller.go#L75-L77)

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 remediation is reassigned at line 76

[Click here to see the code in its original context.](https://github.com/pfnet-research/node-operation-controller/blob/773a4d0c15327ada43b00c3d8f3a1dfb797234e8/controllers/noderemediationtemplate_controller.go#L75-L77)

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

```go
for _, remediation := range childRemediations.Items {
childRemediationByNodeName[remediation.Spec.NodeName] = &remediation
}

```

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: 773a4d0c15327ada43b00c3d8f3a1dfb797234e8

Read controllers/noderemediationtemplate_controller.go around lines 75-77 and inspect the surrounding controller logic to understand the reported reassignment. Check whether the analyzer finding affects the stored remediation references and run the repository's available tests; the work is done when the finding is addressed without changing intended controller behavior.

Written by the indexing model from the issue text.