-
Notifications
You must be signed in to change notification settings - Fork 834
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.
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
Don't hang waiting for input from commands #2231
Comments
Launchpad user Clint Byrum(clint-fewbar) wrote on 2011-12-16T21:44:40.580295+00:00 This makes sense to me. Its simpler even than you suggest. I see no good reason that cloud-init ever should read from stdin, so it should probably just re-open stdin as /dev/null. Any program that hangs waiting for input from a non tty like /dev/null is doing things wrong, or is being invoked incorrectly. I don't see this as High though, as it can be worked around by not running programs that wait for input from stdin. Dropping to Medium, and forwarding to cloud-init upstream project. |
Launchpad user Scott Moser(smoser) wrote on 2011-12-19T22:03:38.613759+00:00 fix-commited in upstream cloud-init at revision 490. |
Launchpad user Launchpad Janitor(janitor) wrote on 2011-12-22T09:10:13.291010+00:00 This bug was fixed in the package cloud-init - 0.6.3~bzr497-0ubuntu1 cloud-init (0.6.3~bzr497-0ubuntu1) precise; urgency=low
|
This bug was originally filed in Launchpad as LP: #903993
Launchpad details
Launchpad user Drew Mazurek(mazurek-4) wrote on 2011-12-13T23:09:24.184811+00:00
If a command is interactive and opens up stdin, the entire deploy will hang. cloud-init should close stdin if anything tries to open it. Examples of this are:
or
(Specifically without the -y option. -y on those commands would be a workaround for this bug.)
The text was updated successfully, but these errors were encountered: