Hi  Christopher,
I agree with you. 5 minutes should be sufficient (I was actually the guy who 
proposed to move from 180s to 300s, I guess it’s not sufficient for me ;-) ).
It may be because all the VMs start at the same time and write to disks, which 
may put the servers under pressure (it’s a rather small openstack).
To be honest, this one and the one for SO are the least important imo ont the 
list :-)

Le 15 nov. 2017 à 17:54, LOTT, CHRISTOPHER M (CHRISTOPHER) 
<[email protected]<mailto:[email protected]>> a écrit :

Re Portal db timeouts in version 1.3.0/R1 - the portal app server waits 300 
seconds (as configured in its docker-compose.yml file, see relevant part below) 
for the database to start.  If your system takes more than 5 minutes for the 
database docker container to become available, I wonder if something is starved 
for resources, because that seems like an unreasonably long time for a MariaDB 
server to load a few kilobytes of data.  Anyhow, to workaround you may can 
update the docker-compose file -- and submit a gerrit review so we increase the 
timeout for everyone.

--

 portal-apps:
   image: ${EP_IMG_NAME}:${PORTAL_TAG}
   ports:
     - 8989:8080
     - 8010:8009
     - 8006:8005
   links:
     - portal-db
     - portal-wms
   depends_on:
     - portal-db
     - portal-wms
   volumes:
     - 
${PROPS_DIR}/ONAPPORTAL/system.properties:${WEBAPPS_DIR}/ONAPPORTAL/WEB-INF/conf/system.properties
     - 
${PROPS_DIR}/ONAPPORTAL/fusion.properties:${WEBAPPS_DIR}/ONAPPORTAL/WEB-INF/fusion/conf/fusion.properties
     - 
${PROPS_DIR}/ONAPPORTAL/portal.properties:${WEBAPPS_DIR}/ONAPPORTAL/WEB-INF/classes/portal.properties
     - 
${PROPS_DIR}/ONAPPORTAL/openid-connect.properties:${WEBAPPS_DIR}/ONAPPORTAL/WEB-INF/classes/openid-connect.properties
     - 
${PROPS_DIR}/ONAPPORTAL/logback.xml:${WEBAPPS_DIR}/ONAPPORTAL/WEB-INF/classes/logback.xml
     - 
${PROPS_DIR}/ONAPPORTALSDK-1.3.0/fusion.properties:${WEBAPPS_DIR}/ONAPPORTALSDK/WEB-INF/fusion/conf/fusion.properties
     - 
${PROPS_DIR}/ONAPPORTALSDK-1.3.0/system.properties:${WEBAPPS_DIR}/ONAPPORTALSDK/WEB-INF/conf/system.properties
     - 
${PROPS_DIR}/ONAPPORTALSDK-1.3.0/portal.properties:${WEBAPPS_DIR}/ONAPPORTALSDK/WEB-INF/classes/portal.properties
     - 
${PROPS_DIR}/ONAPPORTALSDK-1.3.0/logback.xml:${WEBAPPS_DIR}/ONAPPORTALSDK/WEB-INF/classes/logback.xml
     - ${LOGS_DIR}:/opt/apache-tomcat-8.0.37/logs
   command:
     - /wait-for.sh
     - -t
     - "300"                     <----- TIMEOUT VALUE IS HERE
     - portal-db:3306
     - --
     - /start-apps-cmd.sh
     # see comments in .env file
     - $EXTRA_HOST_IP
     - $EXTRA_HOST_NAME
   logging:
     driver: json-file



On Nov 15, 2017, at 11:25 AM, 
[email protected]<mailto:[email protected]> wrote:

Hello guys,
I’ve started a Heat deployment 4h ago with fresh pull just before.


At the end of the deployment,  I’ve got 6 over 30 tests only which are green :
   • DCAE fails (but this is because of multi cloud)
   • SDNGC fails
   • APPC fails
   • Portal fails
   • SO fails


for SDNC, it appears that the init script pull 1.1.0-release branch which is 
quite outdated compared to master. When launching with docker-compose from 
master, it starts and healthcheck is OK

for APPC, I see some errors in the logs:
Error: Could not find or load main class 
org.openecomp.sdnc.dg.loader.DGXMLGenerator
Error: Could not find or load main class org.openecomp.sdnc.dg.loader.DGXMLLoad
Error: Could not find or load main class 
org.openecomp.sdnc.dg.loader.DGXMLActivate
After changing to 1.2 instead of 1.1 for the docker version, healthcheck pass.

For portal, I’ve got a timeout from db access, after after a relaunch of the 
portal it works

For SO, a restart of the script did the trick (forgot to see the error first 
sorry)

For multicloud, I have pulling error from nexus :
Pulling repository 
nexus3.onap.org:10001/onap/msb/msb_discovery<http://nexus3.onap.org:10001/onap/msb/msb_discovery>
Error: image onap/msb/msb_discovery:v1.0.0 not found
Pulling repository 
nexus3.onap.org:10001/onap/msb/msb_apigateway<http://nexus3.onap.org:10001/onap/msb/msb_apigateway>
nexus3.onap.org<http://nexus3.onap.org>
Error: image onap/msb/msb_apigateway:v1.0.0 not found


Am I the only one having all these errors?
How can I debug multicloud?

Thanks!


--
<image001.png>

Sylvain Desbureaux
Ingénieur concepteur développeur
ORANGE/IMT/OLN/CNC/NCA/SINA

Fixe : +33 2 96 07 13 80
Mobile : +33 6 71 17 25 57
[email protected]<mailto:[email protected]>

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

_______________________________________________
onap-discuss mailing list
[email protected]<mailto:[email protected]>
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IZdJcfOS7YWo6UY200A3VVFzja_rCk3u0gLN62mqPOk&m=lHVVpBOIxGFfuShiGiSAigKItXafrPXuxpu3LDwBhdA&s=bzAVUTNDbsaHb3OtxM5bMlctoUqt3Jqc8A1ttikZFvU&e=


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to