Bug 1280017 - Automate instance requires fully-qualified path to properly follow relationship
Automate instance requires fully-qualified path to properly follow relationship
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: GA
: 5.5.0
Assigned To: mkanoor
Dave Johnson
Depends On:
  Show dependency treegraph
Reported: 2015-11-10 13:10 EST by Jared Deubel
Modified: 2015-11-12 12:02 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-11-12 12:02:57 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jared Deubel 2015-11-10 13:10:38 EST
Description of problem:
Need to fill in full path in order to get automate methods to work. /Customer/System/Request/ needs to be changed to full path Domain/Customer/System/Request/. 

Previously this was working in CloudForms 5.3.

--] I, [2015-11-09T17:28:34.129276 #2591:1295ea4]  INFO -- : Updated namespace [miqaedb:/System/Request/vm_delete#create  Customer/System]
[----] I, [2015-11-09T17:28:34.188260 #2591:1295ea4]  INFO -- : Following Relationship [miqaedb:/Customer/Company/Methods/vm_delete#create]
[----] I, [2015-11-09T17:28:34.224449 #2591:1295ea4]  INFO -- : Updated namespace [Company/Methods/vm_delete  Customer/Company]
[----] I, [2015-11-09T17:28:34.228946 #2591:1295ea4]  INFO -- : Invoking [inline] method [/Customer/Company/Methods/vm_delete] with inputs [{}]

Version-Release number of selected component (if applicable):

How reproducible:
Comment 2 Greg McCullough 2015-11-10 13:19:51 EST
Madhu - Please work with Jared on this issue, he has an environment that recreates the issue using a custom button.
Comment 3 mkanoor 2015-11-11 10:27:07 EST
In Automate relationships the paths should have a leading slash, so that we can break the URI into ints constituent parts. After we do the split we expect to see a path.

If the leading slash is missing we get an INVALID_URI during splitting the URI.

In the customers case their paths might not have a leading slash. Waiting for Jared to confirm that. We tested this change on Jared's server by adding a leading slash in the URI for the relationships.

Regarding the inherits attribute in the miq_ae_class, that is legacy experimental stuff. The old UI would allow you set the inherits to the Automate, which has been removed in the newer versions of the UI. Old customer databases might have remnants of the inherits field accidentally set from the UI. After we introduced domains, the legacy inherits columns were not updated to include the domain as part of the name causing the failure.

We would have to clear out the inherits column from the miq_ae_class from the rails console using 
MiqAeClass.where("inherits IS NOT NULL").each { |c| c.update_attributes(:inherits => nil) }
Comment 4 mkanoor 2015-11-12 12:02:57 EST
The customer had a similar named domain and namespace /PitneyBowes & /Customer/PitneyBowes.
The domain is called PitneyBowes and in the Customer domain we have a namespace called PitneyBowes.

We will fix this in the next release.

The customer changed the domain name from PitneyBowes to PB, which resolved the issue.

Note You need to log in before you can comment on or make changes to this bug.