Details
-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
8
-
Severity 3 - Minor
-
1
-
Description
Issue Summary
When adding a "User" attribute to an object type in an Insight Discovery object schema and update it with a valid user causing auto import from Insight Discovery failed.
This is reproducible on Data Center: (yes) / (no)
Steps to Reproduce
- Create a new object schema
- Import manually from Insight Discovery
- Then, update Host object type by adding a new User attribute type
- Then, update an existing object with a valid user for the user attribute.
- Then, set up a auto import from Insight Discovery to Cloud.
- Execute the import
Expected Results
The import was successfully executed because I didn't expect to get any "User" value from Insight Discovery.
Actual Results
Import failed with the error below:-
EC2AMAZ-GQ0KM30(AL-38055): context: rlabs-insight-attribute-2625; messages: [ErrorMessage
];
If there is group validation performed for the user, then you might see the below error message
EC2AMAZ-5QENLDO (Object key: DIS1-2311): User(s) (557058:f481769c-2afd-498e-97a2-27b533cd6626) is not member of configured Jira groups (Assets);
Workaround
There are 2 workaround :-
- Remove the "User" attribute and use a Text attribute instead and perform the auto import from Insight Discovery
- Export the file from Insight Discovery and perform manual import to Insight Cloud.
Attachments
Issue Links
- is caused by
-
JSDCLOUD-10732 Add support to User type attributes on External/Discovery Import
- Reviewing
- is duplicated by
-
JSDSERVER-12334 Assets Discovery import error 'rlabs.insight.i18n.constraint.violation.ObjectAttributeValueBean.NotFound.Users' is shown on Jira Cloud if an object has a manually assigned User value for a manually added User type attribute
- Closed
- mentioned in
-
Page Loading...