Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 06BCBF59C for ; Mon, 13 May 2013 14:53:20 +0000 (UTC) Received: (qmail 21541 invoked by uid 500); 13 May 2013 13:53:20 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 21202 invoked by uid 500); 13 May 2013 13:53:16 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 21137 invoked by uid 500); 13 May 2013 13:53:15 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 21133 invoked by uid 99); 13 May 2013 13:53:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 May 2013 13:53:15 +0000 Date: Mon, 13 May 2013 13:53:15 +0000 (UTC) From: "venkata swamybabu budumuru (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CLOUDSTACK-2460) [GSLB] [EVENTS] MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 venkata swamybabu budumuru created CLOUDSTACK-2460: ------------------------------------------------------ Summary: [GSLB] [EVENTS] Key: CLOUDSTACK-2460 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2460 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.0 Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f Reporter: venkata swamybabu budumuru Assignee: Murali Reddy Priority: Trivial Fix For: 4.2.0 Steps to reproduce : 1. Have CloudStack with at least one advanced zone 2. add a GSLB device 3. Login as a non-ROOT domain user and create a GSLB rule 4. verify the EVENT Observations: (i) It successfully generated an event but, with little discrepancy in the description Here is the description: Description creating a global load balancer: GSLB1 for account: null (ii) we need to update the account with right information. -- 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: http://www.atlassian.com/software/jira