Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

                          -  Docker Pull as a part of Each ONAP VM Creation is generally not clean . There are 2 Global Problem that we keep facing 


                 Docker Pull Errors

                               a. - Image Not Found Error on Nexus Repo for multiple different Docker  Images .

                                      Error: image aaionap/hbase:1.0.0 not found
                              b- TLS Handshake Error for few docker images . 
                                    Error response from daemon: Get https://nexus3.onap.org:10001/v2/openecomp/data-router/manifests/1.1-STAGING-latest: net/http: TLS handshake timeout
                                     Error response from daemon: Get https://nexus3.onap.org:10001/v2/openecomp/aai-traversal/manifests/1.1-STAGING-latest: net/http: TLS handshake timeout
                              c- I/O Timeout
                                     Error response from daemon: Get https://nexus3.onap.org:10001/v1/_ping: dial tcp 199.204.45.137:10001: i/o timeout

                             d- curl command for docker-compose.yaml pull inside initscripts  keeps  failing Intermittenly .

                              e-  directory creation in VID , SDNC and SDC failes . t
                        -     curl command for docker-compose.yaml pull  failing .
             d and e requires manual creation of directory and relaunch Init scripts  manually 
          -     directory creation in VID , SDNC and SDC failes                         f  SDCSDC/SDNC does a GITClone for roughly 800 MB of Size .This hangs intermittenly .intermittently .

                 

               Post Docker Pull /Downloaded successfully errors .

  

                       - AAI2 and AAI1 - has Init issues if certain order is not followed .

                       -SDC sanity container keeps exiting intermittently 

               WorkArounds -WorkArounds -

                                  – reboot AA1 and AAi2 helps in recovering.

              

2. Run the healthCheck inside Robot VM. 

...