sdc-getmachine and sdc-listmachines will fail if a nic for a machine is not in napi

[anthonyvia]

Calls to cloudapi's sdc-getmachine and sdc-listmachines result in the following if a nic for a machine is not in napi:

anthony.via$ sdc-listmachines
sdc-listmachines: error (ResourceNotFound): nic not found
anthony.via$ sdc-getmachine 9a3e0230-7a15-e5b2-ea4a-dccad50a2e9e
sdc-getmachine: error (ResourceNotFound): nic not found

After talking with rmustacc in IRC yesterday, we determined the problem was a VRRP nic we manually added to a zone, which did not and will not make its way into napi. I'm not sure if it is correct for a manually added nic to make its way into napi or not, but I think that sdc-listmachine and sdc-getmachine should still succeed, especially since the vmapi GET /vms/<uuid> call succeeds for the problem machine.

As a workaround for the time being, would it be correct for us to manually create the already existent VRRP nic in napi?

[rmustacc]

I'm not sure it's really going to be a proper work around. VRRP is not supported in SDC even though it's there in vmadm.