Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Andrew... the beta has not yet been certified for upgrades. We will, however, take this bug and make sure it works before GA.

Thanks Bryan, we found this out yesterday too. However, this is in direct contradiction of the ‘Upgrade’ instructions in the ‘Red Hat Satellite 6.1 Beta
Installation Guide’ (Chapter 6) - https://access.redhat.com/sites/default/files/attachments/red_hat_satellite-6.1-installation_guide-en-us.pdf

Raised : https://bugzilla.redhat.com/show_bug.cgi?id=1213887

(In reply to Andrew Schofield from comment #4)
> Thanks Bryan, we found this out yesterday too. However, this is in direct
> contradiction of the ‘Upgrade’ instructions in the ‘Red Hat Satellite 6.1
> Beta
> Installation Guide’ (Chapter 6) -
> https://access.redhat.com/sites/default/files/attachments/red_hat_satellite-
> 6.1-installation_guide-en-us.pdf

From a reproducer:

foreman=> select id, type, reference_id, name, value from parameters;
 id |      type       | reference_id |          name          |           value            
----+-----------------+--------------+------------------------+----------------------------
  1 | CommonParameter |              | default_activation_key | RHEL-default
  2 | CommonParameter |              | time-zone              | America/New_York --isUtc
  5 | GroupParameter  |            2 | kt_cv                  | content_view_case_01476902
  4 | GroupParameter  |            2 | kt_env                 | Library
  3 | GroupParameter  |            2 | kt_org                 | Default_Organization
  6 | GroupParameter  |            2 | kt_cv                  | content_view_case_01476902
  7 | GroupParameter  |            2 | kt_env                 | Library
  8 | GroupParameter  |            2 | kt_org                 | Default_Organization

 Adding KCS https://access.redhat.com/solutions/1575593

Connecting redmine issue http://projects.theforeman.org/issues/11339 from this bug

Can someone add instructions on how to check this data?
I don't know how to start the interface to this DB.

To detect duplicates a similar command can be used:

run

# foreman-rake console

and copy these two lines into it:


found = Parameter.all.map { |param|  {:name => param.name, :type => param.type, :reference_id => param.reference_id} }
puts (found.uniq.count == found.count ? "No Duplicates Found, proceed with upgrade." : "Duplicates Found, Upgrade will fail!")


If it prints:

No Duplicates Found, proceed with upgrade.
irb(main):003:0>

there is no issue. If instead it prints:

Duplicates Found, Upgrade will fail!
irb(main):003:0>

You will need to run the command from https://access.redhat.com/solutions/1575593 to delete the duplicated data.

*** Bug 1253673 has been marked as a duplicate of this bug. ***

Verified this bug with latest Satellite 6.1 GA Snap 17.
And the bug is no more reproducible. Hence changing the status to Verified.


The upgrade is successful.

[root.redhat.com] run: katello-installer --upgrade
[root.redhat.com] out: Upgrading...
[root.redhat.com] out: Upgrade Step: stop_services...
[root.redhat.com] out: Upgrade Step: start_mongo...
[root.redhat.com] out: Upgrade Step: migrate_pulp...
[root.redhat.com] out: Upgrade Step: start_httpd...
[root.redhat.com] out: Upgrade Step: migrate_candlepin...
[root.redhat.com] out: Upgrade Step: migrate_foreman...
[root.redhat.com] out: Upgrade Step: Running installer...
Installing             --- /etc/httpd/conf.d/05-foreman-ssl.conf.yaml]  2015-04- [93%] [................................................................................................................................................      Installing             Done                                               [100%] [..........................................................................................................................................................]
[root.redhat.com] out:   The full log is at /var/log/katello-installer/katello-installer.log
[root.redhat.com] out: Upgrade Step: restart_services...
[root.redhat.com] out: Upgrade Step: db_seed...
[root.redhat.com] out: Upgrade Step: errata_import (this may take a while) ...
[root.redhat.com] out: Upgrade Step: update_gpg_urls (this may take a while) ...
[root.redhat.com] out: Upgrade Step: update_repository_metadata (this may take a while) ...
[root.redhat.com] out: Katello upgrade completed!

Hello,

Is  there any prevision for this errata? Our customer is asking about it.

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-2015:1688