[BOLT-1075] command : commands fail if in a remote session to Windows - Puppet Tickets

XML

Word

Printable

Type: Bug
Status: Closed
Priority: Normal
Resolution: Won't Do
Affects Version/s: None
Fix Version/s: None
Component/s: bolt, Windows
Labels:
- bolt
- closed-github-move
- eyu
- ghm
- known-issue-added
- windows

Release Notes:
Known Issue
Release Notes Summary:

Hide
Interactive tools fail when run in a remote PowerShell session. As such, using `--password` to prompt for a password when running Bolt will trigger an error noting EBADF. Work-arounds include putting the password in bolt.yaml or an inventory file, passing the password on the command-line, or not running Bolt over a remote PowerShell session.

Show
Interactive tools fail when run in a remote PowerShell session. As such, using `--password` to prompt for a password when running Bolt will trigger an error noting EBADF. Work-arounds include putting the password in bolt.yaml or an inventory file, passing the password on the command-line, or not running Bolt over a remote PowerShell session.

Bolt Version 1.8.1

If you are remoted into a Windows machine and attempt to run a command, the command may fail with an `Bad file descriptor` error.

This was discovered during the Getting Started with Puppet training class.

Desired Behavior: The command should execute normally.

Actual Behavior: A bad file descriptor error is encountered.

duplicates

BOLT-627 Secure password prompt fails on Windows