periodic ovb master jobs failing "Stderr: u'Cannot find device "br-ex" & error: Could not connect to cluster

Bug #1820280 reported by Marios Andreou on 2019-03-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Marios Andreou

Bug Description

periodic-tripleo-ci-centos-7-ovb-3ctlr_1comp_1supp-featureset039-master [1] , periodic-tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001-master [2] , periodic-tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset035-master [3] failing - first error is related to network then pacemaker then many other things.

traces in [1][2][3] below like:

  | [2019/03/15 01:23:46 AM] [WARNING] Error in 'ip route add default via 2001:db8:fd00:1000::1 dev br-ex', restarting br-ex:
  | Unexpected error while running command.
  | Command: /sbin/ip route add default via 2001:db8:fd00:1000::1 dev br-ex
  | Exit code: 1
  | Stdout: u''
  | Stderr: u'Cannot find device "br-ex"\n'


  | "error: Could not connect to cluster (is it running?)",

  | "stderr: Error: unable to get cib",
  | "Error: unable to get cib",




Tags: ci Edit Tag help
Marios Andreou (marios-b) wrote :

As suspected this is no longer seen after we had a promotion (which didn't happen for > 2 weeks).

All three jobs have green runs [1] today - except fs 01 but that is failing on a different error we can file a new bug if that is needed.

Closing this as invalid thanks.


tags: removed: promotion-blocker
Changed in tripleo:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers