--limit [exclusive:inclusive] not working as expected

[Mike Cavedon]

I have the following hosts defined:

[router]

rr01

rr[03:99]

rr[100:114]

I then execute a command that contains "--limit router[39:49]". Hosts rr41 through rr51 have the command executed on them. I'm expecting the command to be executed on hosts rr41 through rr50. Why does the command execute on host rr51?

Thanks.

[Kai Stian Olstad]

It's start on 0 not 1
router[0] = rr01

--
Kai Stian Olstad

[Mike Cavedon]

Is it [inclusive:inclusive], or is it [exclusive:inclusive]? I seem to recall the first parameter was exclusive. Maybe that was when [exclusive,inclusive] was supported?

If I have:

[router]

rr[01:99]

How do I deploy to hosts rr39 through rr49?

[Kai Stian Olstad]

On Thursday, 1 February 2018 22.28.46 CET Mike Cavedon wrote:
> On Thursday, February 1, 2018 at 4:03:33 PM UTC-5, Kai Stian Olstad wrote:
> > It's start on 0 not 1
> > router[0] = rr01
> >
> >
>

> Is it [inclusive:inclusive], or is it [exclusive:inclusive]? I seem to
> recall the first parameter was exclusive. Maybe that was when
> [exclusive,inclusive] was supported?
>
> If I have:
>
> [router]
> rr[01:99]
>
> How do I deploy to hosts rr39 through rr49?

It's inclusive:inclusive.
Since it start with 0 rr39 is 38 and rr49 is 48 so -l router[38:48]


--
Kai Stian Olstad

[Mike Cavedon]

Thanks. I asked another question about what appears to be a bug in the doc.