Service destroy should warn if using '-l HOSTNAME' instead of '-kl HOSTNAME'

Bug #2058028 reported by Martin Ananda Boeker
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kayobe
Triaged
Wishlist
Unassigned

Bug Description

Env: 2023.1

I just ran this command:

kayobe overcloud service destroy --yes-i-really-really-mean-it --limit OMC3-RG4-01-STR-03

Because I wanted to just remove OMC3-RG4-01-STR-03. However kayobe started destroying everything. There should really be some kind of warning that for this you should use "-kl" for kolla-limit instead of "-l" for regular limit!

Revision history for this message
Will Szumski (willjs) wrote :

Ouch, This is a nasty example of how people can fall foul of the kolla/kayobe limit split.

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

Other bug subscribers

Remote bug watches

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