All menus from appliance_console appearing twice

[goforgold]

I have installed jansa-1 release using Vagrant and VirtualBox.

[Fryguy]

@jvlcek I think you've been in the appliance console recently...have you noticed this?

[jvlcek]

@Fryguy No I have not. I just ran the appliance console from the master build and it does not do this.

[bdunne]

I just downloaded libvirt jansa-1 and the appliance console was normal.

@goforgold Are you using a SSH session? If so, does the VM console do the same thing?

[goforgold]

Hi @bdunne

I just brought up a new machine jansa-1 using vagrant and VBox and yes, this issue doesn't appear when accessing the console directly from VM console. But I still can reproduce it using SSH session or vagrant ssh.

I decided to use ivanchuk-7 for my POC.

[bdunne]

Interesting, I don't see it through SSH in my environment.

@NickLaMuro Do you use vagrant? If so, do you have a couple minutes to test this out?

[NickLaMuro]

I can check, but I wonder if it is something with the SSH connection via vagrant on windows that is having trouble here, as it seems like you are doing this via powershell. vagrant I am pretty sure uses net-ssh to do it's ssh communication across multiple operating systems, so it is possible we are attempting to pass a terminal return code that doesn't play nicely with powershell which would mean I would need a windows machine to reproduce properly (which I could make happen, just not with my current workstation).

That said, before I try to make any further "guesses", I will give it a test locally and report back.

[NickLaMuro]

Just to report back:

I used the 10.1.0 vagrant box (jansa) and it worked without the duplicate responses output.

I think I would need to test with powershell to confirm the issues being had, so I will maybe try to make that work later today, but no promises.

[bdunne]

Thanks @NickLaMuro

[NickLaMuro]

So after a bit of work to get my Windows box up and running with vagrant, I was able to reproduce:

Though, it was sporadic, and there were times where it didn't repeat. Might have something to do with how we are getting our terminal escape sequences for clear, and that might not mesh well with the Windows cmd terminal.

It does seem to be specific to our application, though, as top seems to work just fine. Forgot to check some other things like vim and less, but my guess would point to the code that we do the call to clear to get our escape sequences or possibly highline.

I would have to do some more investigation, but I can confirm this isn't a isolated incident, though seems specific to Windows hosts, possibly specific to when using vagrant ssh.

[NickLaMuro]

Another weird quirk (and I forgot to snip this), but I got a duplicate terminal prompt after I exited. Something like:

[vagrant@localhost] $ [vagrant@localhost] $

So I do think it is specific to the clear code that we use in appliance_console, and some combination of Windows and/or vagrant ssh.