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: