Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionBrad Buckingham
2011-07-13 13:38:29 UTC
Description of problem:
When attempting to Add Permission to a Role in the UI using an F14 development (git) install, we have observed fairly consistent segmentation faults from Ruby/Rails.
Version-Release number of selected component (if applicable):
git master
How reproducible:
fairly reproducable in F14... not observed with F15
Steps to Reproduce:
1. create a new role from UI (Administration -> Roles -> New Role)
2. select the role just created (opening the edit pane)
3. click 'Add Permission'
Actual results:
Ruby/Rails segmentation fault. We have observed the fault occuring in multiple places and below are several that we've seen. The first one is seen most frequently.
example 1:
/usr/lib/ruby/gems/1.8/gems/activesupport-3.0.5/lib/active_support/core_ext/module/remove_method.rb:3: [BUG] Segmentation fault
ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux]
example 2:
/usr/lib/ruby/gems/1.8/gems/activesupport-3.0.5/lib/active_support/core_ext/module/remove_method.rb:9: [BUG] Segmentation fault
ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux]
example 3:
/usr/lib/ruby/gems/1.8/gems/activerecord-3.0.5/lib/active_record/autosave_association.rb:163: [BUG] rb_gc_mark(): unknown data type 0x2b(0x51187a0) non object
ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux]
example 4:
/usr/lib/ruby/gems/1.8/gems/activesupport-3.0.5/lib/active_support/inflector/inflections.rb:151: [BUG] Segmentation fault
ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux]
example 5:
/usr/lib/ruby/gems/1.8/gems/activesupport-3.0.5/lib/active_support/core_ext/class/attribute.rb:73: [BUG] rb_gc_mark(): unknown data type 0x37(0x493e8e0) non object
ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux]
Expected results:
Form for adding a permission is displayed.
Additional info:
Based on some initial debugging, it appears that if the code below is omitted, the segmentation fault is no longer generated. This should be further investigated.
File: src/lib/util/model_util.rb
Code:
# explicitly load all available model classes
Dir.foreach("#{Rails.root}/app/models") { |f| require f if f =~ /.*\.[rR][bB]/ }
The code is for loading all the models, we need the list of all model classes for table name to class translation and vice versa.
The workaround is to change this line
Dir.foreach("#{Rails.root}/app/models") { |f| require f if f =~ /.*\.[rR][bB]/ }
to
require 'app/models/kp_environment'
...
... all the models for which users are allowed to create permissions
...
ade0f49 720991 - Segmentation Fault during Roles - Add Permission
@Brad - can you verify its gone for you? I was not able to reproduce on F15, but if you dont have F14 devsetup, I can provision a box for this one.
Description of problem: When attempting to Add Permission to a Role in the UI using an F14 development (git) install, we have observed fairly consistent segmentation faults from Ruby/Rails. Version-Release number of selected component (if applicable): git master How reproducible: fairly reproducable in F14... not observed with F15 Steps to Reproduce: 1. create a new role from UI (Administration -> Roles -> New Role) 2. select the role just created (opening the edit pane) 3. click 'Add Permission' Actual results: Ruby/Rails segmentation fault. We have observed the fault occuring in multiple places and below are several that we've seen. The first one is seen most frequently. example 1: /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.5/lib/active_support/core_ext/module/remove_method.rb:3: [BUG] Segmentation fault ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux] example 2: /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.5/lib/active_support/core_ext/module/remove_method.rb:9: [BUG] Segmentation fault ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux] example 3: /usr/lib/ruby/gems/1.8/gems/activerecord-3.0.5/lib/active_record/autosave_association.rb:163: [BUG] rb_gc_mark(): unknown data type 0x2b(0x51187a0) non object ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux] example 4: /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.5/lib/active_support/inflector/inflections.rb:151: [BUG] Segmentation fault ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux] example 5: /usr/lib/ruby/gems/1.8/gems/activesupport-3.0.5/lib/active_support/core_ext/class/attribute.rb:73: [BUG] rb_gc_mark(): unknown data type 0x37(0x493e8e0) non object ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux] Expected results: Form for adding a permission is displayed. Additional info: Based on some initial debugging, it appears that if the code below is omitted, the segmentation fault is no longer generated. This should be further investigated. File: src/lib/util/model_util.rb Code: # explicitly load all available model classes Dir.foreach("#{Rails.root}/app/models") { |f| require f if f =~ /.*\.[rR][bB]/ }