Bug 1389765 - running foreman-rake without options give index error.
Summary: running foreman-rake without options give index error.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Infrastructure
Version: 6.2.3
Hardware: x86_64
OS: Linux
low
low vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-28 14:11 UTC by Martijn ten Heuvel
Modified: 2021-09-09 11:59 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 17:57:16 UTC
Target Upstream Version:


Attachments (Terms of Use)
error and error + trace of foreman-rake command. (12.77 KB, text/plain)
2016-10-28 14:11 UTC, Martijn ten Heuvel
no flags Details

Description Martijn ten Heuvel 2016-10-28 14:11:30 UTC
Created attachment 1214997 [details]
error and error + trace of foreman-rake command.

Description of problem:
Running foreman-rake without options give nasty error pointing towards an index error:
# foreman-rake
rake aborted!
ArgumentError: Index name
'index_katello_repository_errata_on_erratum_id_and_repository_id' on table
'katello_repository_errata' is too long; the limit is 62 characters
/opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/connection_adapters/abstract/schema_statements.rb:797:in
`add_index_options'
/opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/connection_adapters/abstract/schema_statements.rb:536:in
`add_index'


Version-Release number of selected component (if applicable):


How reproducible:
Run command foreman-rake on rhel7, sat6.2.3 version.

Expected results:


Additional info:
See attachment.

Comment 1 Eric Helms 2016-10-28 14:23:12 UTC
This a misnomer but a valid issue given that when 'foreman-rake' is run without arguments the code does not set the environment to production properly and thus uses a sqlite adapter instead of postgres and throws the above index length error. Any use of 'foreman-rake' with an arugment (.e.g foreman-rake console) will not result in the above. That is, the index error isn't a real error, rather the error is in how the foreman-rake script handles no arguments being passed to it.

Comment 2 Eric Helms 2016-10-28 14:23:13 UTC
This a misnomer but a valid issue given that when 'foreman-rake' is run without arguments the code does not set the environment to production properly and thus uses a sqlite adapter instead of postgres and throws the above index length error. Any use of 'foreman-rake' with an arugment (.e.g foreman-rake console) will not result in the above. That is, the index error isn't a real error, rather the error is in how the foreman-rake script handles no arguments being passed to it.

Comment 5 Bryan Kearney 2018-09-04 17:57:16 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


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