Bug 1390545 – [RFE] hammer sync-plan info should show associated products

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1390545 - [RFE] hammer sync-plan info should show associated products

Summary:	[RFE] hammer sync-plan info should show associated products

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Satellite 6
Classification:	Red Hat
Component:	Sync Plans (Show other bugs)
Sub Component:
Version:	6.2.3
Hardware:	Unspecified Unspecified

Priority	medium Severity high (vote)
Target Milestone:	GA
Target Release:	Unused
Assigned To:	Chris Roberts
QA Contact:	Peter Ondrejka
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature, Triaged

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-11-01 07:11 EDT by daniel
Modified:	2018-08-31 11 EDT (History)
CC List:	11 users (show)

See Also:
Fixed In Version:	rubygem-hammer_cli_katello-0.11.3.3
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-02-21 07:36:49 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Foreman Issue Tracker	17155	None	None	None	2016-11-01 07:13 EDT
Red Hat Product Errata	RHSA-2018:0336	normal	SHIPPED_LIVE	Important: Satellite 6.3 security, bug fix, and enhancement update	2018-02-21 17:43:42 EST

Groups: None (edit)

Description daniel 2016-11-01 07:11:05 EDT

Description of problem:
When creating sync plans via hammer one cannot see which products are associated with the sync plan

Version-Release number of selected component (if applicable): current 
tfm-rubygem-hammer_cli-0.5.1.11-4.el7sat.noarch
tfm-rubygem-hammer_cli_foreman-0.5.1.9-1.el7sat.noarch

How reproducible:
create sync plan and associate multiple products. When running `hammer sync-plan info --<id|name> <number|name>` one cannot see which products are assigned to that sync plan


Steps to Reproduce:
1. create Sync plan, e.g.:
hammer sync-plan create --name 'SyncPlan Capsule' --enabled=true --interval daily --sync-date "2016-11-01 20:00:00"

2. attach products
  # hammer product set-sync-plan --name 'Red Hat Enterprise Linux Server' --sync-plan 'SyncPlan Capsule'
  # hammer product set-sync-plan --name 'Red Hat Software Collections for RHEL Server' --sync-plan 'SyncPlan Capsule'
  # hammer product set-sync-plan --name 'Red Hat Satellite Capsule' --sync-plan 'SyncPlan Capsule'

3. display info about sync plan
# hammer sync-plan info --name 'SyncPlan Capsule'
ID:          1
Name:        SyncPlan Capsule
Start Date:  2016/11/01 20:00:00
Interval:    daily
Enabled:     yes
Description: 
Created at:  2016/11/01 10:51:11
Updated at:  2016/11/01 10:51:11



Actual results:
associated products are not displayed

Expected results:
display associated products

Additional info:

Comment 2 Bryan Kearney 2016-11-01 08:17:52 EDT

Upstream bug component is Remote Execution

Comment 3 pm-sat@redhat.com 2017-02-01 14:18:11 EST

Upstream bug assigned to chrobert@redhat.com

Comment 7 Peter Ondrejka 2017-11-15 13:18:59 EST

Looking at Satellite 6.3 snap 24, product info still not around:

]# hammer sync-plan info --id 1
ID:          1
Name:        custom
Start Date:  2017/11/15 17:30:00
Interval:    daily
Enabled:     yes
Description: 
Created at:  2017/11/15 17:30:13
Updated at:  2017/11/15 17:30:13

Comment 8 Peter Ondrejka 2017-11-27 05:17:39 EST

Verified on Sat 6.3 snap 26:

~]# hammer sync-plan info --id 1
ID:          1
Name:        syn
Start Date:  2017/11/27 10:15:00
Interval:    weekly
Enabled:     yes
Description: 
Created at:  2017/11/27 10:15:12
Updated at:  2017/11/27 10:15:12
Products:    
 1) ID:   15
    Name: Red Hat Enterprise Linux Server

Comment 12 errata-xmlrpc 2018-02-21 07:36:49 EST

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-2018:0336

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