Return-Path: X-Original-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6F072DC50 for ; Sun, 18 Nov 2012 06:04:14 +0000 (UTC) Received: (qmail 98187 invoked by uid 500); 18 Nov 2012 06:04:14 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 98090 invoked by uid 500); 18 Nov 2012 06:04:13 -0000 Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ambari-dev@incubator.apache.org Delivered-To: mailing list ambari-dev@incubator.apache.org Received: (qmail 98061 invoked by uid 99); 18 Nov 2012 06:04:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Nov 2012 06:04:12 +0000 Date: Sun, 18 Nov 2012 06:04:12 +0000 (UTC) From: "Tom Beerbower (JIRA)" To: ambari-dev@incubator.apache.org Message-ID: <722403248.128692.1353218652085.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (AMBARI-1020) Start time, end time and resolution not set correctly for rrd.py call in Ganglia property provider. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Tom Beerbower created AMBARI-1020: ------------------------------------- Summary: Start time, end time and resolution not set correctly for rrd.py call in Ganglia property provider. Key: AMBARI-1020 URL: https://issues.apache.org/jira/browse/AMBARI-1020 Project: Ambari Issue Type: Sub-task Reporter: Tom Beerbower Assignee: Tom Beerbower In GangliaPropertyProvider the start time, end time and resolution are set as cs=, ce=, step=. Should be s=, e=, r= for rrd.py mode. This bug causes the arguments to be ignored so that all datapoints for the default range are returned. -- 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