Skip to content

Error when running make 5gc install #2

Open
@hussainahmadmo

Description

@hussainahmadmo

I am working using the quickstart guide on Aether website but when I run the following command :
make aether-5gc-install

Get the following failure error from one of the Ansible tasks in the path /home/atlas-support/projects/aether-onramp/deps/5gc/roles/core/tasks/install.yml:

- name: deploy aether 5gc
  block:
    - name: deploy aether 5gc
      kubernetes.core.helm:
        update_repo_cache: true
        name: sd-core
        release_namespace: omec
        create_namespace: true
        chart_ref: "{{ core.helm.chart_ref }}"
        chart_version: "{{ core.helm.chart_version }}"
        values_files:
          - /tmp/sdcore-5g-values.yaml
        wait: true
        wait_timeout: "1m30s"
        force: true
      when: inventory_hostname in groups['master_nodes'] 


TASK [core : deploy aether 5gc] ****************************************************************************************************************
fatal: [node1]: FAILED! => {"changed": false, "command": "/usr/local/bin/helm --version=0.12.6 upgrade -i --reset-values --wait --timeout 1m30s --create-namespace --values=/tmp/sdcore-5g-values.yaml sd-core aether/sd-core", "msg": "Failure when executing Helm command. Exited 1.\nstdout: Release \"sd-core\" does not exist. Installing it now.\n\nstderr: coalesce.go:175: warning: skipped value for kafka.config: Not a table.\nError: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline\n", "stderr": "coalesce.go:175: warning: skipped value for kafka.config: Not a table.\nError: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline\n", "stderr_lines": ["coalesce.go:175: warning: skipped value for kafka.config: Not a table.", "Error: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline"], "stdout": "Release \"sd-core\" does not exist. Installing it now.\n", "stdout_lines": ["Release \"sd-core\" does not exist. Installing it now."]}

The status shows one of the deployed pods crashes. Any suggestions on where are things going wrong ?

kubectl get pods -n omec

NAME READY STATUS RESTARTS AGE
amf-5887bbf6c5-f9nbb 1/1 Running 0 13m
ausf-6dbb7655c7-mlcgb 1/1 Running 0 11m
kafka-0 1/1 Running 1 (12m ago) 13m
metricfunc-b9f8c667b-9wfgq 1/1 Running 0 13m
mongodb-0 1/1 Running 0 13m
mongodb-1 1/1 Running 0 12m
mongodb-arbiter-0 1/1 Running 0 13m
nrf-54bf88c78c-tmn8f 1/1 Running 0 13m
nssf-5b85b8978d-dxcrv 1/1 Running 0 13m
pcf-758d7cfb48-tlflp 1/1 Running 0 13m
sd-core-zookeeper-0 1/1 Running 0 13m
simapp-6cccd6f787-ng7f4 1/1 Running 0 13m
smf-7f89c6d849-njxvk 1/1 Running 0 13m
udm-768b9987b4-ppckx 1/1 Running 0 13m
udr-8566897d45-6d82h 1/1 Running 0 13m
upf-0 3/5 CrashLoopBackOff 13 (15s ago) 11m
webui-5894ffd49d-4bcgg 1/1 Running 0 13m

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions