-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automate url open fixes #6040
Automate url open fixes #6040
Conversation
f605530
to
d46bc6b
Compare
Checked commits martinpovolny/manageiq-ui-classic@f6d2260~...d46bc6b with ruby 2.4.6, rubocop 0.69.0, haml-lint 0.20.0, and yamllint 1.10.0 |
Everything seems to be working for me except for Generic Object. What I am experiencing there is that the automate method gets invoked, all is set, but the associated So the UI ends up in an endless loop of The automate code for GO that I am testing:
I am using https://gist.github.com/martinpovolny/4d960e550a7838a9b04cb4d8396514b0 to create a Service with GO for testing. This will been some help from someone who knows automate. And I found this issue: #6048 |
@pkomanek : can you help me with the issue in the last comment? (Automate method seems to be finished according to the logs, but the associated
|
Seems the worker crashes fulfilling the MiqTask in question:
|
@mzazrivec : from the above stacktrace I conclude that the last issue is a bug somewhere between Core and Automate. I think that this PR can be merged and the last issue needs to be worked on separately. |
@lfu Can you look into the stacktrace above? |
This method is called by YAML.dump when miq_queue sets the callback result into miq_task.task_results. Reported by ManageIQ/manageiq-ui-classic#6040 (comment).
Returning back workspace breaks the custom button for generic objects. Reported by ManageIQ/manageiq-ui-classic#6040 (comment). https://bugzilla.redhat.com/show_bug.cgi?id=1550002
Fixes for:
https://bugzilla.redhat.com/show_bug.cgi?id=1550002
wait_for_task
route missing in Service controller.Tested automate code for "Provider":
For "Provider" testing also ManageIQ/manageiq#19157 is needed.(merged)Tested automate code for "Service":
Tested automate code for "CloudTenant":
Tested automate code for "Tenant":
Requires automation engine PR: ManageIQ/manageiq-automation_engine#350(merged)Notes:
How to access a number of objects: https://pemcg.gitbooks.io/introduction-to-cloudforms-automation/content/chapter6/evm_and_the_workspace.html
Note that
$evm.root['vmdb_object_type']
contains the class for all the objects.However
$evm.root['target_object_ids']
is NOT set for the singular case (and thus is useless for this case). I am not aware of any generic way to get the ID of the target object in the singular case.Note that a number of variables such as
$evm.root['vm']
or$evm.root['user']
exist but they do NOT contain the target object in all cases.The
$evm.root[...]
variablesuser
,group
andtenant
contain the LOGGED IN user insted of the target object one.For the case where User is the target class,
$evm.root['user_id']
is set with the ID of the target object.