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.
Red Hat Satellite 6.8 upgrade fails with the error "Validation failed: Lookup values is invalid" at db:migrate stage.
~~~~~
[ WARN 2021-03-02T15:55:59 main] /Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]/returns:
[ WARN 2021-03-02T15:55:59 main] /Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]/returns: Caused by:
[ WARN 2021-03-02T15:55:59 main] /Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]/returns: ActiveRecord::RecordInvalid: Validation failed: Lookup values is invalid
[ WARN 2021-03-02T15:55:59 main] /Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]/returns: /opt/theforeman/tfm/root/usr/share/gems/gems/activerecord-6.0.3.1/lib/active_record/validations.rb:80:in `raise_validation_error'
[ WARN 2021-03-02T15:55:59 main] /Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]/returns: /opt/theforeman/tfm/root/usr/share/gems/gems/activerecord-6.0.3.1/lib/active_record/validations.rb:53:in `save!'
.....
[ WARN 2021-03-02T15:55:59 main] /Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]/returns: /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_openscap-4.0.5/db/migrate/20
201202110213_update_puppet_port_param_type.rb:26:in `update_port_type'
~~~~~
Version-Release number of selected component (if applicable):
Red Hat Satellite 6.4
Steps to Reproduce:
Make sure you have some invalid Matchers in foreman_scap_client --> port
Configure --> Smart Class Parameters --> click on foreman_scap_client --> click on "Smart Class Parameter" tab --> click on port
Run the upgrade on Red Hat Satellite 6.8.x -> 6.8.4-1 or 6.7 --> 6.8
Actual results:
- The upgrade fails with the error.
Expected results:
- The upgrade should be completed.
Verified
Verified with:
- Satellite 6.9.0 snap 18
- tfm-rubygem-foreman_openscap-4.1.3-1.el7sat.noarch
Test steps:
1. Install Satellite 6.8.3
2. Import puppet_foreman_scap_client
3. Do not set up any policies or make sure port param has override: false
4. Upgrade Satellite 6.8.3 to Satellite 6.9.0 snap 18
Observations:
- Upgrade completed successfully.
- No migration failures.
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 (Moderate: Satellite 6.9 Release), 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-2021:1313