Red Hat Bugzilla – Bug 1194784
Content View update - needs to be dynflow'ed
Last modified: 2017-02-23 15:27:36 EST
In certain scenarios, performing a content view update will initiate a reindex of association objects (e.g. repositories) during an update. As a result, this action should be dynflow'ed as has been done for similar update actions on other objects.
Created from redmine issue http://projects.theforeman.org/issues/9416
> In certain scenarios, performing a content view update will initiate a reindex of association objects What are these "certain scenarios" that will cause a dynflow task to kick off? Will a dynflow task kick off when: * An update of any kind is made to any content view? * An update of any kind is made to a content view that is associated with one or more repositories? * An update to any field other than "name" is made to any content view? * Something else? Without knowing this, I can only guess as to which actions should kick off a dynflow action, and my guess is likely to be wrong. I did try experimenting manually, but I could not trigger any dynflow tasks. I created a content view and associated it with two repositories, one with a content type of yum and another with a content type of docker. I then updated that content view's name and description, one after the other. Neither update caused a dynflow task to be created.
With this change a dynflow task will be initiated any time a content view update is performed (e.g. PUT /content_view/:id). This includes changes to things like name, description, repositories...etc. Similar to other 'update' requests that have been dynflow'ed the API call will be blocked until the update is completed (vs returning a 202 with a task). Also, I don't think you will see the change in behavior yet. It was just merged upstream today; therefore, it is not yet in nightly or a downstream compose.
Verified in Satellite 6.1.0 snap 4 compose 2. Version tested: RHEL 66 RHEL 71
This bug is slated to be released with Satellite 6.1.
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. https://access.redhat.com/errata/RHSA-2015:1592