Closed goneri closed 1 year ago
Build succeeded. https://ansible.softwarefactory-project.io/zuul/buildset/8f4201a2d38641398d2b216793a6ed86
:heavy_check_mark: ansible-galaxy-importer SUCCESS in 3m 27s :heavy_check_mark: build-ansible-collection SUCCESS in 9m 47s :x: ansible-test-sanity-docker-devel FAILURE in 7m 23s (non-voting) :x: ansible-test-sanity-docker-milestone FAILURE in 7m 17s (non-voting) :heavy_check_mark: ansible-test-sanity-docker-stable-2.11 SUCCESS in 11m 04s :heavy_check_mark: ansible-test-sanity-docker-stable-2.12 SUCCESS in 8m 12s :heavy_check_mark: ansible-test-sanity-docker-stable-2.13 SUCCESS in 10m 06s :heavy_check_mark: ansible-test-sanity-docker-stable-2.14 SUCCESS in 9m 18s :heavy_check_mark: tox-cloud-refresh-examples-amazon SUCCESS in 9m 30s
Build failed. https://ansible.softwarefactory-project.io/zuul/buildset/9dec616ffb7d4443b36f4ac922c75b1b
:x: ansible-galaxy-importer RETRY_LIMIT in 4m 54s :heavy_check_mark: build-ansible-collection SUCCESS in 10m 06s :x: ansible-test-sanity-docker-devel FAILURE in 9m 28s (non-voting) :x: ansible-test-sanity-docker-milestone FAILURE in 7m 59s (non-voting) :heavy_check_mark: ansible-test-sanity-docker-stable-2.11 SUCCESS in 10m 51s :heavy_check_mark: ansible-test-sanity-docker-stable-2.12 SUCCESS in 8m 37s :heavy_check_mark: ansible-test-sanity-docker-stable-2.13 SUCCESS in 8m 06s :heavy_check_mark: ansible-test-sanity-docker-stable-2.14 SUCCESS in 9m 51s :heavy_check_mark: tox-cloud-refresh-examples-amazon SUCCESS in 10m 02s
With MemoryDB,
StatusMessage
is not always defined and this trigger an exception within the existing exception handling block.With this change we fallback on
OperationStatus
ifStatusMessage
is missing. If none of them are available, we will get aNone
instead of an exception.According to the documentation the presence of these two keys is not guarantee. They are both identified as optional (
Required: No
).See: https://docs.aws.amazon.com/cloudcontrolapi/latest/APIReference/API_ProgressEvent.html