Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CLI options "--async" and "--batch-size" are not compatible. #25362

Open
jarpy opened this issue Jul 13, 2015 · 8 comments
Open

CLI options "--async" and "--batch-size" are not compatible. #25362

jarpy opened this issue Jul 13, 2015 · 8 comments
Labels
Bug broken, incorrect, or confusing behavior Core relates to code central or existential to Salt P3 Priority 3 severity-low 4th level, cosemtic problems, work around exists
Milestone
Argon v3008.0

Comments

@jarpy
Copy link
Contributor

jarpy commented Jul 13, 2015

When invoking the Salt command line client with both the --async and --batch-size options, --async is ignored. The batch is run in the foreground, and the shell waits for it to return.
@jarpy jarpy changed the title --async and --batch-sizeCLI options are not compatible. CLI options "--async" and "--batch-size" are not compatible. Jul 13, 2015
@cachedout
Copy link
Contributor

Hmm, yes. I'm not sure this ever worked. (I honestly haven't tried before.) We'll have to take a look here and see what it will take to ensure that batch mode runs correctly in asynchronous mode. Thanks very much for letting us know. Sorry about the oversight here!

@cachedout cachedout added Bug broken, incorrect, or confusing behavior severity-low 4th level, cosemtic problems, work around exists Core relates to code central or existential to Salt P3 Priority 3 labels Jul 13, 2015
@cachedout cachedout added this to the Approved milestone Jul 13, 2015
@mimianddaniel
Copy link

The fact the each new batch job gets its own jid, and current async job runs under a single jid, i am not sure if this would be a easy fix. @cachedout any idea as to how to make this work??

@stale
Copy link

stale bot commented Jun 25, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

@stale stale bot added the stale label Jun 25, 2018
@stale stale bot closed this as completed Jul 2, 2018
@brandon-sling
Copy link

This still seems to be an issue in 2019.2.3

@danlsgiga
Copy link
Contributor

Just noticed this behaviour on 3000.2 as well. Can this be reopened?

@danlsgiga
Copy link
Contributor

I guess this is in the works according to #55268

@DmitryKuzmenko
Copy link
Contributor

@danlsgiga sorry for late response. I've reopened this.

@Ch3LL
Copy link
Contributor

Ch3LL commented Aug 28, 2023

I've confirmed this is still an issue on the head of 3006.x

@Ch3LL Ch3LL self-assigned this Aug 28, 2023
@Ch3LL Ch3LL modified the milestones: Approved, Argon v3008 Aug 28, 2023
@dwoz dwoz unassigned Ch3LL Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug broken, incorrect, or confusing behavior Core relates to code central or existential to Salt P3 Priority 3 severity-low 4th level, cosemtic problems, work around exists
Projects
None yet
Milestone
Argon v3008.0
Development

No branches or pull requests
7 participants
@cachedout @jarpy @danlsgiga @DmitryKuzmenko @Ch3LL @mimianddaniel @brandon-sling