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

SSH async execution is not disabling paging on multi-line output #33

jathanism opened this Issue Aug 21, 2012 · 0 comments


None yet
1 participant

jathanism commented Aug 21, 2012

This is related to the SSH auto-detection support that was added in Trigger 1.2. The problem is noticably occuring when a Brocade router is found in the path, but could be with any IOS-like device that is returning more than 25 lines of output causing the device to send a "--more--" prompt and blocks the entire program while it waits for user input (which is not displayed to the end user because it's async).

The workaround is to disabled SSH async execution on Brocade routers within the Trigger configuration.

Like so:

    'arista': ['SWITCH'],  # Known not to work w/ SSH ... yet
    'brocade': ['SWITCH', 'ROUTER'], # Namely the Brocade VDX (I also added ROUTER!)
    'dell': ['SWITCH'],    # Dell SSH is just straight up broken

What needs to happen is that the Base SSH channel (trigger.twister.TriggerSSHChannelBase) needs a way to accept an optional NetDevice object as an argument to the constructor. When this is set, it should populate the self.initialize list of commands to the appropriate "disable paging" command for the platform (e.g. terminal length 0 on Cisco). This functionality already exists within trigger.twister.IoslikeSendExpect (telnet) and needs to be implemented for SSH channels.

@ghost ghost assigned jathanism Aug 21, 2012

@jathanism jathanism closed this in 24788c3 Nov 21, 2012

jathanism added a commit that referenced this issue Nov 21, 2012

Merge pull request #53 from jathanism/develop
Console paging disabled now by default for SSH Channels (fixes #33)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment