Add --timeout to cloud-init status --wait
Bug #1999876 reported by
Alberto Contreras
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-init |
Expired
|
Wishlist
|
Unassigned | ||
Bug Description
Add a supplemental / optional timeout flat to the `cloud-init status --wait` command to not infinitely block.
This could be useful for testing context, as an example.
Context: https:/
| tags: | added: bit |
| tags: |
added: bitesize removed: bit |
| Changed in cloud-init: | |
| importance: | Undecided → Wishlist |
| summary: |
- Add --timout to cloud-init status --wait + Add --tiemout to cloud-init status --wait |
| summary: |
- Add --tiemout to cloud-init status --wait + Add --timeout to cloud-init status --wait |
| Changed in cloud-init: | |
| status: | New → Triaged |
Revision history for this message
| Brett Holman (holmanb) wrote | #1 |
Revision history for this message
| James Falcon (falcojr) wrote | #2 |
| Changed in cloud-init: | |
| status: | Triaged → Expired |
To post a comment you must log in.
Quoting from the irc logs:
> blocking forever is usually a nono, that's my thought
Agreed. However, this is out of our control. We are awaiting on other systemd units to return before exiting.
Maybe we make this wait forever behavior a little more obvious in the help/manpage output?
> this is in a script that runs tests, so specially here I don't want forever blocks
I guess if you don't care what state your machine is in before doing things on the machine, then a timeout might be useful?
If we add this, lets make sure to document well that using `--timeout` means that system configuration will not be completed at exit.