Integration tests for the CLI/workflow commands

Bug #1620983 reported by Julie Pichon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

It would be good to have some integration testing for the new client commands that use Mistral (overcloud node management, overcloud plan management, ...), to ensure everything keeps working well even as workflows and actions evolve and change.

I assume this exists for the existing 'baremetal' commands but I'm not sure where to find these. Pointers on where such tests should live would be appreciated.

Revision history for this message
Dougal Matthews (d0ugal) wrote :

Related, the old baremetal commands should be deprecated.

At the moment this is done in tripleo.sh (in tripleo-ci repos).

Changed in tripleo:
assignee: nobody → Dougal Matthews (d0ugal)
Dougal Matthews (d0ugal)
Changed in tripleo:
assignee: Dougal Matthews (d0ugal) → nobody
Revision history for this message
Emilien Macchi (emilienm) wrote :

This bug was last updated over 180 days ago, as tripleo is a fast moving project and we'd like to get the tracker down to currently actionable bugs, this is getting marked as Invalid. If the issue still exists, please feel free to reopen it.

Changed in tripleo:
status: Triaged → Invalid
Revision history for this message
Julie Pichon (jpichon) wrote :

Reopening as we still don't have any testing on the workflows in CI, even though it's becoming more and more important :)

Changed in tripleo:
status: Invalid → Triaged
Dougal Matthews (d0ugal)
Changed in tripleo:
importance: Medium → High
importance: High → Medium
Ryan Brady (rbrady)
Changed in tripleo:
milestone: none → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Revision history for this message
Emilien Macchi (emilienm) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE

Changed in tripleo:
importance: Medium → Undecided
status: Triaged → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.