Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status
Hi Tina, The issue is still there. After analyzing it further I have realized that it is a larger problem with the OpenStack deployment. On the last meeting Paul said that he will try taking a look at it and reinstalling using fuel. I think this would be the correct way to go forward and I hope it goes well. Regards, Richard From: opnfv-tech-discuss@lists.opnfv.org on behalf of Tina Tsou Sent: 20 November 2018 04:58:32 To: Tina Tsou Cc: Elias Richard; huangxiangyu; Klozik Martin; opnfv-tech-discuss@lists.opnfv.org; Gary Wu Subject: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Dear Richard et al, Is there still key issue? Thank you, Tina On Nov 12, 2018, at 6:52 AM, Tina Tsou mailto:tina.t...@arm.com>> wrote: Dear Richard et al, It looks like Richard changed the key in the env file, which used to be onap_key, which is keypair in openstack. Thank you, Tina On Nov 9, 2018, at 4:16 AM, Elias Richard mailto:richard.el...@tieto.com>> wrote: Hi Harry, Tina has forwarded me the information below, but this does not solve my issue. The issue I emailed you about is concerning the ssh access into the Openstack VMs, as is shown by this command run by the deploy-onap.sh script: "ssh -o StrictHostKeychecking=no -i /root/.ssh/onap_key ubuntu@172.30.12.114<mailto:ubuntu@172.30.12.114> 'sudo docker ps'" which returns "Permission denied (publickey)." I cannot access the logs without accessing the VMs. I have been going through other public and private keys mentioned in the installation, but still no luck. Could you try connecting to host1 and accessing one of the VMs? Thank you very much, Richard From: Tina Tsou mailto:tina.t...@arm.com>> Sent: 09 November 2018 05:35:16 To: Elias Richard Cc: huangxiangyu; Klozik Martin; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; Gary Wu Subject: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Dear Richard et al, Harry had a look, the docker tag in the environment doesn’t match what’s in the code, you need to look at the log and change accordingly. Thank you, Tina On Nov 5, 2018, at 8:12 AM, Elias Richard mailto:richard.el...@tieto.com>> wrote: Hello, As was recommended by Tina I have added Gary to the conversation. Thank you for the fix Harry, looks like the nbi_docker value was also some problem with the python packages. The VMs do all start up now, but I have problems connecting to them with ssh so I can look over the logs. Even the last command of the deployment script does not complete correctly as it returns a permission problem with the private key. So far I am not sure if it is a problem with the ssh config or if the VMs are not loading the proper ssh public key. Have you encountered this problem? Is there any specific ssh configuration necessary for the pod or ONAP? Thank you very much, Richard From: huangxiangyu mailto:huangxiang...@huawei.com>> Sent: 05 November 2018 08:11:07 To: Elias Richard; Klozik Martin; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Subject: RE: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Richard I have removed the pip.conf for host1. Though pip will still check the local repo first but it can install packages from internet now. There seems no stack at this point and I believed OpenStack components are working functionally. As for nbi_docker, I haven’t met this problem before, maybe you need to find answer from ONAP community Regards Harry 发件人: Elias Richard [mailto:richard.el...@tieto.com] 发送时间: 2018年10月30日 21:36 收件人: Klozik Martin mailto:martin.klo...@tieto.com>>; huangxiangyu mailto:huangxiang...@huawei.com>>; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> 主题: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, I connected to the host and run the commands, but there were problems with the python packages. There was a proxy server set for the pip installation which cannot download the packages. Was there a reason a proxy was necessary for pip? If the packages are already installed the check could probably be skipped. There are also some parts of Openstack that seem to be stuck after the reboot( for example a stack with status:DELETE_FAILED). The teardown script tries to remove this, but as it is stuck there could be problems with the deployment. The creation script itself returns this error: "ERROR: The Parameter (nbi_docker) was not provided." I was not able to find this parameter in any of the templates in ~/onap/integration/test/ete/labs/ so I am not sure what is missing. I started analyzing the problem but I did not want to change anything before asking you for help. Co
Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status
Dear Richard et al, Is there still key issue? Thank you, Tina On Nov 12, 2018, at 6:52 AM, Tina Tsou mailto:tina.t...@arm.com>> wrote: Dear Richard et al, It looks like Richard changed the key in the env file, which used to be onap_key, which is keypair in openstack. Thank you, Tina On Nov 9, 2018, at 4:16 AM, Elias Richard mailto:richard.el...@tieto.com>> wrote: Hi Harry, Tina has forwarded me the information below, but this does not solve my issue. The issue I emailed you about is concerning the ssh access into the Openstack VMs, as is shown by this command run by the deploy-onap.sh script: "ssh -o StrictHostKeychecking=no -i /root/.ssh/onap_key ubuntu@172.30.12.114<mailto:ubuntu@172.30.12.114> 'sudo docker ps'" which returns "Permission denied (publickey)." I cannot access the logs without accessing the VMs. I have been going through other public and private keys mentioned in the installation, but still no luck. Could you try connecting to host1 and accessing one of the VMs? Thank you very much, Richard From: Tina Tsou mailto:tina.t...@arm.com>> Sent: 09 November 2018 05:35:16 To: Elias Richard Cc: huangxiangyu; Klozik Martin; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; Gary Wu Subject: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Dear Richard et al, Harry had a look, the docker tag in the environment doesn’t match what’s in the code, you need to look at the log and change accordingly. Thank you, Tina On Nov 5, 2018, at 8:12 AM, Elias Richard mailto:richard.el...@tieto.com>> wrote: Hello, As was recommended by Tina I have added Gary to the conversation. Thank you for the fix Harry, looks like the nbi_docker value was also some problem with the python packages. The VMs do all start up now, but I have problems connecting to them with ssh so I can look over the logs. Even the last command of the deployment script does not complete correctly as it returns a permission problem with the private key. So far I am not sure if it is a problem with the ssh config or if the VMs are not loading the proper ssh public key. Have you encountered this problem? Is there any specific ssh configuration necessary for the pod or ONAP? Thank you very much, Richard From: huangxiangyu mailto:huangxiang...@huawei.com>> Sent: 05 November 2018 08:11:07 To: Elias Richard; Klozik Martin; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Subject: RE: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Richard I have removed the pip.conf for host1. Though pip will still check the local repo first but it can install packages from internet now. There seems no stack at this point and I believed OpenStack components are working functionally. As for nbi_docker, I haven’t met this problem before, maybe you need to find answer from ONAP community Regards Harry 发件人: Elias Richard [mailto:richard.el...@tieto.com] 发送时间: 2018年10月30日 21:36 收件人: Klozik Martin mailto:martin.klo...@tieto.com>>; huangxiangyu mailto:huangxiang...@huawei.com>>; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> 主题: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, I connected to the host and run the commands, but there were problems with the python packages. There was a proxy server set for the pip installation which cannot download the packages. Was there a reason a proxy was necessary for pip? If the packages are already installed the check could probably be skipped. There are also some parts of Openstack that seem to be stuck after the reboot( for example a stack with status:DELETE_FAILED). The teardown script tries to remove this, but as it is stuck there could be problems with the deployment. The creation script itself returns this error: "ERROR: The Parameter (nbi_docker) was not provided." I was not able to find this parameter in any of the templates in ~/onap/integration/test/ete/labs/ so I am not sure what is missing. I started analyzing the problem but I did not want to change anything before asking you for help. Could you please take a look at it and share any insights you have? Thank you very much, Richard From: Klozik Martin Sent: 29 October 2018 14:36:37 To: huangxiangyu; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Cc: Elias Richard Subject: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status adding Richard to the loop... --Martin Od: opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> mailto:opnfv-tech-discuss@lists.opnfv.org>> za uživatele Klozik Martin mailto:martin.klo...@tieto.com>> Odesláno: stře
Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status
Dear Richard et al, It looks like Richard changed the key in the env file, which used to be onap_key, which is keypair in openstack. Thank you, Tina On Nov 9, 2018, at 4:16 AM, Elias Richard mailto:richard.el...@tieto.com>> wrote: Hi Harry, Tina has forwarded me the information below, but this does not solve my issue. The issue I emailed you about is concerning the ssh access into the Openstack VMs, as is shown by this command run by the deploy-onap.sh script: "ssh -o StrictHostKeychecking=no -i /root/.ssh/onap_key ubuntu@172.30.12.114<mailto:ubuntu@172.30.12.114> 'sudo docker ps'" which returns "Permission denied (publickey)." I cannot access the logs without accessing the VMs. I have been going through other public and private keys mentioned in the installation, but still no luck. Could you try connecting to host1 and accessing one of the VMs? Thank you very much, Richard From: Tina Tsou mailto:tina.t...@arm.com>> Sent: 09 November 2018 05:35:16 To: Elias Richard Cc: huangxiangyu; Klozik Martin; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; Gary Wu Subject: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Dear Richard et al, Harry had a look, the docker tag in the environment doesn’t match what’s in the code, you need to look at the log and change accordingly. Thank you, Tina On Nov 5, 2018, at 8:12 AM, Elias Richard mailto:richard.el...@tieto.com>> wrote: Hello, As was recommended by Tina I have added Gary to the conversation. Thank you for the fix Harry, looks like the nbi_docker value was also some problem with the python packages. The VMs do all start up now, but I have problems connecting to them with ssh so I can look over the logs. Even the last command of the deployment script does not complete correctly as it returns a permission problem with the private key. So far I am not sure if it is a problem with the ssh config or if the VMs are not loading the proper ssh public key. Have you encountered this problem? Is there any specific ssh configuration necessary for the pod or ONAP? Thank you very much, Richard From: huangxiangyu mailto:huangxiang...@huawei.com>> Sent: 05 November 2018 08:11:07 To: Elias Richard; Klozik Martin; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Subject: RE: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Richard I have removed the pip.conf for host1. Though pip will still check the local repo first but it can install packages from internet now. There seems no stack at this point and I believed OpenStack components are working functionally. As for nbi_docker, I haven’t met this problem before, maybe you need to find answer from ONAP community Regards Harry 发件人: Elias Richard [mailto:richard.el...@tieto.com] 发送时间: 2018年10月30日 21:36 收件人: Klozik Martin mailto:martin.klo...@tieto.com>>; huangxiangyu mailto:huangxiang...@huawei.com>>; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> 主题: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, I connected to the host and run the commands, but there were problems with the python packages. There was a proxy server set for the pip installation which cannot download the packages. Was there a reason a proxy was necessary for pip? If the packages are already installed the check could probably be skipped. There are also some parts of Openstack that seem to be stuck after the reboot( for example a stack with status:DELETE_FAILED). The teardown script tries to remove this, but as it is stuck there could be problems with the deployment. The creation script itself returns this error: "ERROR: The Parameter (nbi_docker) was not provided." I was not able to find this parameter in any of the templates in ~/onap/integration/test/ete/labs/ so I am not sure what is missing. I started analyzing the problem but I did not want to change anything before asking you for help. Could you please take a look at it and share any insights you have? Thank you very much, Richard From: Klozik Martin Sent: 29 October 2018 14:36:37 To: huangxiangyu; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Cc: Elias Richard Subject: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status adding Richard to the loop... --Martin Od: opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> mailto:opnfv-tech-discuss@lists.opnfv.org>> za uživatele Klozik Martin mailto:martin.klo...@tieto.com>> Odesláno: středa 24. října 2018 8:00 Komu: huangxiangyu; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Předmět: Re: [op
Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status
Hi Harry, Tina has forwarded me the information below, but this does not solve my issue. The issue I emailed you about is concerning the ssh access into the Openstack VMs, as is shown by this command run by the deploy-onap.sh script: "ssh -o StrictHostKeychecking=no -i /root/.ssh/onap_key ubuntu@172.30.12.114 'sudo docker ps'" which returns "Permission denied (publickey)." I cannot access the logs without accessing the VMs. I have been going through other public and private keys mentioned in the installation, but still no luck. Could you try connecting to host1 and accessing one of the VMs? Thank you very much, Richard From: Tina Tsou Sent: 09 November 2018 05:35:16 To: Elias Richard Cc: huangxiangyu; Klozik Martin; opnfv-tech-discuss@lists.opnfv.org; Gary Wu Subject: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Dear Richard et al, Harry had a look, the docker tag in the environment doesn’t match what’s in the code, you need to look at the log and change accordingly. Thank you, Tina On Nov 5, 2018, at 8:12 AM, Elias Richard mailto:richard.el...@tieto.com>> wrote: Hello, As was recommended by Tina I have added Gary to the conversation. Thank you for the fix Harry, looks like the nbi_docker value was also some problem with the python packages. The VMs do all start up now, but I have problems connecting to them with ssh so I can look over the logs. Even the last command of the deployment script does not complete correctly as it returns a permission problem with the private key. So far I am not sure if it is a problem with the ssh config or if the VMs are not loading the proper ssh public key. Have you encountered this problem? Is there any specific ssh configuration necessary for the pod or ONAP? Thank you very much, Richard From: huangxiangyu mailto:huangxiang...@huawei.com>> Sent: 05 November 2018 08:11:07 To: Elias Richard; Klozik Martin; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Subject: RE: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Richard I have removed the pip.conf for host1. Though pip will still check the local repo first but it can install packages from internet now. There seems no stack at this point and I believed OpenStack components are working functionally. As for nbi_docker, I haven’t met this problem before, maybe you need to find answer from ONAP community Regards Harry 发件人: Elias Richard [mailto:richard.el...@tieto.com] 发送时间: 2018年10月30日 21:36 收件人: Klozik Martin mailto:martin.klo...@tieto.com>>; huangxiangyu mailto:huangxiang...@huawei.com>>; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> 主题: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, I connected to the host and run the commands, but there were problems with the python packages. There was a proxy server set for the pip installation which cannot download the packages. Was there a reason a proxy was necessary for pip? If the packages are already installed the check could probably be skipped. There are also some parts of Openstack that seem to be stuck after the reboot( for example a stack with status:DELETE_FAILED). The teardown script tries to remove this, but as it is stuck there could be problems with the deployment. The creation script itself returns this error: "ERROR: The Parameter (nbi_docker) was not provided." I was not able to find this parameter in any of the templates in ~/onap/integration/test/ete/labs/ so I am not sure what is missing. I started analyzing the problem but I did not want to change anything before asking you for help. Could you please take a look at it and share any insights you have? Thank you very much, Richard From: Klozik Martin Sent: 29 October 2018 14:36:37 To: huangxiangyu; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Cc: Elias Richard Subject: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status adding Richard to the loop... --Martin Od: opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> mailto:opnfv-tech-discuss@lists.opnfv.org>> za uživatele Klozik Martin mailto:martin.klo...@tieto.com>> Odesláno: středa 24. října 2018 8:00 Komu: huangxiangyu; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Předmět: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, thank you for the hints, we will go ahead with ONAP re-deployment as suggested. Best Regards, Martin Od: huangxiangyu mailto:huangxiang...@huawei.com>> Odesláno: středa 24. října 2018 5:01:37 Komu: Klozik Martin; opnfv-tech-discuss@lists.opnfv.org<mailto:
Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status
Dear Richard et al, Harry had a look, the docker tag in the environment doesn’t match what’s in the code, you need to look at the log and change accordingly. Thank you, Tina On Nov 5, 2018, at 8:12 AM, Elias Richard mailto:richard.el...@tieto.com>> wrote: Hello, As was recommended by Tina I have added Gary to the conversation. Thank you for the fix Harry, looks like the nbi_docker value was also some problem with the python packages. The VMs do all start up now, but I have problems connecting to them with ssh so I can look over the logs. Even the last command of the deployment script does not complete correctly as it returns a permission problem with the private key. So far I am not sure if it is a problem with the ssh config or if the VMs are not loading the proper ssh public key. Have you encountered this problem? Is there any specific ssh configuration necessary for the pod or ONAP? Thank you very much, Richard From: huangxiangyu mailto:huangxiang...@huawei.com>> Sent: 05 November 2018 08:11:07 To: Elias Richard; Klozik Martin; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Subject: RE: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Richard I have removed the pip.conf for host1. Though pip will still check the local repo first but it can install packages from internet now. There seems no stack at this point and I believed OpenStack components are working functionally. As for nbi_docker, I haven’t met this problem before, maybe you need to find answer from ONAP community Regards Harry 发件人: Elias Richard [mailto:richard.el...@tieto.com] 发送时间: 2018年10月30日 21:36 收件人: Klozik Martin mailto:martin.klo...@tieto.com>>; huangxiangyu mailto:huangxiang...@huawei.com>>; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> 主题: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, I connected to the host and run the commands, but there were problems with the python packages. There was a proxy server set for the pip installation which cannot download the packages. Was there a reason a proxy was necessary for pip? If the packages are already installed the check could probably be skipped. There are also some parts of Openstack that seem to be stuck after the reboot( for example a stack with status:DELETE_FAILED). The teardown script tries to remove this, but as it is stuck there could be problems with the deployment. The creation script itself returns this error: "ERROR: The Parameter (nbi_docker) was not provided." I was not able to find this parameter in any of the templates in ~/onap/integration/test/ete/labs/ so I am not sure what is missing. I started analyzing the problem but I did not want to change anything before asking you for help. Could you please take a look at it and share any insights you have? Thank you very much, Richard From: Klozik Martin Sent: 29 October 2018 14:36:37 To: huangxiangyu; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Cc: Elias Richard Subject: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status adding Richard to the loop... --Martin Od: opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> mailto:opnfv-tech-discuss@lists.opnfv.org>> za uživatele Klozik Martin mailto:martin.klo...@tieto.com>> Odesláno: středa 24. října 2018 8:00 Komu: huangxiangyu; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Předmět: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, thank you for the hints, we will go ahead with ONAP re-deployment as suggested. Best Regards, Martin Od: huangxiangyu mailto:huangxiang...@huawei.com>> Odesláno: středa 24. října 2018 5:01:37 Komu: Klozik Martin; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Předmět: RE: [Auto] huawei-pod12 ONAP status Hi Martin On host1 you can run the following commands to recreate the ONAP stack: cd /root/onap/integration/test/ete source ./labs/huawei-shanghai/onap-openrc ./scripts/deploy-onap.sh huawei-shanghai These steps will get all onap VMs spinning but all scripts be called inside are pulled from internet where some problems lie. Be aware that there are some docker tag mismatches exist, you will need to manually check the install.log inside VMs to fix them and then call xx_vm_init.sh. Regards Harry 发件人: opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> [mailto:opnfv-tech-discuss@lists.opnfv.org] 代表 Klozik Martin 发送时间: 2018年10月23日 14:16 收件人: huangxiangyu mailto:huangxiang...@huawei.com>>; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@
Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status
Hi Richard I have removed the pip.conf for host1. Though pip will still check the local repo first but it can install packages from internet now. There seems no stack at this point and I believed OpenStack components are working functionally. As for nbi_docker, I haven’t met this problem before, maybe you need to find answer from ONAP community Regards Harry 发件人: Elias Richard [mailto:richard.el...@tieto.com] 发送时间: 2018年10月30日 21:36 收件人: Klozik Martin ; huangxiangyu ; opnfv-tech-discuss@lists.opnfv.org 主题: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, I connected to the host and run the commands, but there were problems with the python packages. There was a proxy server set for the pip installation which cannot download the packages. Was there a reason a proxy was necessary for pip? If the packages are already installed the check could probably be skipped. There are also some parts of Openstack that seem to be stuck after the reboot( for example a stack with status:DELETE_FAILED). The teardown script tries to remove this, but as it is stuck there could be problems with the deployment. The creation script itself returns this error: "ERROR: The Parameter (nbi_docker) was not provided." I was not able to find this parameter in any of the templates in ~/onap/integration/test/ete/labs/ so I am not sure what is missing. I started analyzing the problem but I did not want to change anything before asking you for help. Could you please take a look at it and share any insights you have? Thank you very much, Richard From: Klozik Martin Sent: 29 October 2018 14:36:37 To: huangxiangyu; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Cc: Elias Richard Subject: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status adding Richard to the loop... --Martin Od: opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> mailto:opnfv-tech-discuss@lists.opnfv.org>> za uživatele Klozik Martin mailto:martin.klo...@tieto.com>> Odesláno: středa 24. října 2018 8:00 Komu: huangxiangyu; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Předmět: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, thank you for the hints, we will go ahead with ONAP re-deployment as suggested. Best Regards, Martin Od: huangxiangyu mailto:huangxiang...@huawei.com>> Odesláno: středa 24. října 2018 5:01:37 Komu: Klozik Martin; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Předmět: RE: [Auto] huawei-pod12 ONAP status Hi Martin On host1 you can run the following commands to recreate the ONAP stack: cd /root/onap/integration/test/ete source ./labs/huawei-shanghai/onap-openrc ./scripts/deploy-onap.sh huawei-shanghai These steps will get all onap VMs spinning but all scripts be called inside are pulled from internet where some problems lie. Be aware that there are some docker tag mismatches exist, you will need to manually check the install.log inside VMs to fix them and then call xx_vm_init.sh. Regards Harry 发件人: opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> [mailto:opnfv-tech-discuss@lists.opnfv.org] 代表 Klozik Martin 发送时间: 2018年10月23日 14:16 收件人: huangxiangyu mailto:huangxiang...@huawei.com>>; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> 主题: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, after the power down of huawei-pod12 we are facing an issue with the ONAP installation. The Onap VMs are seen as running by OpenStack, but all of them have failed to boot the kernel and are hanging in the initramfs. Paul did some investigation and he has found out, that it is possible to boot vm manually, it means, that kernel will boot properly. He did some quick checks and it is not clear to us, why VMs can't be boot properly by the OpenStack. Have you seen similar issue in the past, e.g. at any other huawei server after the recent power down? We have a suspicion, that some OS configuration performed during installation was not hardened in the configuration files and thus it was lost after the pod was powered down. We will be grateful for any hints, so we can bring the ONAP installation up and running again. I'm also wondering if you have any notes about the OS and ONAP installation. We can access the bash history, but it is not clear if all performed activities are really necessary. It would be great if you will document the steps required to have OS deployed. I suppose, that for documentation of ONAP installation, we have to ask Gary, am I right? Thank you, Martin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22280): http
Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status
Hello Harry, Did you have time to look into this? Thanks, Richard From: opnfv-tech-discuss@lists.opnfv.org on behalf of Elias Richard Sent: 30 October 2018 14:35:45 To: Klozik Martin; huangxiangyu; opnfv-tech-discuss@lists.opnfv.org Subject: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, I connected to the host and run the commands, but there were problems with the python packages. There was a proxy server set for the pip installation which cannot download the packages. Was there a reason a proxy was necessary for pip? If the packages are already installed the check could probably be skipped. There are also some parts of Openstack that seem to be stuck after the reboot( for example a stack with status:DELETE_FAILED). The teardown script tries to remove this, but as it is stuck there could be problems with the deployment. The creation script itself returns this error: "ERROR: The Parameter (nbi_docker) was not provided." I was not able to find this parameter in any of the templates in ~/onap/integration/test/ete/labs/ so I am not sure what is missing. I started analyzing the problem but I did not want to change anything before asking you for help. Could you please take a look at it and share any insights you have? Thank you very much, Richard From: Klozik Martin Sent: 29 October 2018 14:36:37 To: huangxiangyu; opnfv-tech-discuss@lists.opnfv.org Cc: Elias Richard Subject: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status adding Richard to the loop... --Martin Od: opnfv-tech-discuss@lists.opnfv.org za uživatele Klozik Martin Odesláno: středa 24. října 2018 8:00 Komu: huangxiangyu; opnfv-tech-discuss@lists.opnfv.org Předmět: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, thank you for the hints, we will go ahead with ONAP re-deployment as suggested. Best Regards, Martin Od: huangxiangyu Odesláno: středa 24. října 2018 5:01:37 Komu: Klozik Martin; opnfv-tech-discuss@lists.opnfv.org Předmět: RE: [Auto] huawei-pod12 ONAP status Hi Martin On host1 you can run the following commands to recreate the ONAP stack: cd /root/onap/integration/test/ete source ./labs/huawei-shanghai/onap-openrc ./scripts/deploy-onap.sh huawei-shanghai These steps will get all onap VMs spinning but all scripts be called inside are pulled from internet where some problems lie. Be aware that there are some docker tag mismatches exist, you will need to manually check the install.log inside VMs to fix them and then call xx_vm_init.sh. Regards Harry 发件人: opnfv-tech-discuss@lists.opnfv.org [mailto:opnfv-tech-discuss@lists.opnfv.org] 代表 Klozik Martin 发送时间: 2018年10月23日 14:16 收件人: huangxiangyu ; opnfv-tech-discuss@lists.opnfv.org 主题: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, after the power down of huawei-pod12 we are facing an issue with the ONAP installation. The Onap VMs are seen as running by OpenStack, but all of them have failed to boot the kernel and are hanging in the initramfs. Paul did some investigation and he has found out, that it is possible to boot vm manually, it means, that kernel will boot properly. He did some quick checks and it is not clear to us, why VMs can't be boot properly by the OpenStack. Have you seen similar issue in the past, e.g. at any other huawei server after the recent power down? We have a suspicion, that some OS configuration performed during installation was not hardened in the configuration files and thus it was lost after the pod was powered down. We will be grateful for any hints, so we can bring the ONAP installation up and running again. I'm also wondering if you have any notes about the OS and ONAP installation. We can access the bash history, but it is not clear if all performed activities are really necessary. It would be great if you will document the steps required to have OS deployed. I suppose, that for documentation of ONAP installation, we have to ask Gary, am I right? Thank you, Martin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22258): https://lists.opnfv.org/g/opnfv-tech-discuss/message/22258 Mute This Topic: https://lists.opnfv.org/mt/27566007/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status
Hi Harry, I connected to the host and run the commands, but there were problems with the python packages. There was a proxy server set for the pip installation which cannot download the packages. Was there a reason a proxy was necessary for pip? If the packages are already installed the check could probably be skipped. There are also some parts of Openstack that seem to be stuck after the reboot( for example a stack with status:DELETE_FAILED). The teardown script tries to remove this, but as it is stuck there could be problems with the deployment. The creation script itself returns this error: "ERROR: The Parameter (nbi_docker) was not provided." I was not able to find this parameter in any of the templates in ~/onap/integration/test/ete/labs/ so I am not sure what is missing. I started analyzing the problem but I did not want to change anything before asking you for help. Could you please take a look at it and share any insights you have? Thank you very much, Richard From: Klozik Martin Sent: 29 October 2018 14:36:37 To: huangxiangyu; opnfv-tech-discuss@lists.opnfv.org Cc: Elias Richard Subject: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status adding Richard to the loop... --Martin Od: opnfv-tech-discuss@lists.opnfv.org za uživatele Klozik Martin Odesláno: středa 24. října 2018 8:00 Komu: huangxiangyu; opnfv-tech-discuss@lists.opnfv.org Předmět: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, thank you for the hints, we will go ahead with ONAP re-deployment as suggested. Best Regards, Martin Od: huangxiangyu Odesláno: středa 24. října 2018 5:01:37 Komu: Klozik Martin; opnfv-tech-discuss@lists.opnfv.org Předmět: RE: [Auto] huawei-pod12 ONAP status Hi Martin On host1 you can run the following commands to recreate the ONAP stack: cd /root/onap/integration/test/ete source ./labs/huawei-shanghai/onap-openrc ./scripts/deploy-onap.sh huawei-shanghai These steps will get all onap VMs spinning but all scripts be called inside are pulled from internet where some problems lie. Be aware that there are some docker tag mismatches exist, you will need to manually check the install.log inside VMs to fix them and then call xx_vm_init.sh. Regards Harry 发件人: opnfv-tech-discuss@lists.opnfv.org [mailto:opnfv-tech-discuss@lists.opnfv.org] 代表 Klozik Martin 发送时间: 2018年10月23日 14:16 收件人: huangxiangyu ; opnfv-tech-discuss@lists.opnfv.org 主题: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, after the power down of huawei-pod12 we are facing an issue with the ONAP installation. The Onap VMs are seen as running by OpenStack, but all of them have failed to boot the kernel and are hanging in the initramfs. Paul did some investigation and he has found out, that it is possible to boot vm manually, it means, that kernel will boot properly. He did some quick checks and it is not clear to us, why VMs can't be boot properly by the OpenStack. Have you seen similar issue in the past, e.g. at any other huawei server after the recent power down? We have a suspicion, that some OS configuration performed during installation was not hardened in the configuration files and thus it was lost after the pod was powered down. We will be grateful for any hints, so we can bring the ONAP installation up and running again. I'm also wondering if you have any notes about the OS and ONAP installation. We can access the bash history, but it is not clear if all performed activities are really necessary. It would be great if you will document the steps required to have OS deployed. I suppose, that for documentation of ONAP installation, we have to ask Gary, am I right? Thank you, Martin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22234): https://lists.opnfv.org/g/opnfv-tech-discuss/message/22234 Mute This Topic: https://lists.opnfv.org/mt/27566007/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status
adding Richard to the loop... --Martin Od: opnfv-tech-discuss@lists.opnfv.org za uživatele Klozik Martin Odesláno: středa 24. října 2018 8:00 Komu: huangxiangyu; opnfv-tech-discuss@lists.opnfv.org Předmět: Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, thank you for the hints, we will go ahead with ONAP re-deployment as suggested. Best Regards, Martin Od: huangxiangyu Odesláno: středa 24. října 2018 5:01:37 Komu: Klozik Martin; opnfv-tech-discuss@lists.opnfv.org Předmět: RE: [Auto] huawei-pod12 ONAP status Hi Martin On host1 you can run the following commands to recreate the ONAP stack: cd /root/onap/integration/test/ete source ./labs/huawei-shanghai/onap-openrc ./scripts/deploy-onap.sh huawei-shanghai These steps will get all onap VMs spinning but all scripts be called inside are pulled from internet where some problems lie. Be aware that there are some docker tag mismatches exist, you will need to manually check the install.log inside VMs to fix them and then call xx_vm_init.sh. Regards Harry 发件人: opnfv-tech-discuss@lists.opnfv.org [mailto:opnfv-tech-discuss@lists.opnfv.org] 代表 Klozik Martin 发送时间: 2018年10月23日 14:16 收件人: huangxiangyu ; opnfv-tech-discuss@lists.opnfv.org 主题: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, after the power down of huawei-pod12 we are facing an issue with the ONAP installation. The Onap VMs are seen as running by OpenStack, but all of them have failed to boot the kernel and are hanging in the initramfs. Paul did some investigation and he has found out, that it is possible to boot vm manually, it means, that kernel will boot properly. He did some quick checks and it is not clear to us, why VMs can't be boot properly by the OpenStack. Have you seen similar issue in the past, e.g. at any other huawei server after the recent power down? We have a suspicion, that some OS configuration performed during installation was not hardened in the configuration files and thus it was lost after the pod was powered down. We will be grateful for any hints, so we can bring the ONAP installation up and running again. I'm also wondering if you have any notes about the OS and ONAP installation. We can access the bash history, but it is not clear if all performed activities are really necessary. It would be great if you will document the steps required to have OS deployed. I suppose, that for documentation of ONAP installation, we have to ask Gary, am I right? Thank you, Martin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#7): https://lists.opnfv.org/g/opnfv-tech-discuss/message/7 Mute This Topic: https://lists.opnfv.org/mt/27566007/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status
Hi Harry, thank you for the hints, we will go ahead with ONAP re-deployment as suggested. Best Regards, Martin Od: huangxiangyu Odesláno: středa 24. října 2018 5:01:37 Komu: Klozik Martin; opnfv-tech-discuss@lists.opnfv.org Předmět: RE: [Auto] huawei-pod12 ONAP status Hi Martin On host1 you can run the following commands to recreate the ONAP stack: cd /root/onap/integration/test/ete source ./labs/huawei-shanghai/onap-openrc ./scripts/deploy-onap.sh huawei-shanghai These steps will get all onap VMs spinning but all scripts be called inside are pulled from internet where some problems lie. Be aware that there are some docker tag mismatches exist, you will need to manually check the install.log inside VMs to fix them and then call xx_vm_init.sh. Regards Harry 发件人: opnfv-tech-discuss@lists.opnfv.org [mailto:opnfv-tech-discuss@lists.opnfv.org] 代表 Klozik Martin 发送时间: 2018年10月23日 14:16 收件人: huangxiangyu ; opnfv-tech-discuss@lists.opnfv.org 主题: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, after the power down of huawei-pod12 we are facing an issue with the ONAP installation. The Onap VMs are seen as running by OpenStack, but all of them have failed to boot the kernel and are hanging in the initramfs. Paul did some investigation and he has found out, that it is possible to boot vm manually, it means, that kernel will boot properly. He did some quick checks and it is not clear to us, why VMs can't be boot properly by the OpenStack. Have you seen similar issue in the past, e.g. at any other huawei server after the recent power down? We have a suspicion, that some OS configuration performed during installation was not hardened in the configuration files and thus it was lost after the pod was powered down. We will be grateful for any hints, so we can bring the ONAP installation up and running again. I'm also wondering if you have any notes about the OS and ONAP installation. We can access the bash history, but it is not clear if all performed activities are really necessary. It would be great if you will document the steps required to have OS deployed. I suppose, that for documentation of ONAP installation, we have to ask Gary, am I right? Thank you, Martin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22210): https://lists.opnfv.org/g/opnfv-tech-discuss/message/22210 Mute This Topic: https://lists.opnfv.org/mt/27566007/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status
Hi Martin On host1 you can run the following commands to recreate the ONAP stack: cd /root/onap/integration/test/ete source ./labs/huawei-shanghai/onap-openrc ./scripts/deploy-onap.sh huawei-shanghai These steps will get all onap VMs spinning but all scripts be called inside are pulled from internet where some problems lie. Be aware that there are some docker tag mismatches exist, you will need to manually check the install.log inside VMs to fix them and then call xx_vm_init.sh. Regards Harry 发件人: opnfv-tech-discuss@lists.opnfv.org [mailto:opnfv-tech-discuss@lists.opnfv.org] 代表 Klozik Martin 发送时间: 2018年10月23日 14:16 收件人: huangxiangyu ; opnfv-tech-discuss@lists.opnfv.org 主题: [opnfv-tech-discuss] [Auto] huawei-pod12 ONAP status Hi Harry, after the power down of huawei-pod12 we are facing an issue with the ONAP installation. The Onap VMs are seen as running by OpenStack, but all of them have failed to boot the kernel and are hanging in the initramfs. Paul did some investigation and he has found out, that it is possible to boot vm manually, it means, that kernel will boot properly. He did some quick checks and it is not clear to us, why VMs can't be boot properly by the OpenStack. Have you seen similar issue in the past, e.g. at any other huawei server after the recent power down? We have a suspicion, that some OS configuration performed during installation was not hardened in the configuration files and thus it was lost after the pod was powered down. We will be grateful for any hints, so we can bring the ONAP installation up and running again. I'm also wondering if you have any notes about the OS and ONAP installation. We can access the bash history, but it is not clear if all performed activities are really necessary. It would be great if you will document the steps required to have OS deployed. I suppose, that for documentation of ONAP installation, we have to ask Gary, am I right? Thank you, Martin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22209): https://lists.opnfv.org/g/opnfv-tech-discuss/message/22209 Mute This Topic: https://lists.opnfv.org/mt/27566007/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
