Insecure registry fails for windows nodes during configuration
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
Trunk |
In Progress
|
Undecided
|
Michał Kostrzewa |
Bug Description
When private insecure registry is used for registry, the following error is observed for windows nodes,
global_
REGISTRY_
CONTAINER_
TASK [docker : create /etc/docker directory] *******
[WARNING]: FATAL ERROR DURING FILE TRANSFER: Traceback (most recent call last): File "/usr/lib/python2.7
/site-packages/
self._winrm_
"/usr/lib/
protocol.
line 256, in send_message raise WinRMOperationT
fatal: [10.87.66.194]: FAILED! => {"msg": "winrm send_input failed"}
Using module file /usr/lib/
<10.87.66.192> ESTABLISH WINRM CONNECTION FOR USER: Administrator on PORT 5986 TO 10.87.66.192
Using module file /usr/lib/
<10.87.66.194> ESTABLISH WINRM CONNECTION FOR USER: Administrator on PORT 5986 TO 10.87.66.194
Changed in juniperopenstack: | |
assignee: | nobody → Michał Kostrzewa (mkostrzewa) |
information type: | Proprietary → Public |
Seemingly the following step failed: "create /etc/docker directory". imeoutError.
Reported error is: WinRMOperationT
It doesn't seem that this is anyhow related to any registry.
Looks like a timeout in connection between host running ansible and node being configured.
1. Why do you think this is related to any registry? imeoutError while other tasks were executed?
2. Do you see any correlation between this error and selected registry?
3. How many times this problem occurred when this task was executed?
4. Have you seen WinRMOperationT