Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1315897 - Hypervisor checkin failed with not-null property error
Summary: Hypervisor checkin failed with not-null property error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Candlepin
Version: 6.1.7
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On: 1311664
Blocks: 1320316
TreeView+ depends on / blocked
 
Reported: 2016-03-08 22:43 UTC by Chris Roberts
Modified: 2020-04-15 14:24 UTC (History)
7 users (show)

Fixed In Version: candlepin-0.9.54-5
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1320316 (view as bug list)
Environment:
Last Closed: 2016-07-27 11:02:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Chris Roberts 2016-03-08 22:43:06 UTC 
Description of problem:
Seeing 2 cases now where hypervisor checkins fail and looking in candlepin logs 

Might be a dup of this bz but not sure

1311664

we 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


Version-Release number of selected component (if applicable):

candlepin-0.9.49.11-1.el7.noarch                            Wed Mar  2 12:09:31 
candlepin-common-1.0.22-1.el7.noarch                        Fri Oct  2 20:32:27 
candlepin-guice-3.0-2_redhat_1.el7.noarch                   Fri Oct  2 20:27:54 
candlepin-scl-1-5.el7.noarch                                Fri Oct  2 20:32:17 
candlepin-scl-quartz-2.1.5-6.el7.noarch                     Fri Oct  2 20:32:17 ff14cfafd37110	RSA/SHA256, Thu Sep  4 07:49:48 2014, Key ID 199e2f91fd431d51
candlepin-scl-rhino-1.7R3-3.el7.noarch                      Fri Oct  2 20:32:15 
candlepin-scl-runtime-1-5.el7.noarch                        Fri Oct  2 20:27:55 
candlepin-selinux-0.9.49.11-1.el7.noarch                    Wed Mar  2 12:09:34 
candlepin-tomcat-0.9.49.11-1.el7.noarch


Actual results:

http://pastebin.test.redhat.com/355029

Expected results:
Hypervisors to check in

Additional info:

Traceback from virt-who server

2016-02-23 09:23:52,731 [ERROR]  @subscriptionmanager.py:171 - Communication with server failed:
Traceback (most recent call last):
  File "/usr/share/virt-who/manager/subscriptionmanager/subscriptionmanager.py", line 167, in hypervisorCheckIn
    result = self.connection.hypervisorCheckIn(config.owner, config.env, serialized_mapping)
  File "/usr/lib64/python2.7/site-packages/rhsm/connection.py", line 903, in hypervisorCheckIn
    res = self.conn.request_post(url, host_guest_mapping)
  File "/usr/lib64/python2.7/site-packages/rhsm/connection.py", line 647, in request_post
    return self._request("POST", method, params)
  File "/usr/lib64/python2.7/site-packages/rhsm/connection.py", line 564, in _request
    self.validateResponse(result, request_type, handler)
  File "/usr/lib64/python2.7/site-packages/rhsm/connection.py", line 611, in validateResponse
    raise RestlibException(response['status'], error_msg, response.get('headers'))
RestlibException: Runtime Error org.hibernate.PropertyValueException: not-null property references a null or transient value: org.candlepin.model.GuestId.guestId at org.hibernate.engine.internal.Nullability.checkNullability:103
2016-02-23 09:23:52,732 [ERROR]  @virtwho.py:177 - Unable to send data: Communication with subscription manager failed with code 500: Runtime Error org.hibernate.PropertyValueException: not-null property references a null or transient value: org.candlepin.model.GuestId.guestId at org.hibernate.engine.internal.Nullability.checkNullability:103
2016-02-23 09:23:52,733 [ERROR]  @virtwho.py:305 - Sending data failed 5 times, report skipped
Comment 2 Kedar Bidarkar 2016-03-15 15:43:51 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?
Comment 3 Barnaby Court 2016-03-15 21:05:24 UTC 
This has been backported to the 0.9.54 hotfix branch
Comment 4 Chris Roberts 2016-04-01 14:34:46 UTC 
Kedar,

*** This bug has been marked as a duplicate of bug 1311664 ***
Comment 5 Mike McCune 2016-04-05 14:54:11 UTC 
we still need a Satellite 6 product bug if we are to ship this in a Satellite release.
Comment 6 Chris Roberts 2016-04-12 14:40:30 UTC 
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
Comment 7 Bryan Kearney 2016-07-27 11:02:47 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.