Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR:katprep_snapshot:Unable to get system information with physical hosts running puppet 5.5.0 #114

Open
brotaxt opened this issue Jan 16, 2019 · 6 comments

Comments

@brotaxt
Copy link

brotaxt commented Jan 16, 2019

Describe the bug

When I start katprep_snapshot -o $ORGANIZATIONID I receive the following error message when katprep_snapshot checking a physical system.

ERROR:katprep_snapshot:Unable to get system information for '$HOSTNAME' , dropping system!

This seems only to happen, if the physical host is running puppet agent 5.5.0.

When I run katprep_snapshot and the physical host has puppet agent 3.8.6 installed, everyhting works as expected.

The issue might be correlate with the revised facts in puppet 5.5

To Reproduce
Steps to reproduce the behavior:

katprep_snapshot -o $ORGANIZATIONID on physical host running puppet agent 5.5.0

Expected behavior

katprep_snapshot should not dropping the system from report.

Environment (please complete the following information):

  • OS version: RHEL 7.6
  • Red Hat Satellite 6.4.1
  • Puppet 5.5.0
@stdevel stdevel self-assigned this Jan 17, 2019
@stdevel stdevel added the bug label Jan 17, 2019
@stdevel
Copy link
Owner

stdevel commented Jan 17, 2019

Hey @brotaxt,
thanks for reproducing this against other Puppet versions - really sounds like a facts related issue. Could you share the output of the following API call, please?

https://SATELLITE/api/v2/hosts/$PHYSICAL_HOST_RUNNING_PUPPET_V5

You can access the URL from your web browser or an API client such as postman.

@brotaxt
Copy link
Author

brotaxt commented Jan 17, 2019

Hey @stdevel,
thanks for the fast response. Unfortunately I can't share the output of the given command, because there are too many confidential information included. I can try to exclude the confidential stuff when you tell me which part of the output is needed.

@stdevel
Copy link
Owner

stdevel commented Jan 18, 2019

Hi @brotaxt,
no problem. I'm specially interested in the keys content_facet_attributes and facts. You can also share the censored output in private with me via mail, if you want to. Not going to publish it somewhere else. Hope this helps!

@brotaxt
Copy link
Author

brotaxt commented Jan 22, 2019

Hi @stdevel,

below please find a part of the requested keys.
If you need a bigger part of the code I must first censor more lines of it.

"content_facet_attributes":{"id":1,"uuid":"$UUID","content_view_id":1,"content_view_name":"Default Organization View","lifecycle_environment_id":1,"lifecycle_environment_name":"Library","content_source_id":null,"content_source_name":null,"kickstart_repository_id":null,"kickstart_repository_name":null,"errata_counts":{"security":0,"bugfix":0,"enhancement":0,"total":0},"applicable_package_count":0,"upgradable_package_count":0,"content_view":{"id":1,"name":"Default Organization View"},"lifecycle_environment":{"id":1,"name":"Library"},"content_source":null,"kickstart_repository":null,"content_view_version":"1.0","content_view_version_id":1,"content_view_default?":true,"lifecycle_environment_library?":true,"katello_agent_installed":true},"subscription_global_status":0,"subscription_facet_attributes":{"id":1,"uuid":"$UUID","last_checkin":"2019-01-22 13:32:46 +0100","service_level":null,"release_version":null,"autoheal":true,"registered_at":"2017-03-20 11:54:23 +0100","registered_through":"$SATELLITE","user":null,"virtual_host":null,"virtual_guests":[],"installed_products":[{"productName":"Red Hat Enterprise Linux Server","productId":"","arch":"x86_64","version":"7.6"}],"activation_keys":[{"id":1,"name":"$ACTIVATIONKEYNAME"}],"compliance_reasons":[]},"host_collections":[{"id":1,"name":"$HOST_COLLECTIONS_NAME"}]
"facts":{"virt::host_type":"Not Applicable","lscpu::l1i_cache":"32K","dmi::slot::type:slotbuswidth":"x16","dmi::baseboard::version":"","dmi::memory::error_correction_type":"Multi-bit ECC","dmi::processor::type":"Central Processor","dmi::chassis::thermal_state":"Safe"

@brotaxt
Copy link
Author

brotaxt commented Feb 21, 2019

Hey @stdevel,

do you have any news on this issue?

Best regards

@stdevel
Copy link
Owner

stdevel commented Feb 25, 2019

Hello @brotaxt,
thanks for your feedback!
Sorry for the delay - there is no progress at this time. Currently stuck with other things. 😞

Best wishes,
Christian.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants