Team,
While doing service assignment level operation in SDNC, I’m facing the bellow
error:
2018-10-31 01:18:49,033 | INFO | qtp531183832-146 | message-log
| 223 - org.onap.ccsdk.sli.core.sli-recording - 0.3.1 |
|2018-10-31T01:18:49:33+00:00|LAINA: naming-policy-generate-name: read
properties file.|
2018-10-31 01:18:49,035 | INFO | qtp531183832-146 | SvcLogicExprListener
| 221 - org.onap.ccsdk.sli.core.sli-common - 0.3.1 | Outcome (DELETE) not
found, keys are { (ASSIGN) (Other)}
2018-10-31 01:18:49,036 | INFO | qtp531183832-146 | message-log
| 223 - org.onap.ccsdk.sli.core.sli-recording - 0.3.1 |
|2018-10-31T01:18:49:36+00:00|LAINA: naming-policy-generate-name:
input.policy-instance-name is not set but input.policy is not ASSIGN|
2018-10-31 01:18:49,037 | INFO | qtp531183832-146 | message-log
| 223 - org.onap.ccsdk.sli.core.sli-recording - 0.3.1 |
|2018-10-31T01:18:49:37+00:00|LAINA: naming-policy-generate-name:
input.vfc-customization-uuid is not set|
2018-10-31 01:18:49,038 | INFO | qtp531183832-146 | SvcLogicExprListener
| 221 - org.onap.ccsdk.sli.core.sli-common - 0.3.1 | Outcome (DELETE) not
found, keys are { ("") (Other)}
2018-10-31 01:18:49,039 | INFO | qtp531183832-146 | message-log
| 223 - org.onap.ccsdk.sli.core.sli-recording - 0.3.1 |
|2018-10-31T01:18:49:39+00:00|LAINA: naming-policy-generate-name: input.action
is not set or invalid|
2018-10-31 01:18:49,040 | INFO | qtp531183832-146 | message-log
| 223 - org.onap.ccsdk.sli.core.sli-recording - 0.3.1 |
|2018-10-31T01:18:49:40+00:00|LAINA: naming-policy-generate-name: call
generate-unique-name: constructed-name|
2018-10-31 01:18:49,056 | INFO | qtp531183832-146 | SvcLogicServiceImpl
| 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.1 | About to execute
graph SvcLogicGraph [module=GENERIC-RESOURCE-API,
rpc=naming-policy-generate-unique-name, mode=sync, version=1.4.1-SNAPSHOT,
md5sum=2fa34baae05d4b9f3f58e35c47b5e715]
2018-10-31 01:18:49,057 | INFO | qtp531183832-146 | SvcLogicServiceImpl
| 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.1 | About to execute
node # 1 (block)
2018-10-31 01:18:49,071 | INFO | qtp531183832-146 | SvcLogicServiceImpl
| 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.1 | About to execute
graph SvcLogicGraph [module=GENERIC-RESOURCE-API, rpc=rollback-generated-names,
mode=sync, version=1.4.1-SNAPSHOT, md5sum=cc9c356401aab548f128f1b1c9a95a4a]
2018-10-31 01:18:49,075 | INFO | qtp531183832-146 | SvcLogicServiceImpl
| 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.1 | About to execute
node # 1 (block)
2018-10-31 01:18:49,078 | INFO | qtp531183832-146 | SvcLogicExprListener
| 221 - org.onap.ccsdk.sli.core.sli-common - 0.3.1 | Outcome
(33bbc46e-afa4-4ced-b37c-50eef0ee6445) not found, keys are { ("")}
2018-10-31 01:18:49,129 | ERROR | qtp531183832-146 | CachedDataSource
| 219 - org.onap.ccsdk.sli.core.dblib-provider - 0.3.1 | <sdnctldb01>
Failed to execute: SELECT distinct prefix from GENERIC_RESOURCE_NAME WHERE type
= 'SERVICE_INSTANCE' AND context_id = '33bbc46e-afa4-4ced-b37c-50eef0ee6445'
with no arguments.
java.sql.SQLSyntaxErrorException: (conn=34661) Unknown column 'context_id' in
'where clause'
at
org.mariadb.jdbc.internal.util.exceptions.ExceptionMapper.get(ExceptionMapper.java:158)
[205:org.mariadb.jdbc:2.1.1]
at
org.mariadb.jdbc.internal.util.exceptions.ExceptionMapper.getException(ExceptionMapper.java:118)
[205:org.mariadb.jdbc:2.1.1]
at
org.mariadb.jdbc.MariaDbStatement.executeExceptionEpilogue(MariaDbStatement.java:235)
[205:org.mariadb.jdbc:2.1.1]
at
org.mariadb.jdbc.MariaDbPreparedStatementClient.executeInternal(MariaDbPreparedStatementClient.java:224)
[205:org.mariadb.jdbc:2.1.1]
at
org.mariadb.jdbc.MariaDbPreparedStatementClient.execute(MariaDbPreparedStatementClient.java:159)
[205:org.mariadb.jdbc:2.1.1]
at
org.mariadb.jdbc.MariaDbPreparedStatementClient.executeQuery(MariaDbPreparedStatementClient.java:173)
[205:org.mariadb.jdbc:2.1.1]
Here is the column info for the table it’s trying to update:
mysql> show columns from GENERIC_RESOURCE_NAME;
+------------+--------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+------------+--------------+------+-----+---------+-------+
| type | varchar(50) | NO | PRI | NULL | |
| name | varchar(255) | NO | PRI | NULL | |
| prefix | varchar(255) | YES | | NULL | |
| name_index | int(11) | YES | | NULL | |
| content_id | varchar(255) | YES | | NULL | |
+------------+--------------+------+-----+---------+-------+
5 rows in set (0.00 sec)
Looks like there is a discrepancy between the table schema and the interaction
with it within the naming-policy-generate-unique-name DG.
Can we make sure the table schema represent latest?
Thanks,
Alexis
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13426): https://lists.onap.org/g/onap-discuss/message/13426
Mute This Topic: https://lists.onap.org/mt/27805698/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
