[openstack-dev] [tripleo] [ci] Adding idempotency job on overcloud deployment.
sathlang at redhat.com
Wed Jun 7 11:20:09 UTC 2017
Emilien Macchi <emilien at redhat.com> writes:
> On Wed, Jun 7, 2017 at 12:45 PM, Sofer Athlan-Guyot <sathlang at redhat.com> wrote:
>> I don't think we have such a job in place. Basically that would check
>> that re-running the "openstack deploy ..." command won't do anything.
>> We had such an error by the past, but I'm not sure this has been
>> captured by an associated job.
>> WDYT ?
> It would be interesting to measure how much time does it take to run
> it again.
Could you point out how such an experiment could be done ?
> If it's short, we could add it to all our scenarios + ovb
> jobs. If it's long, maybe we need an additional job, but it would
> take more resources, so maybe we could run it in periodic pipeline
> (note that periodic jobs are not optimal since we could break
> something quite easily).
Just adding as context that the issue was already raised. Beside
time constraint, it was pointed out that we would also need to parse the
log to find out if anything was restarted. But it could be a second
step. For parsing, this code was pointed out.
>>  https://bugs.launchpad.net/tripleo/+bug/1664650
>> Sofer Athlan-Guyot
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> Emilien Macchi
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev