Allow to disable status check in resource_openstack_dns_zone_v2

[ya-isakov]

This will allow terraform to tolerate some backend issues in Designate. If zone is created in Designate, and even all the backends are down, Designate will try to recover.

If only one of the backends is down, zone will be in ERROR state, but will be served by other backends. In this case, waiting for ACTIVE state also doesn't make sense.

[ya-isakov]

recheck designate

[ya-isakov]

Why is openlab pending? Should I do something?

[ozerovandrei]

recheck designate

[theopenlab-ci]

Build succeeded.

• terraform-provider-openstack-unittest : SUCCESS in 3m 01s
• terraform-provider-openstack-acceptance-test : SUCCESS in 2h 31m 18s

[theopenlab-ci]

Build failed.

• terraform-provider-openstack-acceptance-test-designate : FAILURE in 39m 52s

[ya-isakov]

recheck designate

[ya-isakov]

I think I've fixed the tests, please, run them again

[ya-isakov]

No, it seems that I haven't fixed them, trying again.

[ya-isakov]

I hope this is how tests should be fixed. I've looked into other resources (like compute_instance_v2) to see how virtual attributes are handled on import.

[ya-isakov]

recheck designate

[ya-isakov]

@ozerovandrei Please, run designate tests again. It seems that my commands are able to set them to pending state only.

[ozerovandrei]

@ya-isakov there seems to be some problems with Zuul since a lots of jobs are in the "unknown" state: http://status.openlabtesting.org/status

I also tried recheck here: #1117 and it didn't work.

I've just opened the issue: theopenlab/openlab#642

[ya-isakov]

recheck

[ya-isakov]

recheck designate

[theopenlab-ci]

Build succeeded.

• terraform-provider-openstack-acceptance-test-designate : SUCCESS in 31m 47s

[theopenlab-ci]

Build succeeded.

• terraform-provider-openstack-unittest : SUCCESS in 4m 14s
• terraform-provider-openstack-acceptance-test : SUCCESS in 2h 30m 22s

[ya-isakov]

@ozerovandrei Please, review.

[ozerovandrei]

LGTM

[ya-isakov]

Thank you!