Bug 1194784 - Content View update - needs to be dynflow'ed
Summary: Content View update - needs to be dynflow'ed
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: Unspecified
Assignee: Brad Buckingham
QA Contact: jcallaha
URL: http://projects.theforeman.org/issues...
Depends On:
TreeView+ depends on / blocked
Reported: 2015-02-20 17:56 UTC by Brad Buckingham
Modified: 2017-02-23 20:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-08-12 05:26:54 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 9416 0 None None None 2016-04-22 16:13:39 UTC
Red Hat Product Errata RHSA-2015:1592 0 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 09:04:35 UTC

Description Brad Buckingham 2015-02-20 17:56:43 UTC
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.

Comment 1 Brad Buckingham 2015-02-20 17:56:45 UTC
Created from redmine issue http://projects.theforeman.org/issues/9416

Comment 3 jaudet 2015-02-20 21:45:45 UTC
> 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.

Comment 4 Brad Buckingham 2015-02-20 21:52:41 UTC
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.

Comment 8 jcallaha 2015-02-26 17:08:03 UTC
Verified in Satellite 6.1.0 snap 4 compose 2.

Version tested:

Comment 9 Bryan Kearney 2015-08-11 13:34:03 UTC
This bug is slated to be released with Satellite 6.1.

Comment 10 errata-xmlrpc 2015-08-12 05:26:54 UTC
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.


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