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.
DescriptionGarik Khachikyan
2011-10-31 13:07:51 UTC
Description of problem:
Recently now the scenario of having product content promoting to 2 different environments of the org having Locker as their "prior" fails with a JDBC error on Candlepin side:
Version-Release number of selected component (if applicable):
katello-0.1.96-1.git.133.5a44f75.el6.x86_64
How reproducible:
always
Steps to Reproduce:
org create --name org1
provider create --name provider1 --type custom --org org1
product create --name product1 --provider provider1 --org org1
repo create --org org1 --product product1 --name pulpF15-x86_64 --url http://repos.fedorapeople.org/repos/pulp/pulp/fedora-15/x86_64/
repo synchronize --name pulpF15-x86_64 --org org1 --product product1
environment create --name dev --org org1 --prior Locker
environment create --name live --org org1 --prior Locker
changeset create --org org1 --environment dev --name cs1
product promote --environment live --org org1 --name product1
repo list --environment live --environment live --org org1 # assure repo is promoted
repo list --environment live --environment dev --org org1 # and the other env - still nothing...
changeset update --add_product product1 --name cs1 --org org1 --environment dev
changeset promote --environment dev --name cs1 --org org1
Actual results:
Fails on JDBC error on Candlepin side:
Expected results:
no errors - possible to promote the product (and repos actually) to the different environments.
Additional info:
output of the error:
---
Changeset [ cs1 ] promotion failed: Candlepin::Content: 500 Internal Server Error {"displayMessage":"Runtime Error Could not execute JDBC batch update at org.postgresql.jdbc2.AbstractJdbc2Statement$BatchResultHandler.handleError:2,598"} (POST /candlepin/content/)
---
Logs of candlepin are attached (see below)
commit 3c76efd884edae7942d247d4b311a6f845f40a74
Author: Tomas Strachota <tstrachota>
Date: Tue Nov 1 16:44:19 2011 +0100
750246 - promote content of product to different environments
# VERIFIED
fixed. The scenario in comment#0 now works smoothly (no errors - repos promoted to both env-s).
packages:
katello-cli-0.1.11-1.git.0.facb3bb.el6.noarch
katello-0.1.101-1.git.30.d57dd1d.el6.x86_64