Re: [openstack-dev] sqlalchemy-utils fails devstack install
Sorry, I meant setuptools. -Original Message- From: Angela Smith [mailto:aal...@brocade.com] Sent: Thursday, February 25, 2016 11:21 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] sqlalchemy-utils fails devstack install This bug was opened and the solution presented seems to be accurate: https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.launchpad.net_devstack_-2Bbug_1548592=CwICAg=IL_XqQWOjubgfqINi2jTzg=Ai1MvyPlSw0GLEkv2TxEQpGqXLcFW8njDXhHMBos4Xc=vmbGnExBcDYh5VUlAwMyZOYtWE6xu-WUCH6_xGE0L_k=P4olklj94frFuJOh3sM4P9u2rYfiAw-ussz0xihw1Rc= We had the same issue on our CI and deleting setuputils and reinstalling worked for us. -Original Message- From: Beliveau, Ludovic [mailto:ludovic.beliv...@windriver.com] Sent: Thursday, February 25, 2016 7:18 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] sqlalchemy-utils fails devstack install A bug has been raised against SQLAlchemy-Utils and a fixed has been proposed (but not yet merged): https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_kvesteri_sqlalchemy-2Dutils_pull_193=CwICAg=IL_XqQWOjubgfqINi2jTzg=Ai1MvyPlSw0GLEkv2TxEQpGqXLcFW8njDXhHMBos4Xc=ZPoJUKotO6G2_-zWu_uS-YpGG78LX8oSKkcPN3Wq7jI=kuIoTmjzDeBqjHGE_tKrKQyj5Ei5CsXOp5Tt1OHJb5U= Workaround for running devstack: - Download SQLAlchemy-Utils source code (see https://urldefense.proofpoint.com/v2/url?u=https-3A__sqlalchemy-2Dutils.readthedocs.org_en_latest_installation.html=CwICAg=IL_XqQWOjubgfqINi2jTzg=Ai1MvyPlSw0GLEkv2TxEQpGqXLcFW8njDXhHMBos4Xc=ZPoJUKotO6G2_-zWu_uS-YpGG78LX8oSKkcPN3Wq7jI=mJ8E6bsn0XM-nKHAqgJeEi3tNaQ3gTKwsB6UNjeT3p4= ) - Patch source code locally based on the proposed fix - Install the package Regards, /ludovic On 02/25/2016 08:27 AM, Sean Dague wrote: > On 02/24/2016 11:45 PM, Watanabe, Isao wrote: >> Hello team >> >> Does anyone know about why sqlalchemy-utils fails devstack install since >> about 3:00 UTC, Feb 25th? >> >> Our CI start to fail and in log it says: >> >> 2016-02-25 03:34:22.515 | Collecting SQLAlchemy-Utils===0.31.6 (from -c >> /opt/stack/new/requirements/upper-constraints.txt (line 24)) >> 2016-02-25 03:34:22.602 | Downloading SQLAlchemy-Utils-0.31.6.tar.gz >> (112kB) >> 2016-02-25 03:34:23.031 | Complete output from command python setup.py >> egg_info: >> 2016-02-25 03:34:23.031 | error in SQLAlchemy-Utils setup command: >> 'extras_require' must be a dictionary whose values are strings or lists of >> strings containing valid project/version requirement specifiers. >> 2016-02-25 03:34:23.031 | >> 2016-02-25 03:34:23.031 | >> 2016-02-25 03:34:23.062 | Command "python setup.py egg_info" failed >> with error code 1 in /tmp/pip-build-eRYND2/SQLAlchemy-Utils >> >> However, in mirror[1] which we are using, the package is just there, which >> confused me. >> [1] >> https://urldefense.proofpoint.com/v2/url?u=http-3A__mirror.dfw.rax.op >> enstack.org_pypi_simple_sqlalchemy-2Dutils_=CwICAg=IL_XqQWOjubgfq >> INi2jTzg=Ai1MvyPlSw0GLEkv2TxEQpGqXLcFW8njDXhHMBos4Xc=ZPoJUKotO6G2 >> _-zWu_uS-YpGG78LX8oSKkcPN3Wq7jI=nPN16YBhP8L87MWHLOY9HhlCwA3__riE_6W >> r5yqqaes= >> >> Thanks for any help. >> >> Best regards, >> Watanabe.isao > The failure only exists if you are installing from tar.gz and not from > wheels. For performance reasons the upstream gate builds a wheel > mirror and installs from that. > > Those wheels were built on old setuptools, work on any version. There > is a setuptools bug registered for this, which should hopefully be fixed > today. > > -Sean > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev=CwICAg=IL_XqQWOjubgfqINi2jTzg=Ai1MvyPlSw0GLEkv2TxEQpGqXLcFW8njDXhHMBos4Xc=ZPoJUKotO6G2_-zWu_uS-YpGG78LX8oSKkcPN3Wq7jI=e33iauUfMsY9Ous9cmzAXW9Qtzn0YRI75meDooNLRao= __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev=CwICAg=IL_XqQWOjubgfqINi2jTzg=Ai1MvyPlSw0GLEkv2TxEQpGqXLcFW8njDXhHMBos4Xc=vmbGnExBcDYh5VUlAwMyZOYtWE6xu-WUCH6_xGE0L_k=AUnBfBYtDRZeDPPBJL3a23YR9U_tSlUltcEtM6NxEx4= __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] sqlalchemy-utils fails devstack install
This bug was opened and the solution presented seems to be accurate: https://bugs.launchpad.net/devstack/+bug/1548592 We had the same issue on our CI and deleting setuputils and reinstalling worked for us. -Original Message- From: Beliveau, Ludovic [mailto:ludovic.beliv...@windriver.com] Sent: Thursday, February 25, 2016 7:18 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] sqlalchemy-utils fails devstack install A bug has been raised against SQLAlchemy-Utils and a fixed has been proposed (but not yet merged): https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_kvesteri_sqlalchemy-2Dutils_pull_193=CwICAg=IL_XqQWOjubgfqINi2jTzg=Ai1MvyPlSw0GLEkv2TxEQpGqXLcFW8njDXhHMBos4Xc=ZPoJUKotO6G2_-zWu_uS-YpGG78LX8oSKkcPN3Wq7jI=kuIoTmjzDeBqjHGE_tKrKQyj5Ei5CsXOp5Tt1OHJb5U= Workaround for running devstack: - Download SQLAlchemy-Utils source code (see https://urldefense.proofpoint.com/v2/url?u=https-3A__sqlalchemy-2Dutils.readthedocs.org_en_latest_installation.html=CwICAg=IL_XqQWOjubgfqINi2jTzg=Ai1MvyPlSw0GLEkv2TxEQpGqXLcFW8njDXhHMBos4Xc=ZPoJUKotO6G2_-zWu_uS-YpGG78LX8oSKkcPN3Wq7jI=mJ8E6bsn0XM-nKHAqgJeEi3tNaQ3gTKwsB6UNjeT3p4= ) - Patch source code locally based on the proposed fix - Install the package Regards, /ludovic On 02/25/2016 08:27 AM, Sean Dague wrote: > On 02/24/2016 11:45 PM, Watanabe, Isao wrote: >> Hello team >> >> Does anyone know about why sqlalchemy-utils fails devstack install since >> about 3:00 UTC, Feb 25th? >> >> Our CI start to fail and in log it says: >> >> 2016-02-25 03:34:22.515 | Collecting SQLAlchemy-Utils===0.31.6 (from -c >> /opt/stack/new/requirements/upper-constraints.txt (line 24)) >> 2016-02-25 03:34:22.602 | Downloading SQLAlchemy-Utils-0.31.6.tar.gz >> (112kB) >> 2016-02-25 03:34:23.031 | Complete output from command python setup.py >> egg_info: >> 2016-02-25 03:34:23.031 | error in SQLAlchemy-Utils setup command: >> 'extras_require' must be a dictionary whose values are strings or lists of >> strings containing valid project/version requirement specifiers. >> 2016-02-25 03:34:23.031 | >> 2016-02-25 03:34:23.031 | >> 2016-02-25 03:34:23.062 | Command "python setup.py egg_info" failed >> with error code 1 in /tmp/pip-build-eRYND2/SQLAlchemy-Utils >> >> However, in mirror[1] which we are using, the package is just there, which >> confused me. >> [1] >> https://urldefense.proofpoint.com/v2/url?u=http-3A__mirror.dfw.rax.op >> enstack.org_pypi_simple_sqlalchemy-2Dutils_=CwICAg=IL_XqQWOjubgfq >> INi2jTzg=Ai1MvyPlSw0GLEkv2TxEQpGqXLcFW8njDXhHMBos4Xc=ZPoJUKotO6G2 >> _-zWu_uS-YpGG78LX8oSKkcPN3Wq7jI=nPN16YBhP8L87MWHLOY9HhlCwA3__riE_6W >> r5yqqaes= >> >> Thanks for any help. >> >> Best regards, >> Watanabe.isao > The failure only exists if you are installing from tar.gz and not from > wheels. For performance reasons the upstream gate builds a wheel > mirror and installs from that. > > Those wheels were built on old setuptools, work on any version. There > is a setuptools bug registered for this, which should hopefully be fixed > today. > > -Sean > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev=CwICAg=IL_XqQWOjubgfqINi2jTzg=Ai1MvyPlSw0GLEkv2TxEQpGqXLcFW8njDXhHMBos4Xc=ZPoJUKotO6G2_-zWu_uS-YpGG78LX8oSKkcPN3Wq7jI=e33iauUfMsY9Ous9cmzAXW9Qtzn0YRI75meDooNLRao= __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder] Brocade CI
Mike, Brocade OpenStack CI is now complying with requirements mentioned in your mail. 1. Reporting success/failure. (FYI, we had been doing this prior to your email, but the results were not visible using lastcomment script unless use the –m option) 2. Link is now posted for logs in comment and in right hand results column, per the message format requirement. 3. Reporting consistently on all patchsets. 4. Recheck is working. 5. Failed message contains wiki link, and recheck message. 6. Brocade OpenStack CI will remain non-voting. Thanks, Angela From: Angela Smith Sent: Thursday, August 27, 2015 2:21 PM To: OpenStack Development Mailing List (not for usage questions) Cc: DL-GRP-ENG-Brocade-Openstack-CI Subject: RE: [openstack-dev] [cinder] Brocade CI The full results of lastcomment script are here for last 400 commits: [1][2] [1] http://paste.openstack.org/show/430074/ [2] http://paste.openstack.org/show/430088/ From: Angela Smith Sent: Thursday, August 27, 2015 1:56 PM To: OpenStack Development Mailing List (not for usage questions) Cc: DL-GRP-ENG-Brocade-Openstack-CI Subject: RE: [openstack-dev] [cinder] Brocade CI Mike, An update on Brocade CI progress. We are now using the format required for results to show in lastcomment script. We have been consistently reporting for last 9 days. See results here: [1]. We are still working on resolving recheck issue and adding link to wiki page in the failed result comment message. Update will be sent when that is completed. Thanks, Angela [1] http://paste.openstack.org/show/430074/ From: Angela Smith Sent: Friday, August 21, 2015 1:02 PM To: OpenStack Development Mailing List (not for usage questions) Cc: DL-GRP-ENG-Brocade-Openstack-CI Subject: RE: [openstack-dev] [cinder] Brocade CI Mike, I wanted to update you on our progress on the Brocade CI. We are currently working on the remaining requirements of adding recheck and adding link to wiki page for a failed result. Also, the CI is now consistently testing and reporting on all cinder reviews for the past 3 days. Thanks, Angela From: Nagendra Jaladanki [mailto:nagendra.jalada...@gmail.com] Sent: Thursday, August 13, 2015 4:59 PM To: OpenStack Development Mailing List (not for usage questions) Cc: DL-GRP-ENG-Brocade-Openstack-CI Subject: Re: [openstack-dev] [cinder] Brocade CI Ramy, Thanks for providing the correct message. We will update our commit message accordingly. Thanks, Nagendra Rao On Thu, Aug 13, 2015 at 4:43 PM, Asselin, Ramy <ramy.asse...@hp.com<mailto:ramy.asse...@hp.com>> wrote: Hi Nagendra, Seems one of the issues is the format of the posted comments. The correct format is documented here [1] Notice the format is not correct: Incorrect: Brocade Openstack CI (non-voting) build SUCCESS logs at: http://144.49.208.28:8000/build_logs/2015-08-13_18-19-19/ Correct: * test-name-no-spaces http://link.to/result : [SUCCESS|FAILURE] some comment about the test Ramy [1] http://docs.openstack.org/infra/system-config/third_party.html#posting-result-to-gerrit From: Nagendra Jaladanki [mailto:nagendra.jalada...@gmail.com<mailto:nagendra.jalada...@gmail.com>] Sent: Wednesday, August 12, 2015 4:37 PM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Cc: brocade-openstack...@brocade.com<mailto:brocade-openstack...@brocade.com> Subject: Re: [openstack-dev] [cinder] Brocade CI Mike, Thanks for your feedback and suggestions. I had send my response yesterday but looks like didn't get posted on the lists.openstack.org<http://lists.openstack.org>. Hence posting it here again. We reviewed your comments and following issues were identified and some of them are fixed and some fix plans in progress: 1) Not posting success or failure The Brocade CI is a non-voting CI. The CI is posting the comment for build sucucess or failures. The report tool is not seeing these. We are working on correcting this. 2) Not posting a result link to view logs. We could not find any cases where CI is failed to post the link to logs from the generated report. If you have any specific uses where it failed to post logs link, please share with us. But we did see that CI not posted the comment at all for some review patch sets. Root causing the issue why CI not posted the comment at all. 3) Not consistently doing runs. There were planned down times and CI not posted during those periods. We also observed that CI was not posting the failures in some cases where CI failed due non openstack issues. We corrected this. Now the CI should be posting the results for all patch sets either success or failure. We are also doing the following: - Enhance the message format to be inline with other CIs. - Closely monitoring the incoming Jenkin's request vs out going builds and correcting if there are any issues. Once again th
Re: [openstack-dev] [cinder] Brocade CI
The full results of lastcomment script are here for last 400 commits: [1][2] [1] http://paste.openstack.org/show/430074/ [2] http://paste.openstack.org/show/430088/ From: Angela Smith Sent: Thursday, August 27, 2015 1:56 PM To: OpenStack Development Mailing List (not for usage questions) Cc: DL-GRP-ENG-Brocade-Openstack-CI Subject: RE: [openstack-dev] [cinder] Brocade CI Mike, An update on Brocade CI progress. We are now using the format required for results to show in lastcomment script. We have been consistently reporting for last 9 days. See results here: [1]. We are still working on resolving recheck issue and adding link to wiki page in the failed result comment message. Update will be sent when that is completed. Thanks, Angela [1] http://paste.openstack.org/show/430074/ From: Angela Smith Sent: Friday, August 21, 2015 1:02 PM To: OpenStack Development Mailing List (not for usage questions) Cc: DL-GRP-ENG-Brocade-Openstack-CI Subject: RE: [openstack-dev] [cinder] Brocade CI Mike, I wanted to update you on our progress on the Brocade CI. We are currently working on the remaining requirements of adding recheck and adding link to wiki page for a failed result. Also, the CI is now consistently testing and reporting on all cinder reviews for the past 3 days. Thanks, Angela From: Nagendra Jaladanki [mailto:nagendra.jalada...@gmail.com] Sent: Thursday, August 13, 2015 4:59 PM To: OpenStack Development Mailing List (not for usage questions) Cc: DL-GRP-ENG-Brocade-Openstack-CI Subject: Re: [openstack-dev] [cinder] Brocade CI Ramy, Thanks for providing the correct message. We will update our commit message accordingly. Thanks, Nagendra Rao On Thu, Aug 13, 2015 at 4:43 PM, Asselin, Ramy ramy.asse...@hp.commailto:ramy.asse...@hp.com wrote: Hi Nagendra, Seems one of the issues is the format of the posted comments. The correct format is documented here [1] Notice the format is not correct: Incorrect: Brocade Openstack CI (non-voting) build SUCCESS logs at: http://144.49.208.28:8000/build_logs/2015-08-13_18-19-19/ Correct: * test-name-no-spaces http://link.to/result : [SUCCESS|FAILURE] some comment about the test Ramy [1] http://docs.openstack.org/infra/system-config/third_party.html#posting-result-to-gerrit From: Nagendra Jaladanki [mailto:nagendra.jalada...@gmail.commailto:nagendra.jalada...@gmail.com] Sent: Wednesday, August 12, 2015 4:37 PM To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Cc: brocade-openstack...@brocade.commailto:brocade-openstack...@brocade.com Subject: Re: [openstack-dev] [cinder] Brocade CI Mike, Thanks for your feedback and suggestions. I had send my response yesterday but looks like didn't get posted on the lists.openstack.orghttp://lists.openstack.org. Hence posting it here again. We reviewed your comments and following issues were identified and some of them are fixed and some fix plans in progress: 1) Not posting success or failure The Brocade CI is a non-voting CI. The CI is posting the comment for build sucucess or failures. The report tool is not seeing these. We are working on correcting this. 2) Not posting a result link to view logs. We could not find any cases where CI is failed to post the link to logs from the generated report. If you have any specific uses where it failed to post logs link, please share with us. But we did see that CI not posted the comment at all for some review patch sets. Root causing the issue why CI not posted the comment at all. 3) Not consistently doing runs. There were planned down times and CI not posted during those periods. We also observed that CI was not posting the failures in some cases where CI failed due non openstack issues. We corrected this. Now the CI should be posting the results for all patch sets either success or failure. We are also doing the following: - Enhance the message format to be inline with other CIs. - Closely monitoring the incoming Jenkin's request vs out going builds and correcting if there are any issues. Once again thanks for your feedback and suggestions. We will continue to post this list on the updates. Thanks Regards, Nagendra Rao Jaladanki Manager, Software Engineering Manageability Brocade 130 Holger Way, San Jose, CA 95134 On Sun, Aug 9, 2015 at 5:34 PM, Mike Perez thin...@gmail.commailto:thin...@gmail.com wrote: People have asked me at the Cinder midcycle sprint to look at the Brocade CI to: 1) Keep the zone manager driver in Liberty. 2) Consider approving additional specs that we're submitted before the deadline. Here are the current problems with the last 100 runs [1]: 1) Not posting success or failure. 2) Not posting a result link to view logs. 3) Not consistently doing runs. If you compare with other CI's there are plenty missing in a day. This CI does not follow the guidelines [2]. Please get help [3]. [1] - http://paste.openstack.org/show
Re: [openstack-dev] [cinder] Brocade CI
Mike, An update on Brocade CI progress. We are now using the format required for results to show in lastcomment script. We have been consistently reporting for last 9 days. See results here: [1]. We are still working on resolving recheck issue and adding link to wiki page in the failed result comment message. Update will be sent when that is completed. Thanks, Angela [1] http://paste.openstack.org/show/430074/ From: Angela Smith Sent: Friday, August 21, 2015 1:02 PM To: OpenStack Development Mailing List (not for usage questions) Cc: DL-GRP-ENG-Brocade-Openstack-CI Subject: RE: [openstack-dev] [cinder] Brocade CI Mike, I wanted to update you on our progress on the Brocade CI. We are currently working on the remaining requirements of adding recheck and adding link to wiki page for a failed result. Also, the CI is now consistently testing and reporting on all cinder reviews for the past 3 days. Thanks, Angela From: Nagendra Jaladanki [mailto:nagendra.jalada...@gmail.com] Sent: Thursday, August 13, 2015 4:59 PM To: OpenStack Development Mailing List (not for usage questions) Cc: DL-GRP-ENG-Brocade-Openstack-CI Subject: Re: [openstack-dev] [cinder] Brocade CI Ramy, Thanks for providing the correct message. We will update our commit message accordingly. Thanks, Nagendra Rao On Thu, Aug 13, 2015 at 4:43 PM, Asselin, Ramy ramy.asse...@hp.commailto:ramy.asse...@hp.com wrote: Hi Nagendra, Seems one of the issues is the format of the posted comments. The correct format is documented here [1] Notice the format is not correct: Incorrect: Brocade Openstack CI (non-voting) build SUCCESS logs at: http://144.49.208.28:8000/build_logs/2015-08-13_18-19-19/ Correct: * test-name-no-spaces http://link.to/result : [SUCCESS|FAILURE] some comment about the test Ramy [1] http://docs.openstack.org/infra/system-config/third_party.html#posting-result-to-gerrit From: Nagendra Jaladanki [mailto:nagendra.jalada...@gmail.commailto:nagendra.jalada...@gmail.com] Sent: Wednesday, August 12, 2015 4:37 PM To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Cc: brocade-openstack...@brocade.commailto:brocade-openstack...@brocade.com Subject: Re: [openstack-dev] [cinder] Brocade CI Mike, Thanks for your feedback and suggestions. I had send my response yesterday but looks like didn't get posted on the lists.openstack.orghttp://lists.openstack.org. Hence posting it here again. We reviewed your comments and following issues were identified and some of them are fixed and some fix plans in progress: 1) Not posting success or failure The Brocade CI is a non-voting CI. The CI is posting the comment for build sucucess or failures. The report tool is not seeing these. We are working on correcting this. 2) Not posting a result link to view logs. We could not find any cases where CI is failed to post the link to logs from the generated report. If you have any specific uses where it failed to post logs link, please share with us. But we did see that CI not posted the comment at all for some review patch sets. Root causing the issue why CI not posted the comment at all. 3) Not consistently doing runs. There were planned down times and CI not posted during those periods. We also observed that CI was not posting the failures in some cases where CI failed due non openstack issues. We corrected this. Now the CI should be posting the results for all patch sets either success or failure. We are also doing the following: - Enhance the message format to be inline with other CIs. - Closely monitoring the incoming Jenkin's request vs out going builds and correcting if there are any issues. Once again thanks for your feedback and suggestions. We will continue to post this list on the updates. Thanks Regards, Nagendra Rao Jaladanki Manager, Software Engineering Manageability Brocade 130 Holger Way, San Jose, CA 95134 On Sun, Aug 9, 2015 at 5:34 PM, Mike Perez thin...@gmail.commailto:thin...@gmail.com wrote: People have asked me at the Cinder midcycle sprint to look at the Brocade CI to: 1) Keep the zone manager driver in Liberty. 2) Consider approving additional specs that we're submitted before the deadline. Here are the current problems with the last 100 runs [1]: 1) Not posting success or failure. 2) Not posting a result link to view logs. 3) Not consistently doing runs. If you compare with other CI's there are plenty missing in a day. This CI does not follow the guidelines [2]. Please get help [3]. [1] - http://paste.openstack.org/show/412316/ [2] - http://docs.openstack.org/infra/system-config/third_party.html#requirements [3] - https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Questions -- Mike Perez __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org
Re: [openstack-dev] [cinder] Brocade CI
Mike, I wanted to update you on our progress on the Brocade CI. We are currently working on the remaining requirements of adding recheck and adding link to wiki page for a failed result. Also, the CI is now consistently testing and reporting on all cinder reviews for the past 3 days. Thanks, Angela From: Nagendra Jaladanki [mailto:nagendra.jalada...@gmail.com] Sent: Thursday, August 13, 2015 4:59 PM To: OpenStack Development Mailing List (not for usage questions) Cc: DL-GRP-ENG-Brocade-Openstack-CI Subject: Re: [openstack-dev] [cinder] Brocade CI Ramy, Thanks for providing the correct message. We will update our commit message accordingly. Thanks, Nagendra Rao On Thu, Aug 13, 2015 at 4:43 PM, Asselin, Ramy ramy.asse...@hp.commailto:ramy.asse...@hp.com wrote: Hi Nagendra, Seems one of the issues is the format of the posted comments. The correct format is documented here [1] Notice the format is not correct: Incorrect: Brocade Openstack CI (non-voting) build SUCCESS logs at: http://144.49.208.28:8000/build_logs/2015-08-13_18-19-19/ Correct: * test-name-no-spaces http://link.to/result : [SUCCESS|FAILURE] some comment about the test Ramy [1] http://docs.openstack.org/infra/system-config/third_party.html#posting-result-to-gerrit From: Nagendra Jaladanki [mailto:nagendra.jalada...@gmail.commailto:nagendra.jalada...@gmail.com] Sent: Wednesday, August 12, 2015 4:37 PM To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Cc: brocade-openstack...@brocade.commailto:brocade-openstack...@brocade.com Subject: Re: [openstack-dev] [cinder] Brocade CI Mike, Thanks for your feedback and suggestions. I had send my response yesterday but looks like didn't get posted on the lists.openstack.orghttp://lists.openstack.org. Hence posting it here again. We reviewed your comments and following issues were identified and some of them are fixed and some fix plans in progress: 1) Not posting success or failure The Brocade CI is a non-voting CI. The CI is posting the comment for build sucucess or failures. The report tool is not seeing these. We are working on correcting this. 2) Not posting a result link to view logs. We could not find any cases where CI is failed to post the link to logs from the generated report. If you have any specific uses where it failed to post logs link, please share with us. But we did see that CI not posted the comment at all for some review patch sets. Root causing the issue why CI not posted the comment at all. 3) Not consistently doing runs. There were planned down times and CI not posted during those periods. We also observed that CI was not posting the failures in some cases where CI failed due non openstack issues. We corrected this. Now the CI should be posting the results for all patch sets either success or failure. We are also doing the following: - Enhance the message format to be inline with other CIs. - Closely monitoring the incoming Jenkin's request vs out going builds and correcting if there are any issues. Once again thanks for your feedback and suggestions. We will continue to post this list on the updates. Thanks Regards, Nagendra Rao Jaladanki Manager, Software Engineering Manageability Brocade 130 Holger Way, San Jose, CA 95134 On Sun, Aug 9, 2015 at 5:34 PM, Mike Perez thin...@gmail.commailto:thin...@gmail.com wrote: People have asked me at the Cinder midcycle sprint to look at the Brocade CI to: 1) Keep the zone manager driver in Liberty. 2) Consider approving additional specs that we're submitted before the deadline. Here are the current problems with the last 100 runs [1]: 1) Not posting success or failure. 2) Not posting a result link to view logs. 3) Not consistently doing runs. If you compare with other CI's there are plenty missing in a day. This CI does not follow the guidelines [2]. Please get help [3]. [1] - http://paste.openstack.org/show/412316/ [2] - http://docs.openstack.org/infra/system-config/third_party.html#requirements [3] - https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Questions -- Mike Perez __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage
Re: [openstack-dev] [cinder] I have a question about openstack cinder zonemanager driver
The decision should be made based on what vendor switch you have in your SAN. -Original Message- From: hao wang [mailto:sxmatch1...@gmail.com] Sent: Friday, August 21, 2015 4:58 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [cinder] I have a question about openstack cinder zonemanager driver I feel supporting multi drivers of zonemanager in one cinder.conf is not much value. How you can decide when to use driver-1 or driver-2? 2015-08-14 10:20 GMT+08:00 Chenying (A) ying.c...@huawei.com: Hi, Jay S. Bryant, Daniel Wilson .Thank you for your reply. Now I know that in this case I need two cinder nodes, one for Brocade fabric and one for Cisco fabric. Do you consider that cinder zonemanager is necessary to support multi-drivers from different vendors in one cinder.conf ? Thanks, ChenYing 发件人: Jay S. Bryant [mailto:jsbry...@electronicjungle.net] 发送时间: 2015年8月14日 0:36 收件人: OpenStack Development Mailing List (not for usage questions) 主题: Re: [openstack-dev] [cinder] I have a question about openstack cinder zonemanager driver. Danny is correct. You cannot have two different Zone Manager drivers configured for one volume process. Jay On 08/13/2015 11:00 AM, Daniel Wilson wrote: I am fairly certain you cannot currently use two different FC switch zone drivers in one cinder.conf. In this case it looks like you would need two cinder nodes, one for Brocade fabric and one for Cisco fabric. Thanks, Danny On Thu, Aug 13, 2015 at 2:43 AM, Chenying (A) ying.c...@huawei.com wrote: Hi, guys I am using Brocade FC switch in my OpenStack environment. I have a question about OpenStack cinder zonemanger driver. I find that [fc-zone-manager] can only configure one zone driver. If I want to use two FC switches from different vendors at the same time. One is Brocade FC switch, the other one is Cisco FC switch. Is there a method or solution configure two FC switch zone driver in one cinder.conf ? I want them both to support Zone Manager. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best Wishes For You! __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [devstack] RTNETLINK permission denied on setting IPv6 on br-ex
We have been having this issue with devstack installation since Tuesday 6/2. On trying to add IPv6 address to br-ex, it fails with permission denied. Here's the output from stack.sh: + IPV6_ROUTER_GW_IP=2001:db8::1 + die_if_not_set 1299 IPV6_ROUTER_GW_IP 'Failure retrieving IPV6_ROUTER_GW_IP' + local exitcode=0 ++ set +o ++ grep xtrace + local 'xtrace=set -o xtrace' + set +o xtrace + is_neutron_ovs_base_plugin + return 0 + [[ True = \T\r\u\e ]] ++ _neutron_get_ext_gw_interface ++ [[ False == \T\r\u\e ]] ++ sudo ovs-vsctl set Bridge br-ex other_config:disable-in-band=true ++ echo br-ex + local ext_gw_interface=br-ex + local ipv6_cidr_len=64 + sudo ip -6 addr add 2001:db8::2/64 dev br-ex RTNETLINK answers: Permission denied __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
