Red Hat Bugzilla – Bug 839205
ovirt-engine-restapi : [RFE] There is no way to know which hooks are installed on a host
Last modified: 2016-02-10 14:21:40 EST
Description of problem:
On GUI I have the option to see which hooks are install on a specific host.
I see fields like event name , script name , property name and value .
I didn't found this information using the api .
Version-Release number of selected component (if applicable):
Steps to Reproduce:
patch posted upstream:
Created attachment 675571 [details]
Created attachment 675572 [details]
did you pas the header to get all entity details?
are you testing against SF3?
(In reply to comment #5)
> did you pas the header to get all entity details?
it's implemented as host sub-collection.
I am testing against sf3.
I didn't pass any special header.
See Michael's comment (comment 7) please try:
Please consider add links to the hooks response similar to nics.
addition: for each hook, add back-link to host:
does host has link to /hooks sub-collection?
This feature works fine now , the link exists .
(In reply to comment #17)
> does host has link to /hooks sub-collection?
This bug is currently attached to errata RHEA-2013:14491. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.