Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionJitendra Yejare
2019-07-18 10:35:10 UTC
Description of problem:
When the discovery process is canceled for any reason, the discovery_attribute_set related table is not properly saved because database transactions are not used. Unfortunately, rails validator does not allow to save the record anymore, therefore, all subsequent discovery updates fail with 422 "Validation failed: Discovery attribute set can't be blank".
The initial discovery upload fails with 422 :ActiveRecord::RecordNotSaved: Failed to save the new associated discovery_attribute_set
Version-Release number of selected component (if applicable):
Satellite 6.6 snap 11
How reproducible:
Always
Steps to Reproduce:
1. Attempt to PXE boot the host to be discovered by satellite. Follow steps for provisioning from https://github.com/SatelliteQE/robottelo/blob/master/tests/foreman/cli/test_discoveredhost.py#L407 (Test : test_positive_provision_pxe_host_with_bios_syslinux)
Or,
1. We can POST the facts to satellite overs facts url - https://satellite.com/api/v2/discovered_hosts/facts (Follow steps from - https://github.com/SatelliteQE/robottelo/blob/master/tests/foreman/api/test_discoveredhost.py#L100 ( Test - test_positive_upload_facts )
Actual results:
1. The discovered host stucks when attribute stuck is missing
2. Throws error - 'Validation failed: Discovery attribute set can't be blank'
Expected results:
Discovered Host is successfully discovered.
Additional info:
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/RHSA-2019:3172
Description of problem: When the discovery process is canceled for any reason, the discovery_attribute_set related table is not properly saved because database transactions are not used. Unfortunately, rails validator does not allow to save the record anymore, therefore, all subsequent discovery updates fail with 422 "Validation failed: Discovery attribute set can't be blank". The initial discovery upload fails with 422 :ActiveRecord::RecordNotSaved: Failed to save the new associated discovery_attribute_set Version-Release number of selected component (if applicable): Satellite 6.6 snap 11 How reproducible: Always Steps to Reproduce: 1. Attempt to PXE boot the host to be discovered by satellite. Follow steps for provisioning from https://github.com/SatelliteQE/robottelo/blob/master/tests/foreman/cli/test_discoveredhost.py#L407 (Test : test_positive_provision_pxe_host_with_bios_syslinux) Or, 1. We can POST the facts to satellite overs facts url - https://satellite.com/api/v2/discovered_hosts/facts (Follow steps from - https://github.com/SatelliteQE/robottelo/blob/master/tests/foreman/api/test_discoveredhost.py#L100 ( Test - test_positive_upload_facts ) Actual results: 1. The discovered host stucks when attribute stuck is missing 2. Throws error - 'Validation failed: Discovery attribute set can't be blank' Expected results: Discovered Host is successfully discovered. Additional info: