Baremetal API tests are dependent on the fake driver
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Fix Released
|
Undecided
|
Yuiko Takada |
Bug Description
The baremetal API tests perform some basic CRUD operations against the Ironic API. They do not require access to physical hardware and currently target the 'fake' ironic provisioning driver. This is fine for the gate testing, where 'fake' is enabled in the deployment, but the tests should be made to function against other drivers that would be enabled in a real-world cloud.
This presents a couple of caveats:
* Node information would need to be supplied to the test cases. Things like MAC addresses, IPMI credentaisl, etc. Perhaps we can define a JSON format (similar to tripleo-incubator) for defining node inventory as part of configuration.
* Running the API tests against a running non-idle cloud with existing users can be dangerous or cause undefined failures. For instance, creating a new node in Ironic as part of a test would make the node immediately available to any Nova service running in that cloud, and available for scheduling users instances. In the meantime, Tempest tests would be powering the same nodes off, updating properties. Deployers wishing to run these verification tests should do so at their own risk.
As a first step, we should make the current tests skippable if the 'fake' driver is not available. Longer term, we can extend to support other Ironic drivers (pxe_ssh, pxe_ipmi, etc).
tags: | added: ironic-tempest |
Changed in tempest: | |
status: | New → In Progress |
FYI: now a related patch has been proposed on https:/ /review. openstack. org/#/c/ 92996/