Bug 913012

Description of problem:

Associating a package from google chrome repo via api fails.
If a repository is first cloned and then synced it's not possible to associate a package with the clone (post call to /api/services/associate/packages/) Adding the package one by one using pulp-admin works ok.


Version-Release number of selected component (if applicable):
pulp-1.1.15-1.el6cf.noarch


How reproducible:
always


Steps to Reproduce:
wget https://dl-ssl.google.com/linux/linux_signing_key.pub -O /tmp/google_key.pub
pulp-admin repo create --id chrome1 --feed 'http://dl.google.com/linux/chrome/rpm/stable/x86_64' --gpgkeys '/tmp/google_key.pub'
pulp-admin repo clone --id chrome1 --clone_id chrome2
pulp-admin repo sync --id chrome1

# the package google-chrome-stable is listed for repo chrome1
pulp-admin package search

# let's use the api to assign it to the cloned repo chrome2
curl -H "Content-Type: application/json" -H "Accept: application/json" -X POST -d '{"package_info":[[["google-chrome-stable-24.0.1312.70-181759.x86_64.rpm","c983a6ee19b032b13328c1d98d931103b83e79ba"],["chrome2"]]]}' -k -u $PULP_USER:$PULP_PASSWD https://localhost:443/pulp/api/services/associate/packages/


Actual results:
The server responds with
{"google-chrome-stable-24.0.1312.70-181759.x86_64.rpm": {"c983a6ee19b032b13328c1d98d931103b83e79ba": [["chrome2"]]}}
which means the package was not associated.


Expected results:
The server should associate the package and return {}


Additional info:
/var/log/pulp/log says:
2013-02-20 10:11:15,588 22497:140608989538048: pulp.server.api.repo:ERROR: repo:2192 Unable to find package id for filename=google-chrome-stable-24.0.1312.70-181759.x86_64.rpm, checksum=c983a6ee19b032b13328c1d98d931103b83e79ba
2013-02-20 10:11:15,589 22497:140608989538048: pulp.server.api.repo:INFO: repo:2208 Translated 1 filename,checksums in 0.0115659236908 seconds