1255560 – assigning a repo to content-view using 'content-view update' option is not possible by --name

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1255560 - assigning a repo to content-view using 'content-view update' option is not possible by --name

Summary: assigning a repo to content-view using 'content-view update' option is not po...

Keywords:
Status:	CLOSED DUPLICATE of bug 1254977
Alias:	None
Product:	Red Hat Satellite
Classification:	Red Hat
Component:	Hammer
Sub Component:
Version:	6.1.0
Hardware:	All
OS:	Linux
Priority:	medium
Severity:	medium
Target Milestone:	Unspecified
Assignee:	Katello Bug Bin
QA Contact:	Katello QA List
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2015-08-21 00:17 UTC by Anand Vaddarapu
Modified:	2019-07-11 09:50 UTC (History)
CC List:	2 users (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2015-11-18 20:17:33 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Description Anand Vaddarapu 2015-08-21 00:17:46 UTC

Description of problem:

In satellite 6.1

-----------------------

 hammer content-view update --help
Usage:
    hammer content-view update [OPTIONS]

Options:
 --component-ids COMPONENT_IDS           List of component content view version ids for composite views
                                         Comma separated list of values.
 --description DESCRIPTION               Description for the content view
 --id ID                                 Content view identifier
 --name NAME                             Content view name
 --new-name NEW_NAME                     New name for the content view
 --organization ORGANIZATION_NAME        Organization name to search by
 --organization-id ORGANIZATION_ID       organization ID
 --organization-label ORGANIZATION_LABEL Organization label to search by
 --repositories REPOSITORY_NAMES         Comma separated list of values.   <----- repo_name 
 --repository-ids REPOSITORY_IDS         repository ID
                                         Comma separated list of values.
 -h, --help                              print help

1. Creating content view 'Foo'
hammer> content-view create --organization Brisbane --name Foo
Content view created

2. Checking repo list.
hammer> repository list --organization Brisbane
---|-------------------------------------------------------|---------------------------------|--------------|-----------------------------------------------------------------------
ID | NAME                                                  | PRODUCT                         | CONTENT TYPE | URL                                                                   
---|-------------------------------------------------------|---------------------------------|--------------|-----------------------------------------------------------------------
10 | JBoss Enterprise Application Platform                 | jboss channels                  | yum          |                                                                       
3  | motd-repo                                             | motd                            | puppet       | https://yum.puppetlabs.com/?_ga=1.37220005.488448745.1437627233       
2  | puppet-repo                                           | puppet                          | puppet       |                                                                       
4  | Red Hat Enterprise Linux 6 Server RPMs x86_64 6.6     | Red Hat Enterprise Linux Server | yum          | https://cdn.redhat.com/content/dist/rhel/server/6/6.6/x86_64/os       
8  | Red Hat Enterprise Linux 6 Server RPMs x86_64 6Server | Red Hat Enterprise Linux Server | yum          | https://cdn.redhat.com/content/dist/rhel/server/6/6Server/x86_64/os   
1  | Red Hat Virt V2V Tool for RHEL 7 RPMs x86_64 7.1      | Red Hat Enterprise Linux Server | yum          | https://cdn.redhat.com/content/dist/rhel/server/7/7.1/x86_64/v2vwin/os
---|-------------------------------------------------------|---------------------------------|--------------|-----------------------------------------------------------------------

3. Assign repo to the content-view by name
hammer> content-view add-repository --organization Brisbane --name Foo --repository "Red Hat Enterprise Linux 6 Server RPMs x86_64 6Server" 
The repository has been associated 

It works.

> content-view list --organization Brisbane
----------------|---------------------------|---------------------------|-----------|---------------
CONTENT VIEW ID | NAME                      | LABEL                     | COMPOSITE | REPOSITORY IDS
----------------|---------------------------|---------------------------|-----------|---------------
1               | Default Organization View | Default_Organization_View |           |               
5               | Foo                       | Foo                       |           | 8             
4               | RHEL Repo                 | RHEL_Repo                 |           | 4, 8          
3               | v2v                       | v2v                       |           | 1             
----------------|---------------------------|---------------------------|-----------|---------------

I don't think "content-view update" option works. This is more looks like a bug.

hammer> content-view update --organization Brisbane --name Foo --repositories "Red Hat Enterprise Linux 6 Server RPMs x86_64 6.6"
Could not update the content view:
  Error: Could not find repository, please set one of options --repositories, --repository-ids.

hammer> content-view update --organization Brisbane --name Foo --repositories "Red Hat Virt V2V Tool for RHEL 7 RPMs x86_64 7.1"
Could not update the content view:
  Error: Could not find repository, please set one of options --repositories, --repository-ids.

Version-Release number of selected component (if applicable):


Actual results:
Could not update the content view:
  Error: Could not find repository, please set one of options --repositories, --repository-ids.

Expected results:
The repository has been associated

Additional info:

Comment 1 Brad Buckingham 2015-11-18 20:17:33 UTC

This issue was also raised as part of bug 1254977.  That bug was created in the context of 'content-view create'; however, 1254977#4 also raised the issue with 'content-view update'.  In order to ensure that both issues are fixed at the same time, I am going to close this one as a duplicate.

*** This bug has been marked as a duplicate of bug 1254977 ***

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