Right, as Ronelle has found out, that message appears in the passing fs01 jobs and happened to be a red herring :-(
Perhaps the *real* issue starts later and is about AMQP and not DB, which is logged firstly as
Jan 05 12:32:30 ./undercloud/var/log/journal.txt.gz undercloud.localdomain podman[78695]: 2019-01-05T12:32:30.203 9 ERROR oslo_messaging.rpc.server [-] Exception during message handling: RuntimeError: Can not schedule new futures after being shutdown
and that time does overlap with the 2nd re-deployment being executed.
Right, as Ronelle has found out, that message appears in the passing fs01 jobs and happened to be a red herring :-(
Perhaps the *real* issue starts later and is about AMQP and not DB, which is logged firstly as
Jan 05 12:32:30 ./undercloud/ var/log/ journal. txt.gz undercloud. localdomain podman[78695]: 2019-01- 05T12:32: 30.203 9 ERROR oslo_messaging. rpc.server [-] Exception during message handling: RuntimeError: Can not schedule new futures after being shutdown
and that time does overlap with the 2nd re-deployment being executed.