2 answers
- 10-1
I got this working by editing the "aai2_install.sh" script .
Line number 95 : "git clone -b $GERRIT_BRANCH --single-branch http://gerrit.onap.org/r/aai/test-config"
changed line number 95 to : "git clone http://gerrit.onap.org/r/aai/test-config" .
Before it was failing at line number 95 with below error:
~# git clone -b release-1.0.0 --single-branch http://gerrit.onap.org/r/aai/test-config
Cloning into 'test-config'...
warning: Could not find remote branch release-1.0.0 to clone.
fatal: Remote branch release-1.0.0 not found in upstream originNow after changing the script, above error is not seen. Containers are spawned and AAI functionality is working fine.
Thanks.
Add your comment... - 10-1
it should be resolved now, please try agian
- kranthi guttikonda
It works now
- Chandrakiran Barad
It is not working for me . I re ran ./aai2_install.sh and seeing same error.
- Chandrakiran Barad
kranthi guttikonda Please share the link to view ONAP Helpdesk #41973. I cannot find it in Jira.
- kranthi guttikonda
Chandrakiran Barad, my setup don't have two AAI VMs. I am using vanilla openstack setup not rackspace and it works for me now.
- Chandrakiran Barad
kranthi guttikonda Yes i am also using vanilla openstack - newton release. I have used "onap_openstack_float.yaml / onap_openstack_float.env" for ONAP installation. With present yaml file it has 2 AAI VMs.
- Chandrakiran Barad
kranthi guttikonda can you please share output of docker ps -a command on AAI VM. Just want to know how many containers are created. For me no containers are spawned.
- Chandrakiran Barad
root@vm1-aai-inst2:/opt# git clone -b release-1.0.0 --single-branch http://gerrit.onap.org/r/aai/test-config
Cloning into 'test-config'...
warning: Could not find remote branch release-1.0.0 to clone.
fatal: Remote branch release-1.0.0 not found in upstream origin
root@vm1-aai-inst2:/opt# Unexpected end of command streamDaniel Rose - Can you please look into this ? remote branch release-1.0.0 is not accessible from AAI VM.
- kranthi guttikonda
Chandrakiran Barad I have used openstack + contrail (so no floating ip). Are you seeing this problem with only AAI not with any other service?
root@vm1-aai:~# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5f2edc06f415 nexus3.onap.org:10001/openecomp/ajsc-aai:latest "/bin/sh -c ./star..." 6 days ago Up 6 days aai-service
278974a41cd6 aaidocker/aai-hbase-1.2.3 "/bin/bash /opt/en..." 2 weeks ago Up 2 weeks hbase-1.2.3
40256f879ba2 nexus3.onap.org:10001/openecomp/model-loader:1.0-STAGING-latest "/bin/sh -c /opt/j..." 2 weeks ago Up 2 weeks model-loader-service
root@vm1-aai:~# - Daniel Rose
aai release 1.1 has 2 vms, aai release 1.0 has 1 vm
- kranthi guttikonda
Oh Thanks Daniel Rose. So, 1.1 requires different heat template?
- Daniel Rose
vs
master is release 1.1 and has more options including one that works on vanilla openstack.
- kranthi guttikonda
Thank you Daniel Rose There are quite a differences in heat templates and scripts for AAI and DCAE (well may be in others). Which one do you suggest to you? Are you planning to release the current master as an another release like 1.1.0 or something?
- Daniel Rose
i dont know the exact release plan but at some point there will be a release of all the code in master branch. We run CI against 1.0.0 now so that is best if you have rackspace. If you are using vanilla openstack it has to be master branch float heat stack but there is some risk somethings wont work
- kranthi guttikonda
Thanks Daniel Rose What is your recommendation setup like MOS + Contrail? Currently I am using 1.0.0 vanilla openstack heat templates (not float). Only pending work is with DCAE
- Daniel Rose
master branch float template is the best one for that i believe
- Chandrakiran Barad
Yes @kranthi guttikonda, I am seeing this issue only with aai vms. Other services are working fine.
Add your comment...
I have installed ONAP, after installation i check both AAI vms (vm1-aai-inst1 and vm1-aai-inst2) there were no docker containers created. I tried to run "aai2_install.sh" script manually on "vm1-aai-inst1" it failed with below error :
Building dependency tree
Reading state information... Done
docker-engine is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
mkdir: cannot create directory ‘/opt/docker’: File exists
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 617 0 617 0 0 617 0 --:--:-- --:--:-- --:--:-- 617
100 7857k 100 7857k 0 0 437k 0 0:00:17 0:00:17 --:--:-- 1478k
docker stop/waiting
docker start/running, process 26955
Cloning into 'test-config'...
warning: Could not find remote branch release-1.0.0 to clone.
fatal: Remote branch release-1.0.0 not found in upstream origin
Unexpected end of command stream
./aai2_vm_init.sh: line 5: cd: /opt/test-config: No such file or directory
fatal: Not a git repository (or any of the parent directories): .git
./aai2_vm_init.sh: line 10: ./deploy_vm1.sh: No such file or directory
After this there are no docker containers created on both aai vms.
Can any one help me here to solve this issue.
Chandrakiran Barad Its because the repos at Nexus are down. Until it resolves heat scripts will fail to download initial startup scripts and also docker images pull. Please look into following question
docker pull fails for latest/1.0-STAGING-latest all of sudden
ok thanks kranthi guttikonda . I think some repos at nexus are still down.