cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Minying Bao (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-2005) Condition mapping entries / rules are not working as expected
Date Thu, 11 Apr 2013 06:41:16 GMT
Minying Bao created CLOUDSTACK-2005:

             Summary: Condition mapping entries / rules are not working as expected
                 Key: CLOUDSTACK-2005
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: VNC Proxy
    Affects Versions: 4.2.0
         Environment: Build No.#133 (CloudStack-non-OSS-MASTER-133-rhel6.3.tar.gz)
XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr Server, Win7Entx64SP1
for Client machine. 
            Reporter: Minying Bao
             Fix For: 4.2.0

Setup the CloudStack environments with build 4.2#133.
Add template and then create as an instance.
Manually modify the "condition mapping entries" in the ajaxkeys.js file, synchronize the script
to v-2-VM.
Launch the VM via ConsoleProxy in client machine, to check if the "condition mapping entries"
are working as expected.

The requirements link have the following list of rules/conditional mapping entries:

Conditional mapping entry   { 
     type: <event type>, code: <mapped key code>, modifiers: <modifiers>,
     shift : <shift state match condition>,                -- match on shift state
     guestos : <guest os match condition>,         -- match on guestos type
     browser: <browser type match condition>,      -- match on browser
     browserVersion: <brower version match condition>      -- match on browser version

Expected Result
All the condition mapping entries / rules should be working as expected.

Actual Result 
Condition mapping entries / rules are not working as expected.
Please refer to attached for details.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message