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 0D70F10F94 for ; Thu, 7 Nov 2013 23:25:18 +0000 (UTC) Received: (qmail 12262 invoked by uid 500); 7 Nov 2013 23:25:17 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 12232 invoked by uid 500); 7 Nov 2013 23:25:17 -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 12183 invoked by uid 500); 7 Nov 2013 23:25:17 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 12141 invoked by uid 99); 7 Nov 2013 23:25:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Nov 2013 23:25:17 +0000 Date: Thu, 7 Nov 2013 23:25:17 +0000 (UTC) From: "Nitin Mehta (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CLOUDSTACK-5091) Upgrade to 4.2 - used cpu is getting bumped up when the over provisioning factor > 1 - script fix MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Nitin Mehta created CLOUDSTACK-5091: --------------------------------------- Summary: Upgrade to 4.2 - used cpu is getting bumped up when the over provisioning factor > 1 - script fix Key: CLOUDSTACK-5091 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5091 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Nitin Mehta Assignee: Nitin Mehta Fix For: 4.2.0 Upgrade to 4.2 - used cpu is getting bumped up when the over provisioning factor > 1 Provide a script fix for this - Will solve the issue where used cpu is getting bumped up when the over provisioning factor > 1. This would need to be documented and run manually as an additional step by the admin. Also write KB article -- This message was sent by Atlassian JIRA (v6.1#6144)