Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 903520

Summary: Packages from Google Chrome do not promote to environment.
Product: Red Hat Satellite Reporter: Hayk Hovsepyan <hhovsepy>
Component: APIAssignee: Tomas Strachota <tstrachota>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: mmccune, tstrachota
Target Milestone: UnspecifiedKeywords: Reopened, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-16 13:31:44 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: 913012    
Bug Blocks:    
Attachments:
Description Flags
Patch for checking error states in package association api none

Description Hayk Hovsepyan 2013-01-24 08:43:56 UTC
Description of problem:
When promoting some package from Google Chrome repo to environment, it does not appear in that environment. This can be done by UI or by CLI.
Other repo packages like "pulp", "zoo" etc.. promote successfully.

Version-Release number of selected component (if applicable):
katello-glue-candlepin-1.3.3-1.git.40.a3fe82b.el6.noarch
katello-repos-1.3.2-1.el6.noarch
katello-selinux-1.3.1-1.el6.noarch
katello-agent-1.1.3-1.el6.noarch
katello-certs-tools-1.1.9-1.el6.noarch
katello-glue-pulp-1.3.3-1.git.40.a3fe82b.el6.noarch
katello-1.3.3-1.git.40.a3fe82b.el6.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-cli-1.3.3-1.git.23.e4c3fd5.el6.noarch
katello-configure-1.3.3-1.git.5.0f1d8f6.el6.noarch
katello-common-1.3.3-1.git.40.a3fe82b.el6.noarch
katello-glue-foreman-1.3.3-1.git.40.a3fe82b.el6.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-cli-common-1.3.3-1.git.23.e4c3fd5.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. Create provider, product, repo (Google Chrome: "http://dl.google.com/linux/chrome/rpm/stable/x86_64"). Do not sync repo.
2. Promote product to "dev" environment.
3. Sync the repo.
4. Promote one package from repo to environment (for example "google-chrome-stable").
5. You can see that package is not available in environment, by UI (Content Search) or by CLI ("package list").
  
Actual results:
Package is not promoted to environment.

Expected results:
It should be promoted.

Additional info:
But promoting whole Google Chrome product (when repo is synced) works.

Comment 1 Tomas Strachota 2013-02-13 09:05:52 UTC
Could not reproduce. The package google-chrome-stable promoted to the next environment without any problem.

Data used:
repo: http://dl.google.com/linux/chrome/rpm/stable/x86_64
key:  https://dl-ssl.google.com/linux/linux_signing_key.pub
package: google-chrome-stable

Comment 2 Tomas Strachota 2013-02-20 07:59:08 UTC
Reopening. I managed to reproduce the problem in CFSE.

Comment 4 Tomas Strachota 2013-02-20 09:12:09 UTC
Created attachment 699887 [details]
Patch for checking error states in package association api

The actual problem lies in Pulp. Yet we have to fix checking for error states on our side. Patch is attached.

Comment 5 Tomas Strachota 2013-02-20 09:15:51 UTC
Please note that the problem is fixed in Pulp v2 (and therefore in latest katello master).

Comment 6 Mike McCune 2013-02-27 16:19:33 UTC
This is fixed in Katello Master and Pulp V2, not going to resolve in CFSE 1.1.X

Comment 7 Hayk Hovsepyan 2013-05-16 13:31:44 UTC
As promoting individual package by changeset is removed from Katello, this bug is already not actual.