Is there an equivalent of cloud-init status --wait?
See original GitHub issueIs there an equivalent of cloud-init status --wait
of cloud-init in cloudbase-init?
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
CLI Interface - cloud-init 22.4.2 documentation
Generally run by OS init systems to execute modules:config and modules:final boot stages. This executes cloud config Module Reference configured ...
Read more >How do detect that cloud-init completed initialization
cloud -init status gives simple human-readable or programmatic output for what cloud-init is doing and whether it has finished successfully. It ...
Read more >Cloud-init v.18.2: CLI subcommands - Ubuntu
First, cloud-init status gives simple human-readable or programmatic output for what cloud-init is doing and whether it has finished ...
Read more >cloud-init - Read the Docs
Report cloud-init status or wait on completion. ... If your version of cloud-init does not have the collect-logs subcommand, ...
Read more >Bug #1890528 “cloud-init status --wait returns before cloud ...
I was expecting `cloud-init status --wait` to only return after cloud-final has completed, but I discovered today that it can return early ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
My example VM ended-up with these registry keys/values:
The registry key
b3d1dc735800195b8f62
seems to be the value ofinstance-id
property that is inside the cidatameta-data
json file, is that correct?From an external viewpoint, how do we known how many plugins exist?
How do we known when all the plugins are “done” (it seems that not all plugins end-up with the same value)?
And how we do this in a way that is not tied with a specific cloud or plugin?
I think we should have a command available in the cloudbase-init package that deals with all this; I can propose one when the questions above are cleared up 😃
For reference, this is what cloud-init returns:
This is also described at https://cloudinit.readthedocs.io/en/latest/topics/cli.html#cli-status.
as a workaround, we’re using the following powershell: