[katello] Failure Upgrading from Katello 2.0 to 2.1

GD1 · March 4, 2015, 2:52pm

HI all, I've tried upgrading Katello from 2.0 to 2.1 and it fails. I've
run the manual steps afterwards, several times, with no avail. I am
running on Redhat 7.0. The main issue is with pulp content not
importing/migrating. Any advice on how to get this working again? Here's
some relevant logs:

sudo -u apache pulp-manage-db returns this:
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
UpdateFailed [erratum]
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: Traceback
(most recent call last):
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File
"/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 111, in
main
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
_auto_manage_db(options)
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File
"/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 135, in
_auto_manage_db
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
load_content_types()
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File
"/usr/lib/python2.7/site-packages/pulp/plugins/loader/api.py", line 414, in
load_content_types
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
_load_type_definitions(descriptors)
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File
"/usr/lib/python2.7/site-packages/pulp/plugins/loader/api.py", line 451, in
_load_type_definitions
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
database.update_database(definitions)
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File
"/usr/lib/python2.7/site-packages/pulp/plugins/types/database.py", line
131, in update_database
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: raise
UpdateFailed(error_defs)
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
UpdateFailed: UpdateFailed [erratum]
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:

[ERROR 2015-03-04 09:18:29 main]
rake aborted!
500 Internal Server Error

Tasks: TOP => katello:upgrades:2.1:import_errata
(See full trace by running task with --trace)
Importing Errata

