Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D5AB21667A6 for ; Tue, 22 Aug 2017 10:23:10 +0200 (CEST) Received: (qmail 5015 invoked by uid 500); 22 Aug 2017 08:23:09 -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 5006 invoked by uid 500); 22 Aug 2017 08:23:09 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 5003 invoked by uid 99); 22 Aug 2017 08:23:09 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Aug 2017 08:23:09 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 7B9F3180414 for ; Tue, 22 Aug 2017 08:23:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id gYLQlh9p5YXr for ; Tue, 22 Aug 2017 08:23:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id C7CAD5FACE for ; Tue, 22 Aug 2017 08:23:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 05387E0295 for ; Tue, 22 Aug 2017 08:23:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id E03262537F for ; Tue, 22 Aug 2017 08:23:01 +0000 (UTC) Date: Tue, 22 Aug 2017 08:23:01 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-10052) Upgrading to 4.9.2 causes confusion/issues around dynamic roles usage MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-10052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136496#comment-16136496 ] ASF subversion and git services commented on CLOUDSTACK-10052: -------------------------------------------------------------- Commit 310195cbe25ac49160713e511d75525a16c9364b in cloudstack's branch refs/heads/4.9 from [~bhaisaab] [ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=310195c ] CLOUDSTACK-10052: Simplify dynamic roles enable checking (#2241) This fixes issue of enabling dynamic roles based on the global setting only. This also fixes application of the default role/permissions mapping on upgrade from 4.8 and previous versions to 4.9+. Previously, it would make additional check to ensure commands.properties is not in the classpath however this creates confusion for admins who may skip/skim through the rn/docs and assume that mere changing the global settings was not enough. Signed-off-by: Rohit Yadav > Upgrading to 4.9.2 causes confusion/issues around dynamic roles usage > --------------------------------------------------------------------- > > Key: CLOUDSTACK-10052 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10052 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Affects Versions: 4.9.2.0 > Reporter: Rohit Yadav > Assignee: Rohit Yadav > Fix For: 4.11.0.0, 4.9.3.0 > > > The dynamic roles feature need to be enabled based on the global setting only, the additional check to disable it when commands.properties is in the classpath is not widely known and causes issue on freshly installed system. -- This message was sent by Atlassian JIRA (v6.4.14#64029)