https://bugzilla.novell.com/show_bug.cgi?id=856353 https://bugzilla.novell.com/show_bug.cgi?id=856353#c0 Summary: CTS - Test RemoteBaremetal Fails Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability AssignedTo: lmb@suse.com ReportedBy: rbrown@suse.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Every time I run CTS to test a Cluster (currently using openSUSE:Factory + network:ha:factory) every instance of Test RemoteBaremetal fails Example error:
Test RemoteBaremetal FAILED: Failed to start pacemaker_remote on node ix64ph1013
I believe that we might not be using/packaging pacemaker_remote, if this is the case, can we modify our packaged version of CTS so it doesn't run that test by default? At the moment running CTS with --list-tests reports the following
Dec 19 16:49:16 Random seed is: 1387468156 Dec 19 16:49:17 Configuration variant 'pacemaker10' is unknown. Defaulting to latest config Dec 19 16:49:17 Total 15 tests Dec 19 16:49:17 Flip Dec 19 16:49:17 Restart Dec 19 16:49:17 StartOnebyOne Dec 19 16:49:17 SimulStart Dec 19 16:49:17 SimulStop Dec 19 16:49:17 StopOnebyOne Dec 19 16:49:17 RestartOnebyOne Dec 19 16:49:17 PartialStart Dec 19 16:49:17 Standby Dec 19 16:49:17 MaintenanceMode Dec 19 16:49:17 ResourceRecover Dec 19 16:49:17 Reattach Dec 19 16:49:17 SpecialTest1 Dec 19 16:49:17 NearQuorumPoint Dec 19 16:49:17 RemoteBaremetal
The 'error' about our Configuration variant makes me think we can either alter our variant so CTS knows not to run RemoteBaremetal or we can inform CTS what the valid tests for our variant is..either sounds like a good solution to me -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.