Bug 1202798

Summary: Request updated dynflow & foreman-tasks
Product: Red Hat Satellite Reporter: Brad Buckingham <bbuckingham>
Component: OtherAssignee: Ivan Necas <inecas>
Status: CLOSED CURRENTRELEASE QA Contact: jcallaha
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: bkearney, cwelton, jmatthew, jmontleo, mmccune
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/9508
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 13:57:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1212602    

Description Brad Buckingham 2015-03-17 13:10:14 UTC
Description of problem:

There have been some changes made in foreman-tasks and dynflow to support RHCI.  Since the initial release of RHCI will be on Satellite 6.1, we'd like to get the updated rpms in to the Satellite 6.1 compose.  This BZ is to request those updated packages.

The change needed in the above is to support sub-plan actions that contain existing Satellite actions.  For example, RHCI might perform a 'deploy' that syncs repositories.  We want the sync status of those repositories to be visible throughout the UI, regardless of whether they were initiated by Satellite or RHCI.  The above changes will enable that.

The packages needed are:
 foreman-tasks 0.6.13 and dynflow 0.7.7

Referenced PRs:
https://github.com/theforeman/foreman-tasks/pull/104
https://github.com/Dynflow/dynflow/pull/145
https://github.com/theforeman/foreman-packaging/pull/582

Comment 3 Mike McCune 2015-04-28 15:28:00 UTC
*** Bug 1209598 has been marked as a duplicate of this bug. ***

Comment 4 Mike McCune 2015-04-28 22:59:13 UTC
This hasn't been tested upstream yet so I don't want to blindly include it in the 6.1 GA build.

Ivan:

Can you get this built in koji and available in a Katello nightly build so we can have some confidence these changes won't break anything?

Comment 5 Mike McCune 2015-04-28 23:03:06 UTC
Oops, scratch the above, I see them:

http://koji.katello.org/koji/buildinfo?buildID=21030
http://koji.katello.org/koji/buildinfo?buildID=21031

I tried installing to see how far I would get if I built these downstream but hit:

# rpm -Uvh http://koji.katello.org/packages/ruby193-rubygem-foreman-tasks/0.6.13/2.el6/noarch/ruby193-rubygem-foreman-tasks-0.6.13-2.el6.noarch.rpm http://koji.katello.org/packages/ruby193-rubygem-dynflow/0.7.7/1.el6/noarch/ruby193-rubygem-dynflow-0.7.7-1.el6.noarch.rpm
Retrieving http://koji.katello.org/packages/ruby193-rubygem-foreman-tasks/0.6.13/2.el6/noarch/ruby193-rubygem-foreman-tasks-0.6.13-2.el6.noarch.rpm
Retrieving http://koji.katello.org/packages/ruby193-rubygem-dynflow/0.7.7/1.el6/noarch/ruby193-rubygem-dynflow-0.7.7-1.el6.noarch.rpm
error: Failed dependencies:
	foreman >= 1.8.0 is needed by ruby193-rubygem-foreman-tasks-0.6.13-2.el6.noarch

is there something in foreman-tasks-0.6.13 that has a hard requirement on foreman-1.8.0?

I don't want to rebase if there are changes that require things in 1.8 that we don't have.

Comment 6 Ivan Necas 2015-04-29 06:48:39 UTC
The only thing that changed that requires foreman 1.8 is the spec file and the way how the apipie docs are generated:

https://github.com/theforeman/foreman-packaging/commit/041fec38f6012ce55e3bc90cc9f4ed65fdce9f4b

This was introduced in the very last release (0.6.13-2), but the previous one (0.6.13-1) should be ok
https://github.com/theforeman/foreman-packaging/commit/38a57e2a2eb8c1276c527371ae31eb28a9183641

Comment 7 Bryan Kearney 2015-04-30 20:05:23 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/9508 has been closed
-------------
Ivan Necas
Applied in changeset commit:131f05b6fcc027d071cc4ad71610827f7dff9161.

Comment 10 jcallaha 2015-05-13 17:55:05 UTC
Verified in Satellite 6.1 Snap 3.

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

Comment 12 Bryan Kearney 2015-08-12 13:57:24 UTC
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.