Bug 1028104 - When promoting content views a Distribution Unpublished Error occurs
Summary: When promoting content views a Distribution Unpublished Error occurs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: Nightly
Hardware: x86_64
OS: Linux
unspecified
low vote
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: sthirugn@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-07 16:37 UTC by Roy Williams
Modified: 2019-09-26 18:18 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-11 12:23:37 UTC
Target Upstream Version:


Attachments (Terms of Use)
Contains Debug Logs (2.26 MB, application/gzip)
2013-11-07 16:37 UTC, Roy Williams
no flags Details

Description Roy Williams 2013-11-07 16:37:03 UTC
Description of problem:
Promoting a content view with several repositories results in a Distribution Unpublished error.

Version-Release number of selected component (if applicable):
1.5.1-1.git.6.65c0073.el6

How reproducible:
Everytime a promotion occurs with the repositories.

Steps to Reproduce:
1. Create several yum repositories within a product, in this case:
 Adobe Linux x86_64, http://linuxdownload.adobe.com/linux/x86_64/
 Katello, http://fedorapeople.org/groups/katello/releases/yum/1.4/Fedora/19/x86_64
 OpenAFS 1.6.5.1, http://www.openafs.org/dl/openafs/1.6.5.1/fedora-19/x86_64/
 x86_64, http://dl.fedoraproject.org/pub/fedora/linux/releases/19/Fedora/x86_64/os/
2. Create Content View With Repositories Inside.
2. Promote the from Library to an environment.
3. Error should occur.

Actual results:
Repositories should be promoted without issue.

Expected results:
Presents the error below:
Failed to perform additional action KatelloForemanEngine::Actions::DistributionUnpublish: 422 Unprocessable Entity 



Additional info:

Comment 1 Roy Williams 2013-11-07 16:37:41 UTC
Created attachment 821250 [details]
Contains Debug Logs

Comment 2 Partha Aji 2013-11-08 21:33:58 UTC
More info on this
1) A content view was published with repos listed in comment 1 and then promoted. 
2) 2 hosts consumed a specific media (Mosaic/Development/Desktop Fedora Fedora 19 x86_64 ) in this content view
3) Then the repo containing the installation media was removed from the content view's repo list and then the content was refreshed.

4) Now when the content view is repromoted, katello tries to removes the distribution from foreman, causing an error along the lines of

Started DELETE "/foreman/api/media/14" for 127.0.0.1 at 2013-11-07 11:14:42 -0500
Processing by Api::V1::MediaController#destroy as JSON
  Parameters: {"id"=>"14", "medium"=>{}}
Authorized user admin(Admin User)
You may not destroy Mosaic/Development/Desktop Fedora Fedora 19 x86_64 as it is in use!
Unprocessable entity Medium (id: 14):
  Mosaic/Development/Desktop Fedora Fedora 19 x86_64 is used by Host X
  Mosaic/Development/Desktop Fedora Fedora 19 x86_64 is used by Host Y

Comment 3 Partha Aji 2013-11-08 22:45:13 UTC
The work around for this bug is that 
1) Goto <fqdn>/foreman/hosts 
2) Select offending host
3) Select "operating systems"
4) Change the media to something other than "Development/Desktop Fedora Fedora 19 x86_64 "

Same behaviour for hostgroups also.

Comment 4 Bryan Kearney 2014-01-21 19:07:43 UTC
Moving to Sat6 to be tracked there. Upstream bugs are moving to redmine.

Comment 5 RHEL Program Management 2014-01-21 19:18:39 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 8 Brad Buckingham 2014-06-25 21:11:32 UTC
This issue may be solved by the recent work to eliminate the creation of installation media as part of the content view publish/promotion process.  Instead, the provisioning system will identify the installation media based upon the 'capsule' that is associated with the hostgroup/host.

Assigning this over to Justin to confirm.

Comment 9 Justin Sherrill 2014-06-25 21:25:35 UTC
Yes, this should be resolved, moving to on_qa

Comment 10 sthirugn@redhat.com 2014-09-04 18:42:51 UTC
Verified.

Version Tested:
GA Snap 7 - Satellite-6.0.4-RHEL-6-20140829.0

* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.9.23-1.el6_5.noarch
* candlepin-common-1.0.1-1.el6_5.noarch
* candlepin-scl-1-5.el6_4.noarch
* candlepin-scl-quartz-2.1.5-5.el6_4.noarch
* candlepin-scl-rhino-1.7R3-1.el6_4.noarch
* candlepin-scl-runtime-1-5.el6_4.noarch
* candlepin-selinux-0.9.23-1.el6_5.noarch
* candlepin-tomcat6-0.9.23-1.el6_5.noarch
* elasticsearch-0.90.10-6.el6sat.noarch
* foreman-1.6.0.42-1.el6sat.noarch
* foreman-compute-1.6.0.42-1.el6sat.noarch
* foreman-gce-1.6.0.42-1.el6sat.noarch
* foreman-libvirt-1.6.0.42-1.el6sat.noarch
* foreman-ovirt-1.6.0.42-1.el6sat.noarch
* foreman-postgresql-1.6.0.42-1.el6sat.noarch
* foreman-proxy-1.6.0.30-1.el6sat.noarch
* foreman-selinux-1.6.0.14-1.el6sat.noarch
* foreman-vmware-1.6.0.42-1.el6sat.noarch
* katello-1.5.0-30.el6sat.noarch
* katello-ca-1.0-1.noarch
* katello-certs-tools-1.5.6-1.el6sat.noarch
* katello-installer-0.0.62-1.el6sat.noarch
* openldap-2.4.23-34.el6_5.1.x86_64
* openldap-devel-2.4.23-34.el6_5.1.x86_64
* pulp-katello-0.3-4.el6sat.noarch
* pulp-nodes-common-2.4.1-0.5.rc1.el6sat.noarch
* pulp-nodes-parent-2.4.1-0.5.rc1.el6sat.noarch
* pulp-puppet-plugins-2.4.1-0.5.rc1.el6sat.noarch
* pulp-puppet-tools-2.4.1-0.5.rc1.el6sat.noarch
* pulp-rpm-plugins-2.4.1-0.5.rc1.el6sat.noarch
* pulp-selinux-2.4.1-0.5.rc1.el6sat.noarch
* pulp-server-2.4.1-0.5.rc1.el6sat.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch
* ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch

Comment 11 Bryan Kearney 2014-09-11 12:23:37 UTC
This was delivered with Satellite 6.0 which was released on 10 September 2014.


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