| 2017-09-14 16:32:51 |
Chris Gregan |
description |
A run of 'juju deploy' failed with this error:
ERROR cannot deploy bundle: cannot add unit for application "keystone": cannot add unit 1/1 to application "keystone": cannot add unit to application "keystone": unexpected: Get http://10.245.208.33/MAAS/api/2.0/boot-resources/: EOF
Here is the full output:
http://pastebin.ubuntu.com/25534631/
Looking at the MAAS logs, MAAS was up and servicing requests the whole time. I'm not sure where the EOF came from.
Expected behavior: this seems to be a temporary communication problem between juju and MAAS. I don't know why it would affect the 'deploy' run at the client at all; asking about boot resources seems like something that should be happening on the back end? In either case, juju should retry this read operation. |
maas_2.2.2-6099-g8751f91-0ubuntu1~16.04.1
juju_1:2.2.3-0ubuntu1~16.04.1~juju1
ocata
xenial
A run of 'juju deploy' failed with this error:
ERROR cannot deploy bundle: cannot add unit for application "keystone": cannot add unit 1/1 to application "keystone": cannot add unit to application "keystone": unexpected: Get http://10.245.208.33/MAAS/api/2.0/boot-resources/: EOF
Here is the full output:
http://pastebin.ubuntu.com/25534631/
Looking at the MAAS logs, MAAS was up and servicing requests the whole time. I'm not sure where the EOF came from.
Expected behavior: this seems to be a temporary communication problem between juju and MAAS. I don't know why it would affect the 'deploy' run at the client at all; asking about boot resources seems like something that should be happening on the back end? In either case, juju should retry this read operation. |
|
