Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-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 A8F2FD164 for ; Mon, 12 Nov 2012 17:35:17 +0000 (UTC) Received: (qmail 86141 invoked by uid 500); 12 Nov 2012 17:35:17 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 86088 invoked by uid 500); 12 Nov 2012 17:35:16 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 86056 invoked by uid 99); 12 Nov 2012 17:35:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Nov 2012 17:35:16 +0000 Date: Mon, 12 Nov 2012 17:35:12 +0000 (UTC) From: "Daniel Jensen (JIRA)" To: cloudstack-dev@incubator.apache.org Message-ID: <698621337.101465.1352741716271.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (CLOUDSTACK-472) Missing command in installation document MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Daniel Jensen created CLOUDSTACK-472: ---------------------------------------- Summary: Missing command in installation document Key: CLOUDSTACK-472 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-472 Project: CloudStack Issue Type: Bug Components: Doc Affects Versions: 4.0.0 Reporter: Daniel Jensen Priority: Minor If you follow the installation guide for setting up the mysql DB the CS4 documentation is missing one command that will prevent the API service from starting. After section 4.5.4.1.5 the following command should be run: cloud-setup-management -- 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