diff options
| author |   Jiri Stransky <jistr@redhat.com> | 2017-06-16 11:03:45 +0200 |
|---|---|---|
| committer | Jiri Stransky <jistr@redhat.com> | 2017-06-16 11:03:45 +0200 |
| commit | 0e0ccda3696580b46d30e0732bf85c6b510bba23 (patch) | |
| tree | 455556a39de7c36f58a1681d9ab5c0494fa30e16 /environments/docker-network.yaml | |
| parent | 0f88704204b87450c6a82b2ffcc52a50067db8ca (diff) | |
Fall back to non-containerized cinder-volume to unblock CI
CI was stuck on collecting logs. The collect-logs playbook, which
normally takes just a few minutes, took more than an hour and was
eventually killed.
The playbook was stuck on collecting LVM info on the overcloud node,
which runs this command:
(vgs; pvs; lvs) &> /var/log/extra/lvm.txt
Therefore it's very likely that the problematic part is the LVM setup
in the containerized cinder-volume service, and falling back to
non-contianerized for the time being should get the CI going
again.
Change-Id: Ib10e4f18d967d356a15b97f58c488f8402a73356
Closes-Bug: #1698136
Diffstat (limited to 'environments/docker-network.yaml')
0 files changed, 0 insertions, 0 deletions