| Summary: | Hypervisor checkin failed with not-null property error | |||
|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Chris Roberts <chrobert> | |
| Component: | Candlepin | Assignee: | satellite6-bugs <satellite6-bugs> | |
| Status: | CLOSED ERRATA | QA Contact: | Katello QA List <katello-qa-list> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 6.1.7 | CC: | ahuchcha, bcourt, chrobert, ehelms, kbidarka, mmccune, sthirugn | |
| Target Milestone: | Unspecified | Keywords: | Reopened | |
| Target Release: | Unused | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | candlepin-0.9.54-5 | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1320316 (view as bug list) | Environment: | ||
| Last Closed: | 2016-07-27 11:02:47 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Bug Depends On: | 1311664 | |||
| Bug Blocks: | 1320316 | |||
|
Description
Chris Roberts
2016-03-08 22:43:06 UTC
what exactly we mean by "hypervisor checking failed", does it mean when 'RHEVM/RHEV's being registered to satellite6' as hypervisor with virt-who configured ? Can you please provide more detailed steps to reproduce this bug? This has been backported to the 0.9.54 hotfix branch Kedar, *** This bug has been marked as a duplicate of bug 1311664 *** we still need a Satellite 6 product bug if we are to ship this in a Satellite release. Kedar, I was seeing mostly on VMWARE. On the virt-who machine you would see an Internal server error and on the satellite you would see the following: ERROR org.candlepin.resource.HypervisorResource - Hypervisor checkin failed org.hibernate.PropertyValueException: not-null property references a null or transient value: org.candlepin.model.GuestId.guestId Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1501 |