Hi Gerard, I did a few checks today with following outcome:
* (HPE15) installation with VIRT_NUMBER=1 does not pass "reboot_hosts" stage, it simply terminates after this messages is shown; that's why I was not able to see anything else yesterday * (HPE15) installation with VIRT_NUMBER=2 went correctly (i.e. I see the "Installation Complete!" banner :-)) * I tried to retest it (with VIRT_NUMBER=2) at "clean" server HPE16 and I hit the same issue as you did (i.e. RuntimeError: OS installation timeout) I'm wondering if it can be related to the OS state. May be we should firstly try to do an apt update & upgrade (may be even followed by the sever reboot), before execution of compass installation. I'll give it a try at another server. One additional question. How did you "installed" opnfv-clean binary at your server? I've used alien to create a deb package from http://artifacts.opnfv.org/apex/master/opnfv-apex-common-2.1-20160306.noarch.rpm. After its installation at HPE15, I was able to execute opnfv-clean, but I doubt that it works. So I'm wondering if it is enough to install this package or other two rpms/debs are also required (in that case I would expect that such dependency would be enforced by package spec file...). BTW, I did a small updates to your compass install script. May be it's time to comment out one of the options, so it is directly usable for OPNFV deployment at LaaS server. What do you think? Cheers, Martin Od: gerard.d...@wipro.com <gerard.d...@wipro.com> Odesláno: středa 1. srpna 2018 23:20 Komu: opnfv-tech-discuss@lists.opnfv.org Kopie: huangxiangyu; Klozik Martin Předmět: RE: [opnfv-tech-discuss] [compass4nfv][auto] Compass4nfv on LaaS x86 server Hi, Thanks Martin and Harry for your feedback ! On hpe15, the log file doesn't end with the string "compass deploy success", so the process may not have completed correctly. When you reach the point of "reboot_hosts do nothing", it takes quite a while (30-60 minutes ?) to get to the conclusion. Is it possible you stopped the process before it finished ? Also, I didn't see the setting of "VIRT_NUMBER" in the "deploy.sh" file in "/home/opnfv/compass4nfv", but then again it's possible you changed it afterwards. One directory up ("/home/opnfv"), the file "deply.sh.log" ends in "launch_compass failed". Out of curiosity, I tried option 1 on hpe15 (see script in ~/auto) (so: master branch, build+deploy, NOHA scenario, VIRT_NUMBER=2). This one failed with the "get_installing_progress" error. You can check the logs in /opt/opnfv-compass/compass4nfv, and in ~/auto). Best regards, Gerard From: Klozik Martin [mailto:martin.klo...@tieto.com] Sent: Wednesday, August 1, 2018 4:50 AM To: Gerard Damm (Product Engineering Service) <gerard.d...@wipro.com>; opnfv-tech-discuss@lists.opnfv.org Cc: huangxiangyu <huangxiang...@huawei.com> Subject: Re: [opnfv-tech-discuss] [compass4nfv][auto] Compass4nfv on LaaS x86 server ** This mail has been sent from an external source. Treat hyperlinks and attachments in this email with caution** Hi Gerard, I tried to follow your installation procedure (i.e. point 1 below) at HPE15 with the only difference, i.e. VIRT_NUMBER=1. I've not observed the same error as you, but some (probably not fatal) assertion error (search log for client.py). Anyhow the installation process seemed to finish somehow. I plan to have a more detailed look at the machine tomorrow. Feel free to have a look yourself, I'll forward you appropriate credentials. The installation log (output of deploy.sh) is available at /home/opnfv/compass4nfv/deploy.log Have a nice day, Martin Od: opnfv-tech-discuss@lists.opnfv.org <opnfv-tech-discuss@lists.opnfv.org> za uživatele Gerard Damm <gerard.d...@wipro.com> Odesláno: středa 1. srpna 2018 2:06:43 Komu: opnfv-tech-discuss@lists.opnfv.org Kopie: huangxiangyu Předmět: Re: [opnfv-tech-discuss] [compass4nfv][auto] Compass4nfv on LaaS x86 server Thanks for pointing out that other possible issue. The instructions I use as a reference: https://docs.opnfv.org/en/latest/submodules/compass4nfv/docs/release/installation/index.html My spelled out version/script for these instructions (case of virtual deployment on Ubuntu): https://wiki.opnfv.org/display/AUTO/Script%3A+Compass4nfv I did 3 more attempts on hpe32, and unfortunately they also failed: 1) tarball 6.2, stable/fraser branch, noha scenario, set VIRT_NUMBER to 5, deploy.sh 2) quickstart.sh (i.e. in master branch, build.sh, ha scenario, deploy.sh) 3) master branch, build.sh, noha scenario, set VIRT_NUMBER to 5, deploy.sh I got twice with the get_ansible_print error, and once a get_installing_progress error. (details below) At this point, probably the most efficient next step would be for you to try yourself on a LaaS server, write down exactly the sequence of commands you used, so as to find out the missing commands. Then I'll updates my notes, and the compass4nfv docs may also be updated. Best regards, Gerard 1) tarball 6.2, stable/fraser branch, noha scenario, set VIRT_NUMBER to 5, deploy.sh downloaded 6.2 tarball, checked out to stable/fraser, added these lines in deploy.sh (and with noha scenario): export VIRT_NUMBER=5 export VIRT_CPUS=4 export VIRT_MEM=16384 export VIRT_DISK=200G error: Traceback (most recent call last): File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1127, in <module> main() File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1122, in main deploy() File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1076, in deploy ansible_print = client.get_ansible_print() File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 968, in get_ansible_print raise RuntimeError("OS installation timeout") RuntimeError: OS installation timeout + RET=1 + sleep 25 + [[ 1 -eq 0 ]] + /bin/false + exit 1 2) quickstart.sh (i.e. in master branch, build.sh, ha scenario, deploy.sh) error: 2018-07-31 21:57:59,756 p=130 u=root | hostname: host2 2018-07-31 21:57:59,782 p=130 u=root | host=compass-deck,url=/api/clusterhosts/2/state,body={"state": "ERROR"},headers={'Content-type': 'application/json', 'Accept': '*/*', 'X-Auth-Token': '$1$UohR2peC$xirMX8ctPjiZv5d1amTDf/'} 2018-07-31 21:57:59,817 p=130 u=root | notify host status success!!! status=200, body={ "severity": "INFO", "created_at": "2018-07-31 21:37:19", "updated_at": "2018-07-31 21:57:59", "id": 2, "state": "ERROR", "ready": false, "percentage": 0.0, "message": "" } 2018-07-31 21:57:59,818 p=130 u=root | hostname: host1 2018-07-31 21:57:59,845 p=130 u=root | host=compass-deck,url=/api/clusterhosts/1/state,body={"state": "ERROR"},headers={'Content-type': 'application/json', 'Accept': '*/*', 'X-Auth-Token': '$1$F7YoEKlk$1/6TRpRf7crU2U6t8S0lE1'} 2018-07-31 21:57:59,892 p=130 u=root | notify host status success!!! status=200, body={ "severity": "INFO", "created_at": "2018-07-31 21:37:19", "updated_at": "2018-07-31 21:57:59", "id": 1, "state": "ERROR", "ready": false, "percentage": 0.0, "message": "" } Traceback (most recent call last): File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1136, in <module> main() File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1131, in main deploy() File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1086, in deploy client.get_installing_progress(cluster_id, ansible_print) File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1029, in get_installing_progress _get_installing_progress() File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1015, in _get_installing_progress (cluster_id, status, cluster_state) RuntimeError: ('get cluster %s state status %s: %s, error', (1, 200, {u'status': {u'completed_hosts': 0, u'total_hosts': 5, u'installing_hosts': 0, u'failed_hosts': 5}, u'severity': u'ERROR', u'created_at': u'2018-07-31 21:37:19', u'message': u'total 5, installing 0, completed: 0, error 5', u'updated_at': u'2018-07-31 21:57:59', u'state': u'ERROR', u'ready': False, u'percentage': 0.0, u'id': 1})) + RET=1 + sleep 25 + [[ 1 -eq 0 ]] + /bin/false + exit 1 3) master branch, build.sh, noha scenario, set VIRT_NUMBER to 5, deploy.sh error: Traceback (most recent call last): File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1136, in <module> main() File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1131, in main deploy() File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 1085, in deploy ansible_print = client.get_ansible_print() File "/opt/opnfv-compass/compass4nfv/deploy/client.py", line 977, in get_ansible_print raise RuntimeError("OS installation timeout") RuntimeError: OS installation timeout + RET=1 + sleep 25 + [[ 1 -eq 0 ]] + /bin/false + exit 1 From: huangxiangyu [mailto:huangxiang...@huawei.com] Sent: Tuesday, July 31, 2018 2:05 AM To: Gerard Damm (Product Engineering Service) <gerard.d...@wipro.com>; opnfv-tech-discuss@lists.opnfv.org Subject: 答复: [opnfv-tech-discuss] [compass4nfv][auto] Compass4nfv on LaaS x86 server ** This mail has been sent from an external source ** Hi Gerard This Error comes from the missing of variable VIRT_NUMBER. Because in the script, you are using noha scenario (os-nosdn-nofeature-noha.yml) which contains only one controller and one compute. Compass will expect five virtual machines for virtual deploy and user need to export VIRT_NUMBER to specify the number if it’s not 5. BTW, which doc do you follow when testing the compass installer? I will add this operation if there isn’t. Regards Harry The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#21696): https://lists.opnfv.org/g/opnfv-tech-discuss/message/21696 Mute This Topic: https://lists.opnfv.org/mt/23992905/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
