This bug was initially created as a copy of Bug #1878665

Description of problem:
There are two means to bring hypervisor hosts to HBI in Subwatch ,
1. Yupana (Satellite)
2. RHSM-Conduit (RHSM)

If any Hypervisor with 0 socket counts makes it way to HBI, the next tally onwards on the account fails

How reproducible:
Always

Steps to Reproduce:
1. Have a hypervisor with 0 socket submitted via yupana
2.
3.

Actual results:
Tally breaks and account is not tallied.
PFA to see the trace and log

Expected results:
There should be validation happening to detect the 0 hypervisor socket and stop it from being submitted to HBI.
Currently, there is validation at rhsm-conduit, there should be the same in yupana as well.

Additional info:
This only affects the hypervisors submitted via Yupana, i.e Red hat Cloud Satellite Plugin.