If there are no hosts, the patchstate is expected to be
"n/a" since we can't be sure of the current patch state.
However, only the first patch's patchstate is set to "n/a"
while the remaining patch's have a patchstate of "Available"
(or whatever was previously reported for them). This commit
fixes the issue.
Reviewed: https:/ /review. opendev. org/c/starlingx /update/ +/872807 /opendev. org/starlingx/ update/ commit/ 09048aa032d449c 5d1c207baed8a49 16b8c96334
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 09048aa032d449c 5d1c207baed8a49 16b8c96334
Author: Jessica Castelino <email address hidden>
Date: Mon Feb 6 22:53:37 2023 +0000
Fix: Patchstate incorrect when there are no hosts
If there are no hosts, the patchstate is expected to be
"n/a" since we can't be sure of the current patch state.
However, only the first patch's patchstate is set to "n/a"
while the remaining patch's have a patchstate of "Available"
(or whatever was previously reported for them). This commit
fixes the issue.
Test Plan:
Tested with unit test case
Closes-Bug: 2006398 d46e3f88af9548d 2e74c241310
Signed-off-by: Jessica Castelino <email address hidden>
Change-Id: I7f34d35f552a04