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 1774167 - 6.6 Upgrade Error: Host parameters with @ symbol cause failed upgrades: 765: unexpected token at '@Core'
Summary: 6.6 Upgrade Error: Host parameters with @ symbol cause failed upgrades: 765: ...
Keywords:
Status: CLOSED DUPLICATE of bug 1767443
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Parameters
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.7.0
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-19 18:04 UTC by Mike McCune
Modified: 2019-11-21 13:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-21 13:26:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mike McCune 2019-11-19 18:04:53 UTC
1) specify a host parameter with the @ symbol, eg, a package-set, as found in the database:


> echo "select id, name, value, type from parameters" | sudo -u postgres psql -d foreman
could not change directory to "/root"
 id |        name        |        value         |      type      
----+--------------------+----------------------+-----------------
  1 | enable-epel        | false                | CommonParameter
  2 | enable-puppet5     | true                 | CommonParameter
  3 | kt_activation_keys | DEV-RHEL7-INFRA-VIRT | GroupParameter
  4 | kt_activation_keys | DEV-RHEL8-INFRA-VIRT | GroupParameter
  5 | package-set        | @Core                | GroupParameter
  7 | package-set        | @Base                | HostParameter
  8 | package-set        | @Base                | HostParameter
(7 rows)

2) Attempt to upgrade from 6.5 to 6.6

Upgrade Step: migrate_foreman...                                                                                                                  
rake aborted!                                                                                                                                     
StandardError: An error has occurred, this and all later migrations canceled:                                                                     
                                                                                                                                                  
765: unexpected token at '@Core'                                                                                                                  
/usr/share/foreman/db/migrate/20181105061336_cast_key_types_and_values_in_parameters.rb:22:in `rescue in override_key_type_and_value'

Workaround is to update these values via manual SQL from the root shell:

# echo "update parameters set value = 'FixMe' where value like '@%';" | sudo -u postgres psql -d foreman

Then perform the upgrade and correct the parameters in the UI by hand.

Comment 4 Tomer Brisker 2019-11-21 13:26:40 UTC
This is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1767443

*** This bug has been marked as a duplicate of bug 1767443 ***


Note You need to log in before you can comment on or make changes to this bug.