cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9489) When upgrading, new configuration are not updated.
Date Mon, 26 Sep 2016 12:53:20 GMT


ASF GitHub Bot commented on CLOUDSTACK-9489:

Github user dagsonstebo commented on the issue:
    @abhinandanprateek @jburwell @pdion891 - my twopence worth - I've come across issues with
this on two uprade projects in the last 8-10 months. Both cases were CCP to ACS upgrades:
    1) In the first case we hit an issue where the admin account could log in - but no users.
We carried out a preliminary check of this, and the suspicion was on changes in the MD5 authenticator
- but the client eventually chose to just reset all users passwords, hence no accurate RCA
carried out.
    2) In the second, more recent case the client wanted to use either PLAINTEXT or MD5 authenticators,
hence we updated the authenticators order similar to @pdion891 did above. During troubleshooting
of this trace level logging showed the authenticator order in ACS4.9 was respected, no issues
found. RCA of the underlying issue concluded with it being a user configuration and usage
issue rather than a bug.

> When upgrading, new configuration are not updated.
> --------------------------------------------------------------
>                 Key: CLOUDSTACK-9489
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.6.2, 4.7.1, 4.8.0, 4.9.0
>            Reporter: Pierre-Luc Dion
>            Assignee: Pierre-Luc Dion
>            Priority: Blocker
> When Upgrading CloudStack, new configurations (Global Settings) defined in  {{server/src/com/cloud/configuration/}}
are not populated.
> This file changed in 4.5 and 4.6 and those configurations are not applied when upgrading
to post 4.6.

This message was sent by Atlassian JIRA

View raw message