Yeah if there are multiple connects to the same network we could have multiple default routes. That would break the logic and kill all those tests. Actually just pick one should be good.
-- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to heartbeat in Ubuntu. https://bugs.launchpad.net/bugs/1734646 Title: dep8 test failing on many architectures Status in heartbeat package in Ubuntu: Confirmed Bug description: From the Test: Setting up cluster-glue (1.0.12-5ubuntu2) ... Adding group `haclient' (GID 118) ... Done. Warning: The home dir /var/lib/pacemaker you specified can't be accessed: No such file or directory Adding system user `hacluster' (UID 112) ... Adding new user `hacluster' (UID 112) with group `haclient' ... ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. Not creating home directory `/var/lib/pacemaker'. Created symlink /etc/systemd/system/multi-user.target.wants/logd.service → /lib/systemd/system/logd.service. Setting up resource-agents (1:4.1.0~rc1-1) ... resource-agents-deps.target is a disabled or a static unit, not starting it. Setting up heartbeat (1:3.0.6-6) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Setting up autopkgtest-satdep (0) ... Processing triggers for libc-bin (2.26-0ubuntu2) ... Processing triggers for systemd (235-2ubuntu3) ... (Reading database ... 48537 files and directories currently installed.) Removing autopkgtest-satdep (0) ... autopkgtest [18:39:02]: test heartbeat: [----------------------- ● heartbeat.service - Heartbeat High Availability Cluster Communication and Membership Loaded: loaded (/lib/systemd/system/heartbeat.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2017-11-26 18:39:02 UTC; 1min 0s ago Process: 2187 ExecStart=/usr/lib/heartbeat/heartbeat -f (code=exited, status=6) Main PID: 2187 (code=exited, status=6) Nov 26 18:39:02 autopkgtest systemd[1]: Started Heartbeat High Availability Cluster Communication and Membership. Nov 26 18:39:02 autopkgtest heartbeat[2187]: Nov 26 18:39:02 autopkgtest heartbeat: [2187]: ERROR: Illegal directive [enc1] in /etc/ha.d//ha.cf Nov 26 18:39:02 autopkgtest heartbeat[2187]: [2187]: ERROR: Illegal directive [enc1] in /etc/ha.d//ha.cf Nov 26 18:39:02 autopkgtest heartbeat[2187]: Nov 26 18:39:02 autopkgtest heartbeat: [2187]: ERROR: Heartbeat not started: configuration error. Nov 26 18:39:02 autopkgtest heartbeat[2187]: [2187]: ERROR: Heartbeat not started: configuration error. Nov 26 18:39:02 autopkgtest heartbeat[2187]: Nov 26 18:39:02 autopkgtest heartbeat: [2187]: ERROR: Configuration error, heartbeat not started. Nov 26 18:39:02 autopkgtest heartbeat[2187]: [2187]: ERROR: Configuration error, heartbeat not started. Nov 26 18:39:02 autopkgtest systemd[1]: heartbeat.service: Main process exited, code=exited, status=6/NOTCONFIGURED Nov 26 18:39:02 autopkgtest systemd[1]: heartbeat.service: Failed with result 'exit-code'. There are a few things important here: 1. on some platforms that was skipped so far (containers) but now breaks and makes this a blocker 2. It seems to fail on (at least) the network handling, it does seem to force a three digit network device name and then append a number, which then fails to be found. - x86: Illegal directive [ens2] in /etc/ha.d//ha.cf - s390x: ERROR: Illegal directive [enc1] in /etc/ha.d//ha.cf Needs repro on such platforms (might work in local autopkgtest but fail on LP infra) to decide about next steps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heartbeat/+bug/1734646/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-ha Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
