Description of problem: hammer-cli-import creates Products for matching Sat5 channels and config-channels. When we do so, the new products no longer show up in the list at /products for a (or any) selected Organization. Version-Release number of selected component (if applicable): 6.0.4 Snap6 How reproducible: Create a Product using 'hammer product create' (or any other API-creation-method, like 'hammer import repository' or 'hammer import config-file') Steps to Reproduce: 1. hammer> product create --name "hammer-created-product" --label "hammer-created-product" --organization <org-on-your-system> 2. https://<your-sat6-machine/products 3. Choose <org-on-your-system> Actual results: "hammer-created-product" does not appear in the list Expected results: It does appear in the list Additional info: This worked until today - I just updated my Sat6 system to latest-code. Task-list shows create succeeded: {"product"=> {"id"=>194, "name"=>"hammer-created-product", "label"=>"hammer-created-product", "cp_id"=>nil}, "provider"=>{"id"=>5, "name"=>"Anonymous"}, "organization"=>{"id"=>4, "name"=>"SOE-ORG", "label"=>"SOE-ORG"}, "cp_id"=>"1408130082631", "locale"=>"en"} Going to the created-id in the UI, works https://beast-sat6.usersys.redhat.com/products/194/info
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
This is a blocker for the transition-tooling - it menas you never see the newly-created products for Sat5 custom/cloned channels or config-channels.
Additional weirdness, ending in success: * katello-service stop; katello-service start => *NO* products showing in list anywhere * curl http://localhost:9200/_cluster/health?pretty=true => "status" : "red" * Issued the following: === # service elasticsearch stop # rm -rf /var/lib/elasticsearch/elasticsearch/nodes/* # service elasticsearch start # foreman-rake katello:reindex === 'products' page is happy again. Having a workaround removes this as a blocker for transition - but, ow.
One last debugging-note: Prior to this weirdness, I did # katello-installer --foreman-admin-username admin --foreman-admin-password changeme --reset" on the machine. NOTE: usually I only do a --reset after a katello-service stop. Looking at my command-history, in this instance --reset was issued with Sat6 still running. No idea if that has anything to do with the results, just offering it as a datapoint.
We're pretty sure this was caused by https://bugzilla.redhat.com/show_bug.cgi?id=1131524 Closing as a dup for now *** This bug has been marked as a duplicate of bug 1131524 ***