Interactive Shell Commands Are Used

Symptoms

When a shell command that requires users to enter the next instruction is deployed, for example, yum install, cat ${filename}, or awk '{print $0}' ${filename}, the progress is stuck in deploying state until timeout occurs.

Cause Analysis

The shell command is remotely pushed to the target host for deployment and interactive operations are not allowed. If an interactive operation is required in the command, the host keeps waiting for subsequent input instructions until the deployment times out. In this case, the deployment fails and a message indicating deployment timeout is displayed.

Solution

When deploying the action Run Shell Commands, add subsequent operation instructions, for example, yum –y install, to the command in advance.

Parent topic: Running Shell Commands

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot