The test basic_vm_macro as been introduce din CI for honolulu

it waorks fine in Guilin but in Honolulu the  results are hieratic

on the 3 last daily for examples it was the only test in error

https://logs.onap.org/onap-integration/daily/onap_daily_pod4_honolulu/2021-04/28_11-32/smoke-usecases/basic_vm_macro/basic_vm_macro/reporting.html

https://logs.onap.org/onap-integration/daily/onap_daily_pod4_honolulu/2021-04/27_01-06/smoke-usecases/basic_vm_macro/basic_vm_macro/reporting.html

https://logs.onap.org/onap-integration/daily/onap_daily_pod4_honolulu/2021-04/24_00-58/smoke-usecases/basic_vm_macro/basic_vm_macro/reporting.html

The error causes are

24/04: Service instantiation basic_vm_macro_service_instance timed out (already reported, SO remain IN PROGRESS and reach the tester timeout)

27/04: STATUS: Error Source: SDNC, Error Message: Failed to create self-serve assignment for vnf with vnf-id=d8a03230-b24d-43c4-a18d-29b8e49e4609 with error: Failed to get RA assignments: Error from BlueprintProcessingClient FLOW STATUS: All Rollback flows have completed successfully ROLLBACK STATUS: Rollback has been completed successfully."

STATUS: Error Source: SDNC, Error Message: Failed to create self-serve assignment for vnf with vnf-id=4b4078b5-f785-4648-b069-8de5077f72c7 with error: Failed to get RA assignments: Error from BlueprintProcessingClient FLOW STATUS: All Rollback flows have completed successfully ROLLBACK STATUS: Rollback has been completed successfully

as the last error occured twice and was observed also regularly in gate, I assign the ticket to SDNC

the first error (timeout) is more difficult to assign.

see SDNC logs in the daily logs on onap-k8s-teardown for details