Local docker registry access violation seen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Tee Ngo |
Bug Description
Brief Description
-----------------
while the platform-integ-apps was applied it failed with the following reason:
Image 192.168.
2019-05-24 19:01:10.151 105755 INFO sysinv.
2019-05-24 19:01:10.181 105755 ERROR sysinv.
2019-05-24 19:01:10.212 105755 ERROR sysinv.
2019-05-24 19:01:10.212 105755 ERROR sysinv.
2019-05-24 19:01:10.212 105755 TRACE sysinv.
2019-05-24 19:01:10.212 105755 TRACE sysinv.
2019-05-24 19:01:10.212 105755 TRACE sysinv.
2019-05-24 19:01:10.212 105755 TRACE sysinv.
2019-05-24 19:01:10.212 105755 TRACE sysinv.
2019-05-24 19:01:10.212 105755 TRACE sysinv.
2019-05-24 19:01:10.212 105755 TRACE sysinv.
The system is configured with docker_proxy
Severity
--------
Major
Steps to Reproduce
------------------
Bring up a standard system with docker proxy
Expected Behavior
------------------
system should come up with out errors
Actual Behavior
----------------
platform-integ-apps failed
Reproducibility
---------------
seen once
System Configuration
-------
2+10 with docker proxy
Branch/Pull Time/Commit
-------
Private build from 2019-05-23 pull
Last Pass
---------
Not known
Timestamp/Logs
--------------
2019-05-24 19:01:10.181
Test Activity
-------------
Platform Testing
tags: | added: stx.retestneeded |
Changed in starlingx: | |
assignee: | Nimalini Rasa (nrasa) → Bart Wensley (bartwensley) |
Changed in starlingx: | |
assignee: | Bart Wensley (bartwensley) → Tee Ngo (teewrs) |
tags: | added: stx.2.0 |
Changed in starlingx: | |
status: | Incomplete → In Progress |
The Docker registry on the controller seem to give "access violation" when interacted with through the docker client. Sysinv's commands for listing/deleting images/tags which interacts with the registry through restapi seem to work. Interacting with the registry restapi through curl also works.
I removed the proxy file from the proxy config (/etc/systemd/ system/ docker. service. d/http- proxy), which allowed me to interact with the registry through docker commands. I removed the "https" proxy line in the same config, and can still interact with the registry through docker commands.
I spoke with Bart and he suggests the lab should be installed with only 1 of http or https proxy set, which aligns with the results of me playing with the config. Please try reinstalling the lab with only 1 of http or https proxy