thank you for replying。
But CloudStack4.6 mysql database cloud table configuration has no this name.
mysql> use cloud
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
mysql> select database();
+------------+
| database() |
+------------+
| cloud |
+------------+
1 row in set (0.00 sec)
mysql> desc configuration;
+---------------+---------------+------+-----+-------------------+-------+
| Field | Type | Null | Key | Default | Extra |
+---------------+---------------+------+-----+-------------------+-------+
| category | varchar(255) | NO | MUL | Advanced | |
| instance | varchar(255) | NO | MUL | NULL | |
| component | varchar(255) | NO | MUL | management-server | |
| name | varchar(255) | NO | PRI | NULL | |
| value | varchar(8191) | YES | | NULL | |
| description | varchar(1024) | YES | | NULL | |
| default_value | varchar(8191) | YES | | NULL | |
| updated | datetime | YES | | NULL | |
| scope | varchar(255) | YES | | NULL | |
| is_dynamic | tinyint(1) | NO | | 0 | |
+---------------+---------------+------+-----+-------------------+-------+
10 rows in set (0.00 sec)
mysql> select name,value from configuration where name like '%dynamic.apiche%';
Empty set (0.00 sec)
mysql>
roarain...@126.com
From: abhinandanprateek
Date: 2016-09-28 10:06
To: dev
Subject: [GitHub] cloudstack issue #1684: CLOUDSTACK-9489: the new config vars
that are added ...
Github user abhinandanprateek commented on the issue:
https://github.com/apache/cloudstack/pull/1684
@pdion891 The root of this issue is that 4.9 uses dynamic api checker,
which by default is not enabled. So even when the login succeed it does not go
anywhere as the access to any api is denied.
After upgrade run this on cloud db: update cloud.configuration set
value='true' where name='dynamic.apichecker.enabled';
This will fix the login issue.
I am sure this is there in upgrade documentation, @rhtyd will be the best
person to comment if it can be included in upgrade scripts. cc @jburwell
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
