I have received the following during the upgrade from katello 2.4 to
katello 3.0
Installing — /etc/httpd/conf.d/25-puppet.confatell2015-12-08
14 [99%]
[…
/Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]:
Failed to call refresh: /usr/sbin/foreman-rake db:migrate returned 1
instead of one of [0]
/Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]:
/usr/sbin/foreman-rake db:migrate returned 1 instead of one of [0]
Installing Done
[100%]
[…]
Something went wrong! Check the log for ERROR-level output
The full log is at /var/log/foreman-installer/katello.log
Inspecting /var/log/foreman-installer/katello.log I see two things:
First this error at the migrate_foreman step:
Upgrade Step: restart_services…
Upgrade Step: db_seed…
Upgrade Step: import_package_groups (this may take a while) …
Upgrade Step: import_rpms (this may take a while) …
Upgrade Step: import_distributions (this may take a while) …
Upgrade Step: import_puppet_modules (this may take a while) …
Upgrade Step: import_subscriptions (this may take a while) …
Upgrade Step: elasticsearch_message…
Elasticsearch has been removed as a dependency. The database files can be
removed manually with #rm -rf /var/lib/elasticsearch. Some packages are no
longer needed and can be removed: #rpm -e ruby193-rubygem-tire
tfm-rubygem-tire elasticsearch sigar-java sigar snappy-java lucene4-contrib
lucene4
Upgrade Step: add_export_distributor (this may take a while) …
Upgrade Step: remove_docker_v1_content (this may take a while) …
Upgrade Step: update_puppet_repository_distributors (this may take a while)
…
Upgrade Step: update_subscription_facet_backend_data (this may take a
while) …
Upgrade step update_subscription_facet_backend_data failed. Check logs for
more information.
[root@wellkatello ~]#
You've hit an error that I spent the past two days debugging for another
user but have not been able to replicate locally. Couple of questions for
you:
do you have a backup of your 2.4 before upgrading?
If yes, would you be able to privately share backups of your database
with me from 2.4? If you are unable to share it out, would you be willing
to help by doing some live debugging on IRC or some other means?
···
On Jul 1, 2016 1:15 AM, "Dylan Baars" wrote:
I had a further error, final output below
Upgrade Step: restart_services…
Upgrade Step: db_seed…
Upgrade Step: import_package_groups (this may take a while) …
Upgrade Step: import_rpms (this may take a while) …
Upgrade Step: import_distributions (this may take a while) …
Upgrade Step: import_puppet_modules (this may take a while) …
Upgrade Step: import_subscriptions (this may take a while) …
Upgrade Step: elasticsearch_message…
Elasticsearch has been removed as a dependency. The database files can be
removed manually with #rm -rf /var/lib/elasticsearch. Some packages are no
longer needed and can be removed: #rpm -e ruby193-rubygem-tire
tfm-rubygem-tire elasticsearch sigar-java sigar snappy-java lucene4-contrib
lucene4
Upgrade Step: add_export_distributor (this may take a while) …
Upgrade Step: remove_docker_v1_content (this may take a while) …
Upgrade Step: update_puppet_repository_distributors (this may take a
while) …
Upgrade Step: update_subscription_facet_backend_data (this may take a
while) …
Upgrade step update_subscription_facet_backend_data failed. Check logs for
more information.
[root@wellkatello ~]#
Happy to do either! I guess a DB backup is easier for you to work with, let
me know how to get that to you (you're after the Postgres db I take it?)
Dylan
···
On Friday, 1 July 2016, Eric D Helms wrote:
Dylan,
You’ve hit an error that I spent the past two days debugging for another
user but have not been able to replicate locally. Couple of questions for
you:
do you have a backup of your 2.4 before upgrading?
If yes, would you be able to privately share backups of your database
with me from 2.4? If you are unable to share it out, would you be willing
to help by doing some live debugging on IRC or some other means?
On Jul 1, 2016 1:15 AM, “Dylan Baars” <baarsd@gmail.com > <javascript:_e(%7B%7D,‘cvml’,‘baarsd@gmail.com’);>> wrote:
I had a further error, final output below
Upgrade Step: restart_services…
Upgrade Step: db_seed…
Upgrade Step: import_package_groups (this may take a while) …
Upgrade Step: import_rpms (this may take a while) …
Upgrade Step: import_distributions (this may take a while) …
Upgrade Step: import_puppet_modules (this may take a while) …
Upgrade Step: import_subscriptions (this may take a while) …
Upgrade Step: elasticsearch_message…
Elasticsearch has been removed as a dependency. The database files can be
removed manually with #rm -rf /var/lib/elasticsearch. Some packages are no
longer needed and can be removed: #rpm -e ruby193-rubygem-tire
tfm-rubygem-tire elasticsearch sigar-java sigar snappy-java lucene4-contrib
lucene4
Upgrade Step: add_export_distributor (this may take a while) …
Upgrade Step: remove_docker_v1_content (this may take a while) …
Upgrade Step: update_puppet_repository_distributors (this may take a
while) …
Upgrade Step: update_subscription_facet_backend_data (this may take a
while) …
Upgrade step update_subscription_facet_backend_data failed. Check logs
for more information.
[root@wellkatello ~]#
Yea, a dump of the 'foreman' and 'candlepin' database as l will need both
from the 2.4 box preupgrade. The easiest option is to use [1] and email me ( ehelms@redhat.com) the file names that you upload. If you'd prefer a
different method please let me know and we'll figure something out.
You’ve hit an error that I spent the past two days debugging for another
user but have not been able to replicate locally. Couple of questions for
you:
do you have a backup of your 2.4 before upgrading?
If yes, would you be able to privately share backups of your database
with me from 2.4? If you are unable to share it out, would you be willing
to help by doing some live debugging on IRC or some other means?
On Jul 1, 2016 1:15 AM, “Dylan Baars” baarsd@gmail.com wrote:
I had a further error, final output below
Upgrade Step: restart_services…
Upgrade Step: db_seed…
Upgrade Step: import_package_groups (this may take a while) …
Upgrade Step: import_rpms (this may take a while) …
Upgrade Step: import_distributions (this may take a while) …
Upgrade Step: import_puppet_modules (this may take a while) …
Upgrade Step: import_subscriptions (this may take a while) …
Upgrade Step: elasticsearch_message…
Elasticsearch has been removed as a dependency. The database files can
be removed manually with #rm -rf /var/lib/elasticsearch. Some packages are
no longer needed and can be removed: #rpm -e ruby193-rubygem-tire
tfm-rubygem-tire elasticsearch sigar-java sigar snappy-java lucene4-contrib
lucene4
Upgrade Step: add_export_distributor (this may take a while) …
Upgrade Step: remove_docker_v1_content (this may take a while) …
Upgrade Step: update_puppet_repository_distributors (this may take a
while) …
Upgrade Step: update_subscription_facet_backend_data (this may take a
while) …
Upgrade step update_subscription_facet_backend_data failed. Check logs
for more information.
[root@wellkatello ~]#
···
On Fri, Jul 1, 2016 at 10:58 PM, Eric D Helms wrote:
Yea, a dump of the ‘foreman’ and ‘candlepin’ database as l will need both
from the 2.4 box preupgrade. The easiest option is to use [1] and email me ( ehelms@redhat.com) the file names that you upload. If you’d prefer a
different method please let me know and we’ll figure something out.
You’ve hit an error that I spent the past two days debugging for another
user but have not been able to replicate locally. Couple of questions for
you:
do you have a backup of your 2.4 before upgrading?
If yes, would you be able to privately share backups of your database
with me from 2.4? If you are unable to share it out, would you be willing
to help by doing some live debugging on IRC or some other means?
On Jul 1, 2016 1:15 AM, “Dylan Baars” baarsd@gmail.com wrote:
I had a further error, final output below
Upgrade Step: restart_services…
Upgrade Step: db_seed…
Upgrade Step: import_package_groups (this may take a while) …
Upgrade Step: import_rpms (this may take a while) …
Upgrade Step: import_distributions (this may take a while) …
Upgrade Step: import_puppet_modules (this may take a while) …
Upgrade Step: import_subscriptions (this may take a while) …
Upgrade Step: elasticsearch_message…
Elasticsearch has been removed as a dependency. The database files can
be removed manually with #rm -rf /var/lib/elasticsearch. Some packages are
no longer needed and can be removed: #rpm -e ruby193-rubygem-tire
tfm-rubygem-tire elasticsearch sigar-java sigar snappy-java lucene4-contrib
lucene4
Upgrade Step: add_export_distributor (this may take a while) …
Upgrade Step: remove_docker_v1_content (this may take a while) …
Upgrade Step: update_puppet_repository_distributors (this may take a
while) …
Upgrade Step: update_subscription_facet_backend_data (this may take a
while) …
Upgrade step update_subscription_facet_backend_data failed. Check logs
for more information.
[root@wellkatello ~]#
Thanks a ton Dylan! In the end the fix was a simple one [1] but had large
ramifications that I could not have solved without your database!
If you'd like to patch your 3.0.1 with the change and do your upgrade, feel
free. I tested it on your data set with success. I will be working to push
out a 3.0.2 that includes the fix officially as soon as it is merged if
you'd rather wait for an official release of it.
Again, thanks a ton for sharing your data to help resolve this for everyone,
Eric
Yea, a dump of the ‘foreman’ and ‘candlepin’ database as l will need both
from the 2.4 box preupgrade. The easiest option is to use [1] and email me ( ehelms@redhat.com) the file names that you upload. If you’d prefer a
different method please let me know and we’ll figure something out.
You’ve hit an error that I spent the past two days debugging for
another user but have not been able to replicate locally. Couple of
questions for you:
do you have a backup of your 2.4 before upgrading?
If yes, would you be able to privately share backups of your
database with me from 2.4? If you are unable to share it out, would you be
willing to help by doing some live debugging on IRC or some other means?
On Jul 1, 2016 1:15 AM, “Dylan Baars” baarsd@gmail.com wrote:
I had a further error, final output below
Upgrade Step: restart_services…
Upgrade Step: db_seed…
Upgrade Step: import_package_groups (this may take a while) …
Upgrade Step: import_rpms (this may take a while) …
Upgrade Step: import_distributions (this may take a while) …
Upgrade Step: import_puppet_modules (this may take a while) …
Upgrade Step: import_subscriptions (this may take a while) …
Upgrade Step: elasticsearch_message…
Elasticsearch has been removed as a dependency. The database files can
be removed manually with #rm -rf /var/lib/elasticsearch. Some packages are
no longer needed and can be removed: #rpm -e ruby193-rubygem-tire
tfm-rubygem-tire elasticsearch sigar-java sigar snappy-java lucene4-contrib
lucene4
Upgrade Step: add_export_distributor (this may take a while) …
Upgrade Step: remove_docker_v1_content (this may take a while) …
Upgrade Step: update_puppet_repository_distributors (this may take a
while) …
Upgrade Step: update_subscription_facet_backend_data (this may take a
while) …
Upgrade step update_subscription_facet_backend_data failed. Check logs
for more information.
[root@wellkatello ~]#
no worries! Glad I could help (and of course thanks for helping me!). If I
apply the change to my existing 3.0.1 install which failed, do I just run
the upgrade command again? Or should I revert my VM to 2.4 and do the
upgrade again?
Dylan
···
On Sat, Jul 2, 2016 at 4:22 AM, Eric D Helms wrote:
Thanks a ton Dylan! In the end the fix was a simple one [1] but had large
ramifications that I could not have solved without your database!
If you’d like to patch your 3.0.1 with the change and do your upgrade,
feel free. I tested it on your data set with success. I will be working to
push out a 3.0.2 that includes the fix officially as soon as it is merged
if you’d rather wait for an official release of it.
Again, thanks a ton for sharing your data to help resolve this for
everyone,
Eric
Yea, a dump of the ‘foreman’ and ‘candlepin’ database as l will need
both from the 2.4 box preupgrade. The easiest option is to use [1] and
email me (ehelms@redhat.com) the file names that you upload. If you’d
prefer a different method please let me know and we’ll figure something out.
You’ve hit an error that I spent the past two days debugging for
another user but have not been able to replicate locally. Couple of
questions for you:
do you have a backup of your 2.4 before upgrading?
If yes, would you be able to privately share backups of your
database with me from 2.4? If you are unable to share it out, would you be
willing to help by doing some live debugging on IRC or some other means?
On Jul 1, 2016 1:15 AM, “Dylan Baars” baarsd@gmail.com wrote:
I had a further error, final output below
Upgrade Step: restart_services…
Upgrade Step: db_seed…
Upgrade Step: import_package_groups (this may take a while) …
Upgrade Step: import_rpms (this may take a while) …
Upgrade Step: import_distributions (this may take a while) …
Upgrade Step: import_puppet_modules (this may take a while) …
Upgrade Step: import_subscriptions (this may take a while) …
Upgrade Step: elasticsearch_message…
Elasticsearch has been removed as a dependency. The database files
can be removed manually with #rm -rf /var/lib/elasticsearch. Some packages
are no longer needed and can be removed: #rpm -e ruby193-rubygem-tire
tfm-rubygem-tire elasticsearch sigar-java sigar snappy-java lucene4-contrib
lucene4
Upgrade Step: add_export_distributor (this may take a while) …
Upgrade Step: remove_docker_v1_content (this may take a while) …
Upgrade Step: update_puppet_repository_distributors (this may take a
while) …
Upgrade Step: update_subscription_facet_backend_data (this may take a
while) …
Upgrade step update_subscription_facet_backend_data failed. Check
logs for more information.
[root@wellkatello ~]#
> Morning Eric,
>
> no worries! Glad I could help (and of course thanks for helping me!). If I
> apply the change to my existing 3.0.1 install which failed, do I just run
> the upgrade command again? Or should I revert my VM to 2.4 and do the
> upgrade again?
>
To keep going with your current 3.0 will require some migration reverting
and while it's do-able, if you can rollback to your 2.4 and go fresh I'd
recommend that.
Eric
···
On Fri, Jul 1, 2016 at 3:24 PM, Dylan Baars wrote:
Thanks a ton Dylan! In the end the fix was a simple one [1] but had large
ramifications that I could not have solved without your database!
If you’d like to patch your 3.0.1 with the change and do your upgrade,
feel free. I tested it on your data set with success. I will be working to
push out a 3.0.2 that includes the fix officially as soon as it is merged
if you’d rather wait for an official release of it.
Again, thanks a ton for sharing your data to help resolve this for
everyone,
Eric
Yea, a dump of the ‘foreman’ and ‘candlepin’ database as l will need
both from the 2.4 box preupgrade. The easiest option is to use [1] and
email me (ehelms@redhat.com) the file names that you upload. If you’d
prefer a different method please let me know and we’ll figure something out.
You’ve hit an error that I spent the past two days debugging for
another user but have not been able to replicate locally. Couple of
questions for you:
do you have a backup of your 2.4 before upgrading?
If yes, would you be able to privately share backups of your
database with me from 2.4? If you are unable to share it out, would you be
willing to help by doing some live debugging on IRC or some other means?
On Jul 1, 2016 1:15 AM, “Dylan Baars” baarsd@gmail.com wrote:
I had a further error, final output below
Upgrade Step: restart_services…
Upgrade Step: db_seed…
Upgrade Step: import_package_groups (this may take a while) …
Upgrade Step: import_rpms (this may take a while) …
Upgrade Step: import_distributions (this may take a while) …
Upgrade Step: import_puppet_modules (this may take a while) …
Upgrade Step: import_subscriptions (this may take a while) …
Upgrade Step: elasticsearch_message…
Elasticsearch has been removed as a dependency. The database files
can be removed manually with #rm -rf /var/lib/elasticsearch. Some packages
are no longer needed and can be removed: #rpm -e ruby193-rubygem-tire
tfm-rubygem-tire elasticsearch sigar-java sigar snappy-java lucene4-contrib
lucene4
Upgrade Step: add_export_distributor (this may take a while) …
Upgrade Step: remove_docker_v1_content (this may take a while) …
Upgrade Step: update_puppet_repository_distributors (this may take a
while) …
Upgrade Step: update_subscription_facet_backend_data (this may take
a while) …
Upgrade step update_subscription_facet_backend_data failed. Check
logs for more information.
[root@wellkatello ~]#
FYI, my VMware hosts, which didn't appear under Hosts > All Hosts in 2.4,
now do (they appear in both "All Hosts" and "Content Hosts" pages now) but
they had their name reverted their UUID names so I had to manually rename
them again
>
>
>
To keep going with your current 3.0 will require some migration reverting
···
On Saturday, July 2, 2016 at 7:54:23 AM UTC+12, Eric Helms wrote:
> and while it's do-able, if you can rollback to your 2.4 and go fresh I'd
> recommend that.
>
> Eric
>
