when "upload_resources" did not deploy all parts of platform properly, infrastructure playbook can configure onap.repo in failed state.
Subsequent re-run of upload_resource (site.yml) will fail on:

TASK [Check if nfs-utils is installed] ************************************************************************************************************************************************************************
fatal: [infrastructure-server]: FAILED! => {"changed": false, "msg": "Error from repoquery: ['/usr/bin/repoquery', '-show-duplicates', 'plugins', 'quiet', 'disablerepo', '', 'enablerepo', '', '-qf', '%

|%

|%

|%

|%

|%

', 'nfs-utils']: Could not match packages: failure: repodata/repomd.xml from onap: [Errno 256] No more mirrors to try.\nfile:///mnt/opt/onap/pkg/rhel/repodata/repomd.xml: [Errno 14] curl#37 - \"Couldn't open file /mnt/opt/onap/pkg/rhel/repodata/repomd.xml\"\n"}

I think we should improve code by checking that repo is functional after creating onap.repo
If it's not we should make clean-up (Idempotency)