Reviewed: https://review.openstack.org/550832 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0ab03003b9f9c4f0cace538eee84478a099c0c58 Submitter: Zuul Branch: master
commit 0ab03003b9f9c4f0cace538eee84478a099c0c58 Author: Sławek Kapłoński <[email protected]> Date: Thu Mar 8 14:18:31 2018 +0100 [Scenario tests] Try longer SSH timeout for ubuntu image It looks that many scenario tests are failing because of too long instance booting time and reached ssh timeout during checking connectivity. So longer timeout should solve this problem and tests should not fail with this reason. Change-Id: I5d0678ea2383483e6106976c148353ef4352befd Closes-Bug: #1754327 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1754327 Title: Tempest scenario jobs failing due to no FIP connectivity Status in neutron: Fix Released Bug description: It is quite often (especially for linuxbridge scenario job) that some tests (random) are failing because ssh to instance is not possible. Example of such failed tests: http://logs.openstack.org/07/525607/12/check/neutron-tempest-plugin-scenario-linuxbridge/09f04f9/logs/testr_results.html.gz Same issue appears sometimes in dvr scenario job but it is not so often probably because it is multinode job and load on host is maybe lower so instances can boot faster. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1754327/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
