Bug #10565
closed
After registering content host, it is not listed / Bug #6171
Added by Claudiu Nagy over 9 years ago.
Updated over 6 years ago.
Description
I am hitting the exact description of BUG #6171
OS: redhat
RELEASE: CentOS Linux release 7.1.1503 (Core)
FOREMAN: 1.8.1
RUBY: ruby 2.0.0p598 (2014-11-13) [x86_64-linux]
PUPPET: 3.7.5
DENIALS: 0
After subscribing host to katello 2.2 it is not shown in content host list, nor with hammer cli.
Steps to Reproduce:
1. register host by standard means i.e.: subscription-manager register --force --org="ACME_Corporation" --environment="Library"
2. observe "The system has been registered with id:$HOST-ID" message
3. try hammer content-host info --id=$HOST-ID and observe, that host was registered
4. try hammer content-host list --organization-label='ACME_Corporation'
5. try list content hosts for ACME_Corporation in ui
Actual results:
No data.
Expected results:
At least the registered host should have been listed
- Tracker changed from Support to Bug
- Project changed from Foreman to Katello
- Category deleted (
API)
- Triaged set to No
- Status changed from New to Need more information
- Translation missing: en.field_release set to 55
- Triaged changed from No to Yes
You see the content host listed from hammer but not the Web UI? Do you see errors in production.log? Does the Content Host sit and spin or just show no results?
The missing hosts don't show up in the web gui or hammer. The webpage is loading fine and shows some systems and not others. Same with hammer. There are no errors reported in the logs.
If in hammer i try to get the information of the missing systems by explicitly providing the uuid then it works. I have also looked into mongodb and postgresql databases and i can see the systems are there.
Are the missing hosts different in anyway than the hosts that are showing up? Hypervisors? or configuration? or the base OS? Trying to see if there is a common thread.
The missing hosts are identical with others that work.
Can you try running `rake katello:reindex' as this sounds like the registered systems are not in Elasticsearch.
I have run the command "foreman-rake katello:reindex", but the problem is still there.
=========
- foreman-rake katello:reindex
Elasticsearch Indices cleared.
Re-indexing Katello::TaskStatus
Re-indexing Katello::ContentViewFilter
Re-indexing Katello::Product
Re-indexing Katello::Repository
Re-indexing Katello::ContentView
Re-indexing Katello::ContentViewPuppetEnvironment
Re-indexing Katello::ContentViewPuppetModule
Re-indexing Katello::HostCollection
Re-indexing Katello::ContentViewHistory
Re-indexing Katello::Job
Re-indexing Katello::ContentViewPackageFilterRule
Re-indexing Katello::System
Re-indexing Katello::ContentViewPackageGroupFilterRule
Re-indexing Katello::Notice
Re-indexing Katello::ContentViewErratumFilterRule
Re-indexing Katello::ActivationKey
Re-indexing Katello::Provider
Re-indexing Katello::Distributor
Re-indexing Katello::PulpTaskStatus
Re-indexing Katello::PulpSyncStatus
Re-indexing Katello::ContentViewPackageGroupFilter
Re-indexing Katello::ContentViewErratumFilter
Re-indexing Katello::ContentViewPackageFilter
Re-indexing Katello::MarketingProduct
Re-indexing Katello::Hypervisor
Re-indexing Katello::Package
Re-indexing Katello::PuppetModule
Re-indexing Katello::Distribution
Re-indexing Katello::PackageGroup
Re-indexing Pools
=====
In the Re-indexing list i don't see any Katello::ContetHosts or something similar. Is it posible that this job is not re-indexing the content hosts?
Below are a few more things that i have noticed:
1) only 2 content hosts have the problem at this time, and hosts that have been registered since then are working as expected
2) I was able to add the 2 content hosts to a Host Collection (with hammer cli) and that Host collection shows a count of 6 Content Hosts but when i list them i only see 4 of them.
Something happened with this 2 hosts that prevents them from being listed in katello related queries (webpage, API or CLI).
- Translation missing: en.field_release changed from 55 to 61
- Translation missing: en.field_release changed from 61 to 31
- Translation missing: en.field_release changed from 31 to 70
- Translation missing: en.field_release changed from 70 to 86
- Status changed from Need more information to Resolved
Elasticsearch has been removed and content hosts have been reworked for better integration with Host objects. Please re-open if you still see this on 3.0
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by