Bug 1397081 - [Automate] - unknown attribute 'source' for MiqAeDomain. [miq_ae_tools/import_automate_datastore]
Summary: [Automate] - unknown attribute 'source' for MiqAeDomain. [miq_ae_tools/import...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: GA
: cfme-future
Assignee: mkanoor
QA Contact: Dave Johnson
URL:
Whiteboard: ui:automate
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-21 14:36 UTC by Pavol Kotvan
Modified: 2016-11-22 12:18 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-22 12:18:49 UTC
Category: Bug
Cloudforms Team: Unknown
Target Upstream Version:

Attachments (Terms of Use)
Screen shot of different branches (77.14 KB, image/png)
2016-11-21 19:23 UTC, mkanoor 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Comment 2 mkanoor 2016-11-21 19:22:26 UTC 
The source attribute was added to the Euwe release of ManageIQ which replaces the old system attribute in the miq_ae_namespace table.

Kevin Morey maintains different branches of his Automate model for different versions. His master was updated last weekend and was built with the CFME 4.2 exporter, which has the source attribute.

You can't take his master branch which is only for CFME 4.2 and import it into previous versions of the product like CFME 4.1

Please use the correct branch when testing this.
I have attached a screen shot which shows the different branches that shows the different branches.

Please close this issue once you have verified this with the correct version.
Comment 3 mkanoor 2016-11-21 19:23:12 UTC 
Created attachment 1222470 [details]
Screen shot of different branches
Comment 4 mkanoor 2016-11-21 19:56:59 UTC 
I spoke to Kevin he is going to be updating his master to remove the source attribute. So if you go looking for it now it might work. But the crux of the issue is still you can't use new data on older versions
Note You need to log in before you can comment on or make changes to this bug.