Bug 750246

Summary: promote content of product to different environments (prior-ed from same Locker)
Product: Red Hat Satellite Reporter: Garik Khachikyan <gkhachik>
Component: APIAssignee: Tomas Strachota <tstrachota>
Status: CLOSED CURRENTRELEASE QA Contact: Garik Khachikyan <gkhachik>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0.0CC: hhovsepy, mkoci, tstrachota
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: katello-0.1.97-1.git.126.6dec5c9 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-22 18:03:52 UTC Type: ---
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:    
Bug Blocks: 747354    
Attachments:
Description Flags
tomcat6 logs. none

Description Garik 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:
Comment 1 Garik Khachikyan 2011-10-31 13:08:35 UTC 
put QE flag for automation.
Comment 2 Garik Khachikyan 2011-10-31 13:33:15 UTC 
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)
Comment 3 Garik Khachikyan 2011-10-31 13:34:46 UTC 
Created attachment 530974 [details]
tomcat6 logs.
Comment 4 Tomas Strachota 2011-11-02 08:52:55 UTC 
commit 3c76efd884edae7942d247d4b311a6f845f40a74
Author: Tomas Strachota <tstrachota>
Date:   Tue Nov 1 16:44:19 2011 +0100

    750246 - promote content of product to different environments
Comment 5 Garik Khachikyan 2011-11-14 09:51:02 UTC 
# 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
Comment 8 Hayk Hovsepyan 2012-12-05 11:37:45 UTC 
Automated in method: "com.redhat.qe.katello.tests.e2e.PromoteProductToDifferentEnvs.test_promoteProduct()".