Skip to content

Test cases against nodeset error handling

Gᴏɴɢ Jie edited this page Oct 12, 2017 · 6 revisions

The main purpose of these test cases is verify the changes made by pull request #4037 [1].

[1] https://github.com/xcat2/xcat-core/pull/4037

A handful of bogus xCAT node definitions will be created, and xCAT command nodeset will be run against these bogus node definitions. After the command was run, check the outputs and exit codes to see if the error handling worked fine.

Scenario 1

One node has no MAC address available in its node definition. Run nodeset <noderange> osimage=<osimage>

Scenario 2

One node has no arch attribute set in its node definition. Run the following commands

nodeset <noderange> shell
nodeset <noderange> runcmd=bmcsetup
nodeset <noderange> runimage=/non/existant/image
nodeset <noderange> standby

nodeset <noderange> osimage
nodeset <noderange> osimage=an-osimage
nodeset <noderange> osimage=non-existant-osimage

Scenario 3

One node has serialport set in its node definition but serialspeed is not set. Run the following commands

nodeset <noderange> shell
nodeset <noderange> runcmd=bmcsetup
nodeset <noderange> runimage=/non/existant/image
nodeset <noderange> standby

nodeset <noderange> osimage
nodeset <noderange> osimage=an-osimage
nodeset <noderange> osimage=non-existant-osimage

Scenario 1, 2 and 3 should be run against nodes with netboot=petitboot, netboot=xnba and netboot=grub2

News

History

  • Oct 22, 2010: xCAT 2.5 released.
  • Apr 30, 2010: xCAT 2.4 is released.
  • Oct 31, 2009: xCAT 2.3 released. xCAT's 10 year anniversary!
  • Apr 16, 2009: xCAT 2.2 released.
  • Oct 31, 2008: xCAT 2.1 released.
  • Sep 12, 2008: Support for xCAT 2 can now be purchased!
  • June 9, 2008: xCAT breaths life into (at the time) the fastest supercomputer on the planet
  • May 30, 2008: xCAT 2.0 for Linux officially released!
  • Oct 31, 2007: IBM open sources xCAT 2.0 to allow collaboration among all of the xCAT users.
  • Oct 31, 1999: xCAT 1.0 is born!
    xCAT started out as a project in IBM developed by Egan Ford. It was quickly adopted by customers and IBM manufacturing sites to rapidly deploy clusters.

Clone this wiki locally