You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 24, 2023. It is now read-only.
We were successful in running the deploy script for controller and node with ne_ngc_test_enable variable true in group_vars/all/10-default.yml. The documentation mentioned that by enabling ngc rule, the playbook script performs epcforedge repo cloning and starts AF,NEF and OAM pods. But, to the contrary, when we check for those pods, they are not present. Can you please give more information on what must be the problem. How can I make sure if the epcforedge repo is cloned?
Thanks and regards.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
We were successful in running the deploy script for controller and node with ne_ngc_test_enable variable true in group_vars/all/10-default.yml. The documentation mentioned that by enabling ngc rule, the playbook script performs epcforedge repo cloning and starts AF,NEF and OAM pods. But, to the contrary, when we check for those pods, they are not present. Can you please give more information on what must be the problem. How can I make sure if the epcforedge repo is cloned?
Thanks and regards.
The text was updated successfully, but these errors were encountered: