Listing upper-constraints doesn’t mean that it will be installed. It only enforces the right version.
Functest doesn’t leverage on it then why should we force the installation in our container? It must be installed as any parser dependency when installing your package. I can modify your requirements.txt if it helps. Cédric De : shang.xiaod...@zte.com.cn [mailto:shang.xiaod...@zte.com.cn] Envoyé : lundi 11 décembre 2017 10:23 À : OLLIVIER Cédric IMT/OLN Cc : ollivier.ced...@gmail.com; feng.xiao...@zte.com.cn; opnfv-helpd...@rt.linuxfoundation.org; opnfv-tech-discuss@lists.opnfv.org Objet : 答复: RE: [opnfv-tech-discuss] Hi, ollivier and functest team, one test issue from community CI. python-openstackclient is already included in the file of upper-constraints.txt( https://git.opnestack.org/cgit/openstack/requirements/plain/upper-constrains.txt) which is used in functest/core dockefile. and i notice that all the other clients(nova,neutron,cinder.etc) are installed except opnestack client. In addition. in my opinion openstack client is a common requirement for all feature projects. 尚小冬 shangxiaodong 原始邮件 发件人： <cedric.olliv...@orange.com<mailto:cedric.olliv...@orange.com>>; 收件人：尚小冬10032185; <ollivier.ced...@gmail.com<mailto:ollivier.ced...@gmail.com>>; 抄送人：冯晓伟00125593; <opnfv-helpd...@rt.linuxfoundation.org<mailto:opnfv-helpd...@rt.linuxfoundation.org>>; <opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>; 日 期 ：2017年12月11日 16:52 主 题 ：RE: [opnfv-tech-discuss] Hi, ollivier and functest team, one test issue from community CI. Hello, It should have been added as dependency (requirements.txt) in your python package. I don’t want to list it in the Dockerfile to bypass your issue. Cédric De : opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] De la part de shang.xiaod...@zte.com.cn<mailto:shang.xiaod...@zte.com.cn> Envoyé : lundi 11 décembre 2017 10:00 À : ollivier.ced...@gmail.com<mailto:ollivier.ced...@gmail.com> Cc : feng.xiao...@zte.com.cn<mailto:feng.xiao...@zte.com.cn>; opnfv-helpd...@rt.linuxfoundation.org<mailto:opnfv-helpd...@rt.linuxfoundation.org>; opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Objet : [opnfv-tech-discuss] Hi, ollivier and functest team, one test issue from community CI. I consider the following ci functest test result about parser project in master branch. ======================={ Parser functest begin }========================== |========= 1/4. Preparing VM image for parser... =========| Download image cirros-0.3.5-x86_64-disk.img... ./functest_run.sh: line 72: openstack: command not found Registe image cirros-0.3.2-x86_64-uec... ./functest_run.sh: line 79: openstack: command not found Clean-up the environment... ./functest_run.sh: line 243: openstack: command not found Delete local image file cirros-0.3.2-x86_64-uec.img after test. Delete local URL image file cirros-0.3.5-x86_64-disk.img after test. ./functest_run.sh: line 275: openstack: command not found Delete user parser's role from project parser ./functest_run.sh: line 283: openstack: command not found Delete user parser ./functest_run.sh: line 290: openstack: command not found Delete project parser ./functest_run.sh: line 295: openstack: command not found======================={ Parser functest end }========================== It seems that openstack client is not installed in parser docker image, so i installed python-openstackclient after launching parser container manually in my local enviroment, and the test was successful. Would you please check the dockerfile or scripts in functest? thanks. 尚小冬 shangxiaodong _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
