3 Posts
0
3584
Deploying ECS CE 3.2.2.0 fails with "The error was: AttributeError: 'module' object has no attribute 'HTTPError'"
Hi folks,
I am following the Quick Start Guide on https://ecsce.readthedocs.io/en/latest/ deploy ECS CE 3.2.2.0 (single node) on CentoOS 7.
The bootstrap ran fine but the install is failing as below on "step1" with 'module' object has no attribute 'HTTPError'.
TASK [common_deploy : Common | Create a data container for ECS configuration control] ******************************************************************************************************************************************************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: AttributeError: 'module' object has no attribute 'HTTPError'
fatal: [192.168.100.189]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Traceback (most recent call last):\n File \"/tmp/ansible_4FOhhl/ansible_module_docker.py\", line 526, in \n import docker.client\n File \"/usr/lib/python2.7/site-packages/docker/__init__.py\", line 6, in \n from .client import Client, AutoVersionClient, from_env # flake8: noqa\n File \"/usr/lib/python2.7/site-packages/docker/client.py\", line 11, in \n from . import api\n File \"/usr/lib/python2.7/site-packages/docker/api/__init__.py\", line 2, in \n from .build import BuildApiMixin\n File \"/usr/lib/python2.7/site-packages/docker/api/build.py\", line 7, in \n from .. import errors\n File \"/usr/lib/python2.7/site-packages/docker/errors.py\", line 4, in \n c lass APIError(requests.exceptions.HTTPError):\nAttributeError: 'module' object has no attribute 'HTTPError'\n", "module_stdout": "", "msg": "MODULE FAILURE", "rc": 1}
PLAY RECAP *********************************************************************************************************************************************************************************************************************************************************************
192.168.100.189 : ok=19 changed=15 unreachable=0 failed=1
Playbook run took 0 days, 0 hours, 0 minutes, 19 seconds
Operation failed.
Running "step1" a 2nd time fails as the ECS disk is already partitioned, however when I re-format the drive and re-run "step1" again I hot the same error-> APIError(requests.exceptions.HTTPError):\nAttributeError: 'module' object has no attribute 'HTTPError'\n
Has anyone seen this behaviour?
Message was edited by: micksul
micksul
3 Posts
0
November 9th, 2018 08:00
The issue was that the obj docker container IP range matched the network I used to deploy ECS.
I performed a workaround and ECS CE is up and running.
micksul
3 Posts
0
November 9th, 2018 06:00
The root cause here was operator error on my part. I had deployed ECS on a CentOS VM I spun up that used a 7.5 ISO, rather than 7.4.
I redeployed on 7.4 and now #step1 is successful but #step2 hangs pinging the endpoint for more than 1 hour.
I am also seeing "SystemVirtualArrayModule.java (line 159) System varray : null" in the logs but I don't know if that's an issue.
The total number of DTs is shows as 0.
step1 (successful)
TASK [CentOS_7_service_policies : CentOS 7 | Insert ecs.service into systemd] **************************************************************************************************************************************************************************************************
ok: [192.168.100.189]
PLAY RECAP *********************************************************************************************************************************************************************************************************************************************************************
192.168.100.189 : ok=41 changed=14 unreachable=0 failed=0
Playbook run took 0 days, 0 hours, 0 minutes, 18 seconds
PLAY [Common | Ping data nodes before doing anything else] *******************************************************************************************************************************************************************************************************************
TASK [ping] ********************************************************************************************************************************************************************************************************************************************************************
ok: [192.168.100.189]
PLAY [Common | Start and enable ECS services] **********************************************************************************************************************************************************************************************************************************
TASK [common_start_enable_service : Common | Enable ECS service and start ECS] *************************************************************************************************************************************************************************************************
changed: [192.168.100.189]
PLAY RECAP *********************************************************************************************************************************************************************************************************************************************************************
192.168.100.189 : ok=2 changed=1 unreachable=0 failed=0
Playbook run took 0 days, 0 hours, 0 minutes, 1 seconds
step2
[admin@luna ~]$ sudo -i step2
> Pinging Management API Endpoint until ready
> Pinging endpoint 192.168.100.189... (CTRL-C to break)
> WAIT: API service is not alive. This is likely temporary.
> WAIT: API service is not alive. This is likely temporary.
> WAIT: API service is not alive. This is likely temporary.
> WAIT: API service is not alive. This is likely temporary.
> WAIT: API service is not alive. This is likely temporary.
> WAIT: API service is not alive. This is likely temporary.
ECS Logs
luna:/var/log # grep -i "System varray" dtquery.log | tail
2018-11-09T14:21:47,936 [ZoneScanner-000] INFO SystemVirtualArrayModule.java (line 159) System varray : null
2018-11-09T14:21:52,938 [ZoneScanner-000] INFO SystemVirtualArrayModule.java (line 159) System varray : null
2018-11-09T14:21:57,940 [ZoneScanner-000] INFO SystemVirtualArrayModule.java (line 159) System varray : null
2018-11-09T14:22:02,942 [ZoneScanner-000] INFO SystemVirtualArrayModule.java (line 159) System varray : null
2018-11-09T14:22:07,943 [ZoneScanner-000] INFO SystemVirtualArrayModule.java (line 159) System varray : null
2018-11-09T14:22:12,945 [ZoneScanner-000] INFO SystemVirtualArrayModule.java (line 159) System varray : null
2018-11-09T14:22:17,946 [ZoneScanner-000] INFO SystemVirtualArrayModule.java (line 159) System varray : null
2018-11-09T14:22:22,951 [ZoneScanner-000] INFO SystemVirtualArrayModule.java (line 159) System varray : null
2018-11-09T14:22:27,953 [ZoneScanner-000] INFO SystemVirtualArrayModule.java (line 159) System varray : null
2018-11-09T14:22:32,955 [ZoneScanner-000] INFO SystemVirtualArrayModule.java (line 159) System varray : null
admin@luna emcvipr-object]$ sudo docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
05965f8b7344 emccorp/ecs-software:latest "/opt/vipr/boot/bo..." 37 minutes ago Up 37 minutes ecs-storageos
5a343a5b6354 emccorp/ecs-install:latest "/bin/echo echo 'D..." 39 minutes ago Exited (0) 38 minutes ago ecs-install-data
04378b528e0c emccorp/ecs-software:latest "/bin/echo 'ECS co..." About an hour ago Created ecs-config
luna:/var/log # curl -X GET http://192.168.100.2:9101/stats/dt/DTInitStat
0 0 0 luna:/var/log #