I can also confirm this bug occurs for me, and led me down a rabbit hole trying to understand the lvm physical volume status validation.
replacing "pvck >/dev/null 2>&1" with "pvs --no-headings|awk '{print $1}'|xargs pvck >/dev/null 2>&1" allows the tool to output the correct status.
I can also confirm this bug occurs for me, and led me down a rabbit hole trying to understand the lvm physical volume status validation.
replacing "pvck >/dev/null 2>&1" with "pvs --no-headings|awk '{print $1}'|xargs pvck >/dev/null 2>&1" allows the tool to output the correct status.