Re: [Xen-API] Console Login Bug?

[Graham Frank <jakiao@xxxxxxxxx>]

Tested in XenCenter 6.1 build 872 and am getting the same results.
--Graham

On Mon, Jun 10, 2013 at 10:27 AM, Brian Menges <bmenges@xxxxxxxxxx> wrote:
> Recommend upgrading first to XenCenter 6.1 (build 872)
>
> - Brian Menges
> Principal Engineer, DevOps
> GoGrid | ServePath | ColoServe | UpStream Networks
>
>
> -----Original Message-----
> From: xen-api-bounces@xxxxxxxxxxxxx [mailto:xen-api-bounces@xxxxxxxxxxxxx] On 
> Behalf Of Graham Frank
> Sent: Saturday, June 08, 2013 17:04
> To: xen-api@xxxxxxxxxxxxx
> Subject: Re: [Xen-API] Console Login Bug?
>
> Some additional details --
>
> 1. Happens in XenCenter 6.0.2 53158 as well 2. Discovered Shift 3 backspaces 
> while Shift 2 erases back to home
>
> On Sat, Jun 8, 2013 at 6:55 PM, Graham Frank <jakiao@xxxxxxxxx> wrote:
>> Hey all,
>>
>> I'm running a handful of resource pools running XCP 1.6 61809c. The
>> XenCenter version is 6.0 50489.
>>
>> Beginning last night, a strange problem has spread across all of our
>> Linux VMs. Any Linux VM with an @ symbol in the password appears to be
>> triggering a bug in the XenCenter console.
>>
>> Example: I login to a Linux VM over console and it works fine. I exit.
>> I try to login again. All further attempts fail. And now I find that
>> any attempt to console to any VM on any resource pool where I have to
>> type the @ results in complete failure. This includes VMs that I could
>> login to just moments ago.
>>
>> So what's going on? You can see it when you try to type the password
>> as the username. Upon sending the @ symbol (either thru the keystroke
>> or pasting the text), all text prior to the @ symbol is erased.
>>
>> SSH still works and the VMs individually appear to be okay. KVM to
>> real Linux servers doesn't experience this issue either. If you're
>> already logged into the VM in the Xen console, then you can type @ all
>> you want. This issue is not happening on Windows VMs as far as I can
>> tell.
>>
>> It is happening on multiple computers to all of our staff. The issue
>> began last night.
>>
>> Does anybody have some insight to this issue? Thanks.
>>
>> --Graham
>
> _______________________________________________
> Xen-api mailing list
> Xen-api@xxxxxxxxxxxxx
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
>
> The information contained in this message, and any attachments, may contain 
> confidential and legally privileged material. It is solely for the use of the 
> person or entity to which it is addressed.  Any review, retransmission, 
> dissemination, or action taken in reliance upon this information by persons 
> or entities other than the intended recipient is prohibited. If you receive 
> this in error, please contact the sender and delete the material from any 
> computer.
>
> _______________________________________________
> Xen-api mailing list
> Xen-api@xxxxxxxxxxxxx
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api