Hi Gerard, Sorry for the late response. I'll try to respond inline and answer some of your comments.
Tim Rozet Red Hat SDN Team On Wed, Aug 1, 2018 at 8:03 PM Gerard Damm <[email protected]> wrote: > > > Hi, > > > > I wanted to confirm the procedure, but got an error again, and this time > the opnfv-clean command > > did not do the trick: it actually also issued an error (please see details > below). > > > > However, I re-run the installation after exploring post-install scripts > (Install Docker, Install Python) from Mark: > > > https://wiki.opnfv.org/display/storperf/LaaS+Setup+For+Development#LaaSSetupForDevelopment-InstallOPNFVApex > > > > The second opnfv-deploy attempt failed again, but this time opnfv-clean > worked, and a 3rd installation attempt worked. > > > > So I'm thinking there must be some missing/undocumented additional > required setup for Apex (Docker ? Python ?), which may or may not happen > incidentally when doing other things, but which is revealed by running the > procedure for the first time on a brand new server (and maybe is not > revealed on daily CI runs on already configured servers). > > > > Best regards, > > Gerard > > > > > > > > > > > > a) initial error from deploy: > > > > 2018-08-01 17:43:27,073 INFO: TASK [systemd] > ***************************************************************** > > task path: > /usr/share/opnfv-apex/ansible/playbooks/deploy_dependencies.yml:25 > > fatal: [localhost]: FAILED! => {"changed": false, "msg": "Unable to start > service openvswitch: A dependency job for openvswitch.service failed. See > 'journalctl -xe' for details. > > "} > > to retry, use: --limit > @/usr/share/opnfv-apex/ansible/playbooks/deploy_dependencies.retry > > > > > > 2018-08-01 17:43:27,073 INFO: PLAY RECAP > ********************************************************************* > > localhost : ok=5 changed=0 unreachable=0 failed=1 > > > > > > 2018-08-01 17:43:27,142 ERROR: Ansible playbook failed. See Ansible logs > for details. > > Traceback (most recent call last): > > File "/bin/opnfv-deploy", line 10, in <module> > > sys.exit(main()) > > File "/usr/lib/python3.4/site-packages/apex/deploy.py", line 312, in main > > 'deploy_dependencies.yml')) > > File "/usr/lib/python3.4/site-packages/apex/common/utils.py", line 141, > in run_ansible > > raise Exception(e) > > Exception: Ansible playbook failed. See Ansible logs for details. > > > > > OpenVswitch was not installed. I'm not sure how this is possible since it is a requirement of the opnfv-apex package itself: https://github.com/opnfv/apex/blob/stable/fraser/build/rpm_specs/opnfv-apex-common.spec#L15 So if you installed the apex RPMs they should have failed if they did not install OVS. > > > > > b) initial error from opnfv-clean: > > > > # opnfv-clean > > 2018-08-01 18:02:45,725 INFO: Destroying all Apex VMs > > libvirt: Storage Driver error : Storage pool not found: no storage pool > with matching name 'default' > > Traceback (most recent call last): > > File "/usr/bin/opnfv-clean", line 10, in <module> > > sys.exit(main()) > > File "/usr/lib/python3.4/site-packages/apex/clean.py", line 146, in main > > clean_vms() > > File "/usr/lib/python3.4/site-packages/apex/clean.py", line 62, in > clean_vms > > pool = conn.storagePoolLookupByName('default') > > File "/usr/lib64/python3.4/site-packages/libvirt.py", line 4589, in > storagePoolLookupByName > > if ret is None:raise libvirtError('virStoragePoolLookupByName() > failed', conn=self) > > libvirt.libvirtError: Storage pool not found: no storage pool with > matching name 'default' > > [root@hpe34 opnfv-TripleO-apex]# > > > This usually happens if for some reason you are missing a default pool in libvirt (virsh pool-list |grep default). You can recreate it manually virsh pool-define-as default dir --target /var/lib/libvirt/images/ virsh pool-autostart default virsh pool-start default We should probably handle this condition and create the default pool for the user if it is missing. We may already do this in the deploy, but not in the clean. I need to check. Feel free to open a bug on that. > > > > > > > c) second installation error: > > > > 2018-08-01 18:28:44,848 INFO: Created machine baremetal0 with UUID > 114d0d22-d384-4a95-a8c3-c58ba2895756 > > 2018-08-01 18:28:44,882 DEBUG: Detected virsh default network ip: > 192.168.122.1 > > Traceback (most recent call last): > > File "/usr/bin/opnfv-deploy", line 10, in <module> > > sys.exit(main()) > > File "/usr/lib/python3.4/site-packages/apex/deploy.py", line 318, in main > > build_vms(inventory, net_settings, args.deploy_dir) > > File "/usr/lib/python3.4/site-packages/apex/deploy.py", line 99, in > build_vms > > virt_utils.host_setup({name: node['pm_port']}) > > File "/usr/lib/python3.4/site-packages/apex/virtual/utils.py", line 132, > in host_setup > > chain = iptc.Chain(iptc.Table(iptc.Table.FILTER), "INPUT") > > File "/usr/lib64/python3.4/site-packages/iptc/ip4tc.py", line 1566, in > __new__ > > obj._init(name, autocommit) > > File "/usr/lib64/python3.4/site-packages/iptc/ip4tc.py", line 1582, in > _init > > self.refresh() > > File "/usr/lib64/python3.4/site-packages/iptc/ip4tc.py", line 1619, in > refresh > > self.strerror())) > > iptc.ip4tc.IPTCError: can't initialize filter: b'iptables who? (do you > need to insmod?)' > > > > > > d) installation success on 3rd run (after successful opnfv-clean): > > > > 2018-08-01 19:56:12,719 INFO: PLAY RECAP > ********************************************************************* > > 192.0.2.15 : ok=4 changed=3 unreachable=0 failed=0 > > > > > > 2018-08-01 19:56:12,795 INFO: Post Deploy Overcloud Configuration Complete > for node overcloud-novacompute-3 > > 2018-08-01 19:56:12,796 INFO: Apex deployment complete > > 2018-08-01 19:56:12,796 INFO: Undercloud IP: 192.168.122.24, please > connect by doing 'opnfv-util undercloud' > > > > > Looks like this bug: https://jira.opnfv.org/browse/APEX-521 > > 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 (#21710): https://lists.opnfv.org/g/opnfv-tech-discuss/message/21710 Mute This Topic: https://lists.opnfv.org/mt/23827274/21656 Group Owner: [email protected] Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
