Welcome to the Linux Foundation Forum!

Fail deploy in LFS263 Exercise 4.1


I fail to deploy in LFS263 Exercise 4.1.

 LFS263 Exercise 4.1

The following command:
 nohup sudo bash -x aio-centos-gcp-deploy.sh 4 &

 No package matching 'erlang-22.1.3-1.el7.x86_64' found available
 (10 out of 10 Fails)

nohup.out file:
 TASK [rabbitmq_server : Register a fact for the installed RabbitMQ version] ****
 skipping: [aio1_rabbit_mq_container-7aeeaf7f] => (item={'skipped': True, 'changed': False, 'skip_reason': u'Conditional result was False'})
 ok: [aio1_rabbit_mq_container-7aeeaf7f] => (item={'stderr_lines': [], u'changed': True, u'end': u'2021-03-12 07:50:27.659404', u'stdout': u'', u'cmd':
 u'rpm -qa | grep rabbitmq-server', u'failed': False, u'delta': u'0:00:00.259248', u'stderr': u'', u'rc': 1, u'msg': u'non-zero return code', 'stdout_li
 nes': [], 'failed_when_result': False, u'start': u'2021-03-12 07:50:27.400156'})
 TASK [rabbitmq_server : Compare installed version of RabbitMQ with new version variable] ***
 TASK [rabbitmq_server : include_tasks] *****************************************
 TASK [rabbitmq_server : include_tasks] *****************************************
 included: /etc/ansible/roles/rabbitmq_server/tasks/install_yum.yml for aio1_rabbit_mq_container-7aeeaf7f
 TASK [rabbitmq_server : Fail if installation method is not 'external_repo'] ****
 TASK [rabbitmq_server : Configure repositories] ********************************
 ok: [aio1_rabbit_mq_container-7aeeaf7f] => (item={u'description': u'RabbitMQ Erlang Packages from Bintray', u'name': u'rabbitmq_els-erlang', u'baseurl'
 : u'https://packagecloud.io/rabbitmq/erlang/el/7/$basearch', u'filename': u'els-erlang'})
 ok: [aio1_rabbit_mq_container-7aeeaf7f] => (item={u'description': u'RabbitMQ Server Rolling Repository', u'name': u'rabbitmq_rabbitmq-server', u'baseur
 l': u'https://packagecloud.io/rabbitmq/rabbitmq-server/el/7/$basearch', u'filename': u'RabbitMQ'})
 TASK [rabbitmq_server : Install RabbitMQ packages] *****************************
 fatal: [aio1_rabbit_mq_container-7aeeaf7f]: FAILED! => {"changed": false, "msg": "No package matching 'erlang-22.1.3-1.el7.x86_64' found available, ins
 talled or updated", "rc": 126, "results": ["No package matching 'erlang-22.1.3-1.el7.x86_64' found available, installed or updated"]}
 PLAY RECAP *********************************************************************
 aio1 : ok=31 changed=0 unreachable=0 failed=0 skipped=19 rescued=0 ignored=0
 aio1_galera_container-dc6e643a : ok=49 changed=0 unreachable=0 failed=0 skipped=6 rescued=0 ignored=0
 aio1_memcached_container-2568ac10 : ok=14 changed=0 unreachable=0 failed=0 skipped=4 rescued=0 ignored=0
 aio1_rabbit_mq_container-7aeeaf7f : ok=16 changed=1 unreachable=0 failed=1 skipped=6 rescued=0 ignored=0
 aio1_repo_container-c0773ddc : ok=26 changed=0 unreachable=0 failed=0 skipped=7 rescued=0 ignored=0
 aio1_utility_container-e84bda78 : ok=44 changed=0 unreachable=0 failed=0 skipped=16 rescued=0 ignored=0
 EXIT NOTICE [Playbook execution failure] **************************************
 + grep -q 'Playbook execution success' setup-infrastructure.out
 + echo 'Failed to run the ansible playbook setup-infrastructure.yml'
 Failed to run the ansible playbook setup-infrastructure.yml
 + sleep 1m
 + (( c++ ))
 + (( c<=4 ))
 + return 1

The procedure is as follows. I am an ONLINE USER.:
 Step0. Quotas(CPUs & Local SSD) are no problem. And add port 5000 in "default-allow-https".
 Step1. gcloud compute instances create openstack-01 --zone us-central1-f --custom-cpu 32 --custom-memory 72GB --min-cpu-platform "Intel Haswell" --image "https://www.googleapis.com/compute/v1/projects/onap-177920/global/images/aarna-aio-openstack-train-centos-7-08062020-00"
 Step2. SSH connect to "openstack-01"
 Step3. To run using the "aarna" account in GCP VM instance:
  sudo usermod -aG wheel aarna
  sudo passwd aarna
  #set password
  sudo su aarna
  sudo ls
  #try sudo
 Step4. cd $HOME/onap-custom/setup-utils
  nohup sudo bash -x aio-centos-gcp-deploy.sh 4 &

How can I deploy successfully?


  • SriramRupanagunta

    Hi, we are looking into this issue. It seems like some dependency is broken in Openstack AIO installation recently. We will update here once we fix it, and also update the documentation.


Upcoming Training