Closed idirect-dev closed 4 years ago
Note also that roles/openness/onprem/worker/tasks/build.yml gave a similar error when I later tried to deploy a node - I made the same changes there as a workaround.
It looks like this is not an issue - it probably related to the context in which the script was initially executed (perhaps sudo as opposed to root.
Starting with a centos 7 minimal install (on controller and edge node hosts), I have cloned the experience kit. git clone https://github.com/open-ness/openness-experience-kits.git I modified group_vars/all.yml with my git token I edited inventory.ini to match my configurations (controller and one node) I've setup passwordless ssh and hostnames
I've run the deploy_onprem_controller.sh script
It fails as follows:
roles/openness/onprem/master/tasks/build.yml has an invalid path to git_repo (occurs twice) fatal: [mec-controller]: FAILED! => {"reason": "Unable to retrieve file contents\nCould not find or access '/git_repo/tasks/gitconfig_bootstrap.yml'"} fatal: [mec-controller]: FAILED! => {"reason": "Unable to retrieve file contents\nCould not find or access '/git_repo/tasks/gitconfig_remove.yml'"}
this appears to be a misconfiguration of the relative path of the git_repo directory (in both instances) modifying to use ../../../../git_repo instead of ../../../git_repo (which is an invalid path) appears to fix it. Perhaps this is misconfigured in build.yml?