[root@servername share]# foreman-rake katello:upgrades:2.1:import_errata
–trace
** Invoke katello:upgrades:2.1:import_errata (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute katello:upgrades:2.1:import_errata
Importing Errata
rake aborted!
500 Internal Server Error
/opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/abstract_response.rb:48:in
return!' /opt/rh/ruby193/root/usr/share/gems/gems/runcible-1.3.0/lib/runcible/base.rb:92:inblock in get_response'
/opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:228:in
call' /opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:228:inprocess_result'
/opt/rh/ruby193/root/usr/share/gems/gems/rbovirt-0.0.29/lib/restclient_ext/request.rb:50:in
block in transmit' /opt/rh/ruby193/root/usr/share/ruby/net/http.rb:746:instart'
/opt/rh/ruby193/root/usr/share/gems/gems/rbovirt-0.0.29/lib/restclient_ext/request.rb:44:in
transmit' /opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:64:inexecute'
/opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:33:in
execute' /opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/resource.rb:67:inpost'
/opt/rh/ruby193/root/usr/share/gems/gems/runcible-1.3.0/lib/runcible/base.rb:91:in
get_response' /opt/rh/ruby193/root/usr/share/gems/gems/runcible-1.3.0/lib/runcible/base.rb:82:incall'
/opt/rh/ruby193/root/usr/share/gems/gems/runcible-1.3.0/lib/runcible/resources/unit.rb:43:in
search' /opt/rh/ruby193/root/usr/share/gems/gems/katello-2.1.1/app/models/katello/glue/pulp/pulp_content_unit.rb:99:infetch_all'
/opt/rh/ruby193/root/usr/share/gems/gems/katello-2.1.1/app/models/katello/glue/pulp/pulp_content_unit.rb:50:in
import_all' /opt/rh/ruby193/root/usr/share/gems/gems/katello-2.1.1/lib/katello/tasks/upgrades/2.1/import_errata.rake:27:inblock (4 levels) in <top (required)>'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:in call' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:inblock in execute'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:in each' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:inexecute'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:in block in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:ininvoke'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:116:in invoke_task' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock (2
levels) in top_level'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in each' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock in
top_level'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:intop_level'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:in block in run' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:in run' /opt/rh/ruby193/root/usr/bin/rake:32:in<main>'
Tasks: TOP => katello:upgrades:2.1:import_errata

stbenjam · March 5, 2015, 6:43am

> HI all, I've tried upgrading Katello from 2.0 to 2.1 and it fails. I've
> run the manual steps afterwards, several times, with no avail. I am
> running on Redhat 7.0. The main issue is with pulp content not
> importing/migrating. Any advice on how to get this working again? Here's
> some relevant logs:
>
> sudo -u apache pulp-manage-db returns this:
> Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
> UpdateFailed [erratum]
> Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: Traceback
> (most recent call last):
> Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File
> "/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 111, in
> main
> Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
> _auto_manage_db(options)
> Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File
> "/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 135, in
> _auto_manage_db
> Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
> load_content_types()
> Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File
> "/usr/lib/python2.7/site-packages/pulp/plugins/loader/api.py", line 414, in
> load_content_types
> Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
> _load_type_definitions(descriptors)
> Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File
> "/usr/lib/python2.7/site-packages/pulp/plugins/loader/api.py", line 451, in
> _load_type_definitions
> Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
> database.update_database(definitions)
> Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File
> "/usr/lib/python2.7/site-packages/pulp/plugins/types/database.py", line
> 131, in update_database
> Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: raise
> UpdateFailed(error_defs)
> Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
> UpdateFailed: UpdateFailed [erratum]
> Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:

Do you have EPEL 7 synced? There's an issue where they issue very long
errata names. I'm relatively certain this is the problem.

This is fixed in Pulp 2.6, but you can try this workaround:
https://bugzilla.redhat.com/show_bug.cgi?id=1175616#c5

And run the upgrade again.

>
>
> [ERROR 2015-03-04 09:18:29 main]
> rake aborted!
> 500 Internal Server Error
>
> Tasks: TOP => katello:upgrades:2.1:import_errata
> (See full trace by running task with --trace)
> Importing Errata
>
>
> [root@servername share]# foreman-rake katello:upgrades:2.1:import_errata
> --trace

This failing is just a product of the previous failure.

···

On Wed, Mar 04, 2015 at 06:52:56AM -0800, GD wrote:

** Invoke katello:upgrades:2.1:import_errata (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute katello:upgrades:2.1:import_errata
Importing Errata
rake aborted!
500 Internal Server Error
/opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/abstract_response.rb:48:in
return!' /opt/rh/ruby193/root/usr/share/gems/gems/runcible-1.3.0/lib/runcible/base.rb:92:inblock in get_response’
/opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:228:in
call' /opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:228:inprocess_result’
/opt/rh/ruby193/root/usr/share/gems/gems/rbovirt-0.0.29/lib/restclient_ext/request.rb:50:in
block in transmit' /opt/rh/ruby193/root/usr/share/ruby/net/http.rb:746:instart’
/opt/rh/ruby193/root/usr/share/gems/gems/rbovirt-0.0.29/lib/restclient_ext/request.rb:44:in
transmit' /opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:64:inexecute’
/opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:33:in
execute' /opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/resource.rb:67:inpost’
/opt/rh/ruby193/root/usr/share/gems/gems/runcible-1.3.0/lib/runcible/base.rb:91:in
get_response' /opt/rh/ruby193/root/usr/share/gems/gems/runcible-1.3.0/lib/runcible/base.rb:82:incall’
/opt/rh/ruby193/root/usr/share/gems/gems/runcible-1.3.0/lib/runcible/resources/unit.rb:43:in
search' /opt/rh/ruby193/root/usr/share/gems/gems/katello-2.1.1/app/models/katello/glue/pulp/pulp_content_unit.rb:99:infetch_all’
/opt/rh/ruby193/root/usr/share/gems/gems/katello-2.1.1/app/models/katello/glue/pulp/pulp_content_unit.rb:50:in
import_all' /opt/rh/ruby193/root/usr/share/gems/gems/katello-2.1.1/lib/katello/tasks/upgrades/2.1/import_errata.rake:27:inblock (4 levels) in <top (required)>’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:in call' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:inblock in execute’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:in each' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:inexecute’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:in block in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:ininvoke’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:116:in invoke_task' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock (2
levels) in top_level’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in each' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock in
top_level’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:intop_level’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:in block in run' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:in run' /opt/rh/ruby193/root/usr/bin/rake:32:in'
Tasks: TOP => katello:upgrades:2.1:import_errata

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

GD1 · March 5, 2015, 12:42pm

Thanks for the response. EPEL was synced, but perhaps I need to republish
all affected content views? After I do that, I'll attempt the upgrade
again. The workaround looks promising.

···

On Thursday, March 5, 2015 at 1:43:31 AM UTC-5, Stephen Benjamin wrote: > > On Wed, Mar 04, 2015 at 06:52:56AM -0800, GD wrote: > > HI all, I've tried upgrading Katello from 2.0 to 2.1 and it fails. I've > > run the manual steps afterwards, several times, with no avail. I am > > running on Redhat 7.0. The main issue is with pulp content not > > importing/migrating. Any advice on how to get this working again? > Here's > > some relevant logs: > > > > sudo -u apache pulp-manage-db returns this: > > Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: > > UpdateFailed [erratum] > > Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: > Traceback > > (most recent call last): > > Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File > > "/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 111, > in > > main > > Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: > > _auto_manage_db(options) > > Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File > > "/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 135, > in > > _auto_manage_db > > Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: > > load_content_types() > > Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File > > "/usr/lib/python2.7/site-packages/pulp/plugins/loader/api.py", line 414, > in > > load_content_types > > Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: > > _load_type_definitions(descriptors) > > Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File > > "/usr/lib/python2.7/site-packages/pulp/plugins/loader/api.py", line 451, > in > > _load_type_definitions > > Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: > > database.update_database(definitions) > > Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File > > "/usr/lib/python2.7/site-packages/pulp/plugins/types/database.py", line > > 131, in update_database > > Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: > raise > > UpdateFailed(error_defs) > > Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: > > UpdateFailed: UpdateFailed [erratum] > > Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: > > Do you have EPEL 7 synced? There's an issue where they issue very long > errata names. I'm relatively certain this is the problem. > > This is fixed in Pulp 2.6, but you can try this workaround: > https://bugzilla.redhat.com/show_bug.cgi?id=1175616#c5 > > And run the upgrade again. > > > > > > > [ERROR 2015-03-04 09:18:29 main] > > rake aborted! > > 500 Internal Server Error > > > > Tasks: TOP => katello:upgrades:2.1:import_errata > > (See full trace by running task with --trace) > > Importing Errata > > > > > > [root@servername share]# foreman-rake katello:upgrades:2.1:import_errata > > --trace > > This failing is just a product of the previous failure. > > > ** Invoke katello:upgrades:2.1:import_errata (first_time) > > ** Invoke environment (first_time) > > ** Execute environment > > ** Execute katello:upgrades:2.1:import_errata > > Importing Errata > > rake aborted! > > 500 Internal Server Error > > > /opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/abstract_response.rb:48:in > > > `return!' > > > /opt/rh/ruby193/root/usr/share/gems/gems/runcible-1.3.0/lib/runcible/base.rb:92:in > > > `block in get_response' > > > /opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:228:in > > > `call' > > > /opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:228:in > > > `process_result' > > > /opt/rh/ruby193/root/usr/share/gems/gems/rbovirt-0.0.29/lib/restclient_ext/request.rb:50:in > > > `block in transmit' > > /opt/rh/ruby193/root/usr/share/ruby/net/http.rb:746:in `start' > > > /opt/rh/ruby193/root/usr/share/gems/gems/rbovirt-0.0.29/lib/restclient_ext/request.rb:44:in > > > `transmit' > > > /opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:64:in > > > `execute' > > > /opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:33:in > > > `execute' > > > /opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/resource.rb:67:in > > > `post' > > > /opt/rh/ruby193/root/usr/share/gems/gems/runcible-1.3.0/lib/runcible/base.rb:91:in > > > `get_response' > > > /opt/rh/ruby193/root/usr/share/gems/gems/runcible-1.3.0/lib/runcible/base.rb:82:in > > > `call' > > > /opt/rh/ruby193/root/usr/share/gems/gems/runcible-1.3.0/lib/runcible/resources/unit.rb:43:in > > > `search' > > > /opt/rh/ruby193/root/usr/share/gems/gems/katello-2.1.1/app/models/katello/glue/pulp/pulp_content_unit.rb:99:in > > > `fetch_all' > > > /opt/rh/ruby193/root/usr/share/gems/gems/katello-2.1.1/app/models/katello/glue/pulp/pulp_content_unit.rb:50:in > > > `import_all' > > > /opt/rh/ruby193/root/usr/share/gems/gems/katello-2.1.1/lib/katello/tasks/upgrades/2.1/import_errata.rake:27:in > > > `block (4 levels) in ' > > /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:in `call' > > /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:in `block in > execute' > > /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:in `each' > > /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:in `execute' > > /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:in `block in > > invoke_with_call_chain' > > /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:in `mon_synchronize' > > /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in > > `invoke_with_call_chain' > > /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:in `invoke' > > /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:116:in > `invoke_task' > > /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in `block (2 > > levels) in top_level' > > /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in `each' > > /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in `block in > > top_level' > > /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in > > `standard_exception_handling' > > /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:in > `top_level' > > /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:in `block in > run' > > /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in > > `standard_exception_handling' > > /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:in `run' > > /opt/rh/ruby193/root/usr/bin/rake:32:in `' > > Tasks: TOP => katello:upgrades:2.1:import_errata > > > > -- > > You received this message because you are subscribed to the Google > Groups "Foreman users" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to foreman-user...@googlegroups.com . > > To post to this group, send email to forema...@googlegroups.com > . > > Visit this group at http://groups.google.com/group/foreman-users. > > For more options, visit https://groups.google.com/d/optout. > > > -- > Best Regards, > > Stephen Benjamin > Red Hat Engineering >

stbenjam · March 5, 2015, 1:05pm

> Thanks for the response. EPEL was synced, but perhaps I need to republish
> all affected content views? After I do that, I'll attempt the upgrade
> again. The workaround looks promising.

No, you don't need to republish any CV's., it doesn't have anything to
do with that, Pulp 2.5 in Katello 2.1 can't handle the long errata
names used by EPEL, it'll be fixed in 2.2, but for now you can try the
mongo workaround by dropping the index on that column.

···

On Thu, Mar 05, 2015 at 04:42:46AM -0800, GD wrote:

On Thursday, March 5, 2015 at 1:43:31 AM UTC-5, Stephen Benjamin wrote:

On Wed, Mar 04, 2015 at 06:52:56AM -0800, GD wrote:

HI all, I’ve tried upgrading Katello from 2.0 to 2.1 and it fails. I’ve
run the manual steps afterwards, several times, with no avail. I am
running on Redhat 7.0. The main issue is with pulp content not
importing/migrating. Any advice on how to get this working again?
Here’s
some relevant logs:

sudo -u apache pulp-manage-db returns this:
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
UpdateFailed [erratum]
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
Traceback
(most recent call last):
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File
"/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 111,
in
main
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
_auto_manage_db(options)
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File
"/usr/lib/python2.7/site-packages/pulp/server/db/manage.py", line 135,
in
_auto_manage_db
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
load_content_types()
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File
"/usr/lib/python2.7/site-packages/pulp/plugins/loader/api.py", line 414,
in
load_content_types
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
_load_type_definitions(descriptors)
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File
"/usr/lib/python2.7/site-packages/pulp/plugins/loader/api.py", line 451,
in
_load_type_definitions
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
database.update_database(definitions)
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL: File
"/usr/lib/python2.7/site-packages/pulp/plugins/types/database.py", line
131, in update_database
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
raise
UpdateFailed(error_defs)
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:
UpdateFailed: UpdateFailed [erratum]
Mar 4 09:13:44 servername pulp: pulp.server.db.manage:CRITICAL:

Do you have EPEL 7 synced? There’s an issue where they issue very long
errata names. I’m relatively certain this is the problem.

This is fixed in Pulp 2.6, but you can try this workaround:
https://bugzilla.redhat.com/show_bug.cgi?id=1175616#c5

And run the upgrade again.

[ERROR 2015-03-04 09:18:29 main]
rake aborted!
500 Internal Server Error

Tasks: TOP => katello:upgrades:2.1:import_errata
(See full trace by running task with --trace)
Importing Errata

[root@servername share]# foreman-rake katello:upgrades:2.1:import_errata
–trace

This failing is just a product of the previous failure.

** Invoke katello:upgrades:2.1:import_errata (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute katello:upgrades:2.1:import_errata
Importing Errata
rake aborted!
500 Internal Server Error

/opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/abstract_response.rb:48:in

`return!’

/opt/rh/ruby193/root/usr/share/gems/gems/runcible-1.3.0/lib/runcible/base.rb:92:in

`block in get_response’

/opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:228:in

`call’

/opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:228:in

`process_result’

/opt/rh/ruby193/root/usr/share/gems/gems/rbovirt-0.0.29/lib/restclient_ext/request.rb:50:in

block in transmit' /opt/rh/ruby193/root/usr/share/ruby/net/http.rb:746:instart’

/opt/rh/ruby193/root/usr/share/gems/gems/rbovirt-0.0.29/lib/restclient_ext/request.rb:44:in

`transmit’

/opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:64:in

`execute’

/opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:33:in

`execute’

/opt/rh/ruby193/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/resource.rb:67:in

`post’

/opt/rh/ruby193/root/usr/share/gems/gems/runcible-1.3.0/lib/runcible/base.rb:91:in

`get_response’

/opt/rh/ruby193/root/usr/share/gems/gems/runcible-1.3.0/lib/runcible/base.rb:82:in

`call’

/opt/rh/ruby193/root/usr/share/gems/gems/runcible-1.3.0/lib/runcible/resources/unit.rb:43:in

`search’

/opt/rh/ruby193/root/usr/share/gems/gems/katello-2.1.1/app/models/katello/glue/pulp/pulp_content_unit.rb:99:in

`fetch_all’

/opt/rh/ruby193/root/usr/share/gems/gems/katello-2.1.1/app/models/katello/glue/pulp/pulp_content_unit.rb:50:in

`import_all’

/opt/rh/ruby193/root/usr/share/gems/gems/katello-2.1.1/lib/katello/tasks/upgrades/2.1/import_errata.rake:27:in

block (4 levels) in <top (required)>' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:incall’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:in block in execute' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:ineach’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:in execute' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:inblock in
invoke_with_call_chain’
/opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:in mon_synchronize' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:ininvoke_with_call_chain’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:in invoke' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:116:ininvoke_task’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in block (2 levels) in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:ineach’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in block in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:in
top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:inblock in
run’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:inrun’
/opt/rh/ruby193/root/usr/bin/rake:32:in `'
Tasks: TOP => katello:upgrades:2.1:import_errata

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-user...@googlegroups.com <javascript:>.
To post to this group, send email to forema...@googlegroups.com
<javascript:>.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

GD1 · March 6, 2015, 1:50pm

After running the dropIndex command I still get this error, which
ultimately causes the installer to fail:

OperationFailure: Btree::insert: key too large to index, failing
pulp_database.units_erratum.$title_1 1267 { :
"ghc-7.0.4-46.el6,haskell-platform-2011.4.0.0-6.el6,ghc-rpm-macros-0.15.5-1.el6,hscolour-1.19-6.el6,ghc-HUnit-1.2.4.2-3.el6,ghc-transformers-0.2.2.0-14…"
}

Checking to make sure the index is not there…

> db.units_erratum.getIndexes()
[
{
"v" : 1,
"key" : {
"_id" : 1
},
"ns" : "pulp_database.units_erratum",
"name" : "id"
},
{
"v" : 1,
"unique" : true,
"key" : {
"id" : 1
},
"name" : "id_1",
"ns" : "pulp_database.units_erratum",
"dropDups" : false
}
]

Ideas?