Ticket for the robot issue: https://jira.onap.org/browse/OOM-618
But I think it should be a Robot ticket. > On Jan 24, 2018, at 2:20 PM, FREEMAN, BRIAN D <[email protected]> wrote: > > On the chrome driver. > > I think I worked around it by installing an alternate chrome version in the > container. > Using part of a fix that Gary has in integration – basically using the 2.32 > version instead of the version in the container. > > Brian > > > # install chrome driver > if [ ! -x ${ROBOT_VENV}/bin/chromedriver ]; then > pushd ${ROBOT_VENV}/bin > wget -N > http://chromedriver.storage.googleapis.com/2.32/chromedriver_linux64.zip > <http://chromedriver.storage.googleapis.com/2.32/chromedriver_linux64.zip> > unzip chromedriver_linux64.zip > chmod +x chromedriver > popd > fi > > From: Alexis de Talhouët [mailto:[email protected]] > Sent: Wednesday, January 24, 2018 2:10 PM > To: FREEMAN, BRIAN D <[email protected]> > Cc: onap-discuss <[email protected]> > Subject: Re: [onap-discuss] [OOM] inter-module instantiate dependencies > > Thank Brian for trying OOM and helping improving it! I guess this is on > Amsterdam? > I opened bugs to track this, see inline. for questions. > > Thanks > Alexis > > > On Jan 24, 2018, at 1:50 PM, FREEMAN, BRIAN D <[email protected] > <mailto:[email protected]>> wrote: > > Started to confirm functionality with OOM Amsterdam. > > I think these are already being tracked but wanted to confirm with OOM team. > > Model distribution from SDC fails to SO and SDNC on a fresh install. > SO’s ASDC Adapter tries to communicate with SDC-BE before its up. > i. Delete > of the SO pod and K8 automated restart clears the problem – redistribute > works so it seems like a timing problem that SO should not be started till > SDC-BEis up. > > AdT: https://jira.onap.org/browse/OOM-616 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_OOM-2D616&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=0q6hZVTaqZ7d33E8pEaugboYHfjCjI_0rYPNo91TCCU&s=ltLOv2wp22VQOG-weLJjQaTkLwj7PIWg9r1vpdXkuTc&e=> > > > SDNC ueb-listener tries to communicate with SDC-BE before its up. > i. Delete > of the ueb-listener pod and K8 automated restart clears the problem – > redistribute works so it seems like a timing problem that ueb-listener/SDNC > should not be started till SDC is up. > > AdT: https://jira.onap.org/browse/OOM-617 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_OOM-2D617&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=0q6hZVTaqZ7d33E8pEaugboYHfjCjI_0rYPNo91TCCU&s=oAqDwtrHbRogu8ZA7K1KcOSZkmdzDX9Y-4fs0x0OdX0&e=> > > > Agree there should be automated retry in listeners on boot but in Amsterdam > that does not seem to be there. > > AdT: It’s ok, we can have deterministic startup with K8S. We can check for a > given port to be open. > > > > AAF does not come up and delays the install by 10+ minutes > I assume we can take AAF out of the config and not try to start it. > I would think for Amsterdam that might need to be the default > > AdT: As far as I know, AAF never worked for OOM on Amsterdam. Always failed > with `Error: Could not find or load main class > org.onap.aaf.authz.service.AuthAPI` > > Robot had a problem with the chrome driver when trying to instantiate (and > probably other flows) – is there a fix ? > WebDriverException: Message: unknown error: an X display is required for > keycode conversions, consider using Xvfb (Session info: headless > chrome=63.0.3239.132) (Driver info: chromedriver=2.29.461571 > > > AdT: Is this specific to OOM? > > > > > Brian > > _______________________________________________ > onap-discuss mailing list > [email protected] <mailto:[email protected]> > https://lists.onap.org/mailman/listinfo/onap-discuss > <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=0q6hZVTaqZ7d33E8pEaugboYHfjCjI_0rYPNo91TCCU&s=rHqg85CQ5FyJN75nqHsgWBLC6vcn_orisGfehj8iHJs&e=>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
