kayobe overcloud service deploy --limit hostname not limiting to that hostname

[Martin Ananda Boeker]

Everything on version 2023.1

I ran `kayobe overcloud service deploy --limit storage0,storage1`

Pages and pages of output of course, here's a small snippet:

RUNNING HANDLER [prometheus : Restart prometheus-server container] *********************************************************************************************************************************************************************
Thursday 08 February 2024 12:43:35 +0000 (0:00:00.042) 0:02:14.524 *****
changed: [control0]
changed: [control1]

RUNNING HANDLER [prometheus : Restart prometheus-node-exporter container] **************************************************************************************************************************************************************
Thursday 08 February 2024 12:43:42 +0000 (0:00:06.655) 0:02:21.179 *****
changed: [storage0]
changed: [storage2]
changed: [storage1]
changed: [control0]
changed: [control1]

There were lots of other things changed as well, even on compute0 and 1. I don't know if that's intentional and needed because the configuration on the storage nodes changed, but it's unexpected.

[Will Szumski (willjs)]

Use: kayobe overcloud service deploy --kolla-limit storage0,storage1`

This is a quirk of running kolla playbooks and kayobe playbooks which may need different limits. Possibly we could combine the two, but sometimes you need different limits for each.

[Martin Ananda Boeker (mboeker)]

Gotcha, thank you for that info!