Re: [openstack-dev] [infra][tempest][devstack][congress] tempest.config.CONF.service_available changed on Jan 2/3?

2018-01-08 Thread Eric K 


On 1/7/18, 9:27 PM, "Ghanshyam Mann"  wrote:

>On Sat, Jan 6, 2018 at 3:41 PM, Chandan kumar 
>wrote:
>> Hello Eric,
>>
>> On Sat, Jan 6, 2018 at 4:46 AM, Eric K  wrote:
>>> Seems that sometime between 1/2 and 1/3 this year,
>>> tempest.config.CONF.service_available.aodh_plugin as well as
>>> ..service_available.mistral became unavailable in congress dsvm
>>>check/gate
>>> job. [1][2]
>>>
>>> I've checked the changes that went in to congress, tempest, devstack,
>>> devstack-gate, aodh, and mistral during that period but don't see
>>>obvious
>>> causes. Any suggestions on where to look next to fix the issue? Thanks
>>> very much!
>
>These config options should stay there even separating the tempest
>plugin.  I have checked aodh and mistral config options and there are
>present as tempest config.
>
>- 
>https://github.com/openstack/telemetry-tempest-plugin/blob/b30a19214d00361
>41de75047b444d48ae0d0b656/telemetry_tempest_plugin/config.py#L27
>- 
>https://github.com/openstack/mistral-tempest-plugin/blob/63a0fe20f98e0cb83
>16beb81ca77249ffdda29c5/mistral_tempest_tests/config.py#L18
>
>
>Issue occurred because of removing the in-tree plugins before congress
>was setup to use new repo. We should not remove the in-tree plugin
>before gate setup of consuming the new plugin is complete for each
>consumer of plugings.
>
>>>
>>
>> The aodh tempest plugin [https://review.openstack.org/#/c/526299/] is
>> moved to telemetry-tempest-plugin
>> [https://github.com/openstack/telemetry-tempest-plugin].
>> I have sent a patch to Congress project to fix the issue:
>> https://review.openstack.org/#/c/531534/
>
>Thanks Chandan, this will fix congress issue for Aodh, we need same
>fix for mistral case too.
Thank you Chandan Kumar and Ghanshyam Mann!
It seems that the adding of telemetry-tempest-plugin does not solve the
issue though.
I did a testing patch based-off of Chandan's, and the aodh test was still
skipped. Any ideas what more needs to be done? Thanks so much!
https://review.openstack.org/#/c/531922/
http://logs.openstack.org/22/531922/1/check/congress-devstack-api-mysql/381
2b5d/logs/testr_results.html.gz
>
>>
>> The mistral bundled intree tempest plugin
>> [https://review.openstack.org/#/c/526918/] is also moved to
>> mistral-tempest-plugin repo
>> [https://github.com/openstack/mistral-tempest-plugin]
>>
>> Tests are moved to a new repo as a part of Tempest Plugin Split goal
>> 
>>[https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.h
>>tml].
>> Feel free to consume the new tempest plugin and let me know if you
>> need any more help.
>>
>> Thanks,
>>
>> Chandan Kumar
>>
>> 
>>_
>>_
>> 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

Re: [openstack-dev] [infra][tempest][devstack][congress] tempest.config.CONF.service_available changed on Jan 2/3?

2018-01-07 Thread Ghanshyam Mann 
On Sat, Jan 6, 2018 at 3:41 PM, Chandan kumar  wrote:
> Hello Eric,
>
> On Sat, Jan 6, 2018 at 4:46 AM, Eric K  wrote:
>> Seems that sometime between 1/2 and 1/3 this year,
>> tempest.config.CONF.service_available.aodh_plugin as well as
>> ..service_available.mistral became unavailable in congress dsvm check/gate
>> job. [1][2]
>>
>> I've checked the changes that went in to congress, tempest, devstack,
>> devstack-gate, aodh, and mistral during that period but don't see obvious
>> causes. Any suggestions on where to look next to fix the issue? Thanks
>> very much!

These config options should stay there even separating the tempest
plugin.  I have checked aodh and mistral config options and there are
present as tempest config.

- 
https://github.com/openstack/telemetry-tempest-plugin/blob/b30a19214d0036141de75047b444d48ae0d0b656/telemetry_tempest_plugin/config.py#L27
- 
https://github.com/openstack/mistral-tempest-plugin/blob/63a0fe20f98e0cb8316beb81ca77249ffdda29c5/mistral_tempest_tests/config.py#L18


Issue occurred because of removing the in-tree plugins before congress
was setup to use new repo. We should not remove the in-tree plugin
before gate setup of consuming the new plugin is complete for each
consumer of plugings.

>>
>
> The aodh tempest plugin [https://review.openstack.org/#/c/526299/] is
> moved to telemetry-tempest-plugin
> [https://github.com/openstack/telemetry-tempest-plugin].
> I have sent a patch to Congress project to fix the issue:
> https://review.openstack.org/#/c/531534/

Thanks Chandan, this will fix congress issue for Aodh, we need same
fix for mistral case too.

>
> The mistral bundled intree tempest plugin
> [https://review.openstack.org/#/c/526918/] is also moved to
> mistral-tempest-plugin repo
> [https://github.com/openstack/mistral-tempest-plugin]
>
> Tests are moved to a new repo as a part of Tempest Plugin Split goal
> [https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html].
> Feel free to consume the new tempest plugin and let me know if you
> need any more help.
>
> Thanks,
>
> Chandan Kumar
>
> __
> 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

Re: [openstack-dev] [infra][tempest][devstack][congress] tempest.config.CONF.service_available changed on Jan 2/3?

2018-01-06 Thread Chandan kumar 
Hello Eric,

On Sat, Jan 6, 2018 at 4:46 AM, Eric K  wrote:
> Seems that sometime between 1/2 and 1/3 this year,
> tempest.config.CONF.service_available.aodh_plugin as well as
> ..service_available.mistral became unavailable in congress dsvm check/gate
> job. [1][2]
>
> I've checked the changes that went in to congress, tempest, devstack,
> devstack-gate, aodh, and mistral during that period but don't see obvious
> causes. Any suggestions on where to look next to fix the issue? Thanks
> very much!
>

The aodh tempest plugin [https://review.openstack.org/#/c/526299/] is
moved to telemetry-tempest-plugin
[https://github.com/openstack/telemetry-tempest-plugin].
I have sent a patch to Congress project to fix the issue:
https://review.openstack.org/#/c/531534/

The mistral bundled intree tempest plugin
[https://review.openstack.org/#/c/526918/] is also moved to
mistral-tempest-plugin repo
[https://github.com/openstack/mistral-tempest-plugin]

Tests are moved to a new repo as a part of Tempest Plugin Split goal
[https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html].
Feel free to consume the new tempest plugin and let me know if you
need any more help.

Thanks,

Chandan Kumar

__
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] [infra][tempest][devstack][congress] tempest.config.CONF.service_available changed on Jan 2/3?

2018-01-05 Thread Eric K 
Seems that sometime between 1/2 and 1/3 this year,
tempest.config.CONF.service_available.aodh_plugin as well as
..service_available.mistral became unavailable in congress dsvm check/gate
job. [1][2]

I've checked the changes that went in to congress, tempest, devstack,
devstack-gate, aodh, and mistral during that period but don't see obvious
causes. Any suggestions on where to look next to fix the issue? Thanks
very much!

Eric Kao

[1] test results from Jan 2; note that aodh is available:
http://logs.openstack.org/54/530154/5/check/congress-devstack-api-mysql/6f8
2f93/logs/testr_results.html.gz
[2] test results from Jan 3; note that aodh is skipped by this line [3],
but aodh is in fact available as seen from the aodh logs [4]:
http://logs.openstack.org/13/526813/11/gate/congress-devstack-api-mysql/7bf
b025/logs/testr_results.html.gz
[3] 
http://git.openstack.org/cgit/openstack/congress/tree/congress_tempest_test
s/tests/scenario/congress_datasources/test_aodh.py#n32
[4] 
http://logs.openstack.org/13/526813/11/gate/congress-devstack-api-mysql/7bf
b025/logs/



__
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