Sorry, missed the mentioned patches: [1] Refresh log files for tripleo project: https://review.openstack.org/#/c/312985/ [2] Add bug for TripleO timeouts: https://review.openstack.org/#/c/313038/
On Mon, May 9, 2016 at 8:22 PM, Sagi Shnaidman <sshna...@redhat.com> wrote: > Hi, all > > I'd like to enable elastic recheck on TripleO CI and have submitted > patches for refreshing the tracked logs [1] (please review) and for timeout > case [2]. > But according to Derek's comment behind the timeout issue could be > multiple issues and bugs, so I'd like to clarify - what are criteria for > elastic recheck bugs? > > I thought about those markers: > > Nova: > 1) "No valid host was found. There are not enough hosts" > Network issues: > 2) "Failed to connect to trunk.rdoproject.org" OR "fatal: The remote end > hung up unexpectedly" OR "Could not resolve host:" > Ironic: > 3) "Error contacting Ironic server:" > 4) "Introspection completed with errors:" > 5) ": Introspection timeout" > 6) "Timed out waiting for node " > Glance: > 7) "500 Internal Server Error: Failed to upload image" > crm_resource: > 8) "crm_resource for openstack " > > and various puppet errors. > > However almost all of these messages could have different root causes, > except of network failures. Easy to fix bug doesn't make to submit there, > because they will be fixed yet before recheck patch will be merged. > So, could you please think about right criteria of bugs for elastic > recheck? > > Thanks > > -- > Best regards > Sagi Shnaidman > -- Best regards Sagi Shnaidman
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
