Project

General

Profile

Actions

Bug #4948

closed

Syncing a product results in Content Search not showing packages

Added by Bryan Kearney about 10 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
-
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

On a clean install, I created a product a single repo and then I synced it down. The task shows complete and it shows 8 packages which is also correct. When I click on the '8 Packages' from the product page it takes me to content search. I can not see the packages reflected there.

Actions #1

Updated by Bryan Kearney about 10 years ago

  • Priority changed from Normal to High
Actions #2

Updated by Bryan Kearney about 10 years ago

If I go to the content search, and select Content = Packages and then search, I see this in the logs;

#
# {
# "error":"IndexMissingException[[katello_package] missing]",
# "status":404
# }
dev setup +
[bkearney@bkearney hammer-cli]$ for i in `rpm -qa | grep -iE "^rubygem-hammer|^katello|^pulp|^candlepin|^foreman|^headpin|^thumbslug|^elasticsearch|ldap|signo|ruby193-rubygem-runcible" | sort`; do echo "* $i"; done
  • candlepin-0.8.29.3-1.fc19.noarch
  • elasticsearch-0.90.10-4.fc19.noarch
  • katello-certs-tools-1.4.4-1.fc19.noarch
  • katello-configure-1.4.9-1.fc19.noarch
  • katello-repos-1.4.4-1.fc19.noarch
  • ldapjdk-4.18-14.fc20.noarch
  • openldap-2.4.39-2.fc20.x86_64
  • pulp-admin-client-2.3.1-1.fc19.noarch
  • pulp-katello-plugins-0.2-1.fc19.noarch
  • pulp-nodes-common-2.3.1-1.fc19.noarch
  • pulp-nodes-parent-2.3.1-1.fc19.noarch
  • pulp-puppet-plugins-2.3.1-1.fc19.noarch
  • pulp-rpm-admin-extensions-2.3.1-1.fc19.noarch
  • pulp-rpm-plugins-2.3.1-1.fc19.noarch
  • pulp-rpm-yumplugins-2.3.1-1.fc19.noarch
  • pulp-server-2.3.1-1.fc19.noarch
  • python-ldap-2.4.6-5.fc20.x86_64
  • rubygem-ldap_fluff-0.2.2-2.fc19.noarch
  • rubygem-net-ldap-0.3.1-5.fc20.noarch
  • sssd-ldap-1.11.4-1.fc20.x86_64
Actions #3

Updated by Bryan Kearney about 10 years ago

  • Status changed from New to Closed

Not seeing this on the production install, so I am closing this out. Must be my dev instance some how.

Actions #4

Updated by Eric Helms almost 10 years ago

  • Triaged changed from No to Yes
Actions #5

Updated by Eric Helms over 9 years ago

  • translation missing: en.field_release set to 13
Actions

Also available in: Atom PDF