Description of problem: Customer is trying to upgrade satellite 6.2.12 with command "# satellite-installer --scenario satellite --upgrade" and getting below error : Upgrade Step: db_seed... rake aborted! NoMethodError: undefined method `first' for nil:NilClass Seems to be there is an issue in bookmark related audit records. Observed below logs: /usr/share/foreman/db/seeds.d/15-bookmarks.rb:12:in `block (2 levels) in <top (required)>' /usr/share/foreman/db/seeds.d/15-bookmarks.rb:10:in `each' /usr/share/foreman/db/seeds.d/15-bookmarks.rb:10:in `block in <top (required)>' Seeding /usr/share/foreman/db/seeds.d/15-bookmarks.rb Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Satellite Upgrade ends with below error: Upgrade Step: db_seed... rake aborted! NoMethodError: undefined method `first' for nil:NilClass Expected results: Upgrade should be successful. Additional info:
(In reply to sandeep mutkule from comment #0) > Description of problem: Customer is trying to upgrade satellite 6.2.12 with > command "# satellite-installer --scenario satellite --upgrade" and getting > below error : > > Upgrade Step: db_seed... > rake aborted! > NoMethodError: undefined method `first' for nil:NilClass > > > Seems to be there is an issue in bookmark related audit records. > > Observed below logs: > > /usr/share/foreman/db/seeds.d/15-bookmarks.rb:12:in `block (2 levels) in > <top (required)>' > /usr/share/foreman/db/seeds.d/15-bookmarks.rb:10:in `each' > /usr/share/foreman/db/seeds.d/15-bookmarks.rb:10:in `block in <top > (required)>' > Seeding /usr/share/foreman/db/seeds.d/15-bookmarks.rb > > > Version-Release number of selected component (if applicable): > > > Actual results: > > Satellite Upgrade ends with below error: > > Upgrade Step: db_seed... > rake aborted! > NoMethodError: undefined method `first' for nil:NilClass > > > Expected results: Upgrade should be successful. > > > Additional info:
What releases are you upgrading from and to? (e.g. 6.2.11 to 6.2.12) Is the machine that is encountering this error available internally? Is the issue reproducable? Would it be possible to attach a foreman-debug?