Bug #10523: katello fails when content host registers with a release version or uploading facts - Katello - Foreman

Actions

Copy link

Bug #10523

closed

katello fails when content host registers with a release version or uploading facts

Added by Justin Sherrill almost 10 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Justin Sherrill

Category:

Web UI

Target version:

Katello 2.2.1

Difficulty:

Triaged:

Yes

Bugzilla link:

1222089

Pull request:

https://github.com/Katello/katello/pull/5230

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1222089
Description of problem:
Satellite fails when content host registers with a release version

Version-Release number of selected component (if applicable):
Sat 6.1 GA Snap 4 Compose 2

How reproducible:
Always

Steps to Reproduce:
1. Syncing rhel 6.6 server.
2. Attempt to register a rhel 6.6 content host with release version:

subscription-manager register --org="testorg" --activationkey="actkey1" --release 6.6 --force

Actual results:
Content host registration completed but with a big stacktrace failing to update the system facts (see attached production.log)

Further, content host errata information is not showing in the satellite UI

Expected results:
- Content host registration works with no stacktrace
- Content host errata information should be shown in Satellite UI

Additional info:

Actions

Copy link

Updated by Justin Sherrill almost 10 years ago

Subject changed from Satellite fails when content host registers with a release version or uploading facts to katello fails when content host registers with a release version or uploading facts
Assignee set to Justin Sherrill
Translation missing: en.field_release set to 51
Triaged changed from No to Yes

Actions

Copy link

Updated by The Foreman Bot almost 10 years ago

Status changed from New to Ready For Testing
Pull request https://github.com/Katello/katello/pull/5230 added
Pull request deleted ()

Actions

Copy link

Updated by Justin Sherrill almost 10 years ago

Simply running:

subscription-manager facts --update

will reproduce the error. The client will always say it uploaded successfully, check the server logs and you will see the error.

Actions

Copy link

Updated by Justin Sherrill almost 10 years ago

traceback:

2015-05-15 17:00:20 [D] ExecutionPlan b38ae409-7983-45f9-a5ae-48401ecb2996      pending >>  planning
2015-05-15 17:00:21 [E] Error on on_execution_plan_save event
2015-05-15 17:00:21 [E] Validation failed: Resource can't be blank
2015-05-15 17:00:21 [E] /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activerecord-3.2.8/lib/active_record/validations.rb:56:in `save!'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activerecord-3.2.8/lib/active_record/attribute_methods/dirty.rb:33:in `save!'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activerecord-3.2.8/lib/active_record/transactions.rb:246:in `block in save!'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activerecord-3.2.8/lib/active_record/transactions.rb:295:in `block in with_transaction_returning_status'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/database_statements.rb:192:in `transaction'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activerecord-3.2.8/lib/active_record/transactions.rb:208:in `transaction'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activerecord-3.2.8/lib/active_record/transactions.rb:293:in `with_transaction_returning_status'
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/activerecord-3.2.8/lib/active_record/transactions.rb:246:in `save!'
/home/vagrant/git/foreman-tasks/app/models/foreman_tasks/lock.rb:131:in `owner!'
/home/vagrant/git/foreman-tasks/lib/foreman_tasks/dynflow/persistence.rb:27:in `on_execution_plan_save'
/home/vagrant/git/foreman-tasks/lib/foreman_tasks/dynflow/persistence.rb:12:in `block in save_execution_plan'
/home/vagrant/git/foreman-tasks/lib/foreman_tasks/dynflow/persistence.rb:10:in `tap'
/home/vagrant/git/foreman-tasks/lib/foreman_tasks/dynflow/persistence.rb:10:in `save_execution_plan'
/home/vagrant/git/dynflow/lib/dynflow/persistence.rb:47:in `save_execution_plan'
/home/vagrant/git/dynflow/lib/dynflow/execution_plan.rb:281:in `save'
/home/vagrant/git/dynflow/lib/dynflow/execution_plan.rb:80:in `update_state'
/home/vagrant/git/dynflow/lib/dynflow/execution_plan.rb:162:in `plan'
/home/vagrant/git/dynflow/lib/dynflow/world.rb:129:in `block in plan'
/home/vagrant/git/dynflow/lib/dynflow/world.rb:127:in `tap'
/home/vagrant/git/dynflow/lib/dynflow/world.rb:127:in `plan'
/home/vagrant/git/dynflow/lib/dynflow/world.rb:100:in `trigger'
/home/vagrant/git/foreman-tasks/lib/foreman_tasks.rb:17:in `trigger'
/home/vagrant/git/foreman-tasks/lib/foreman_tasks.rb:23:in `trigger_task'
/home/vagrant/git/foreman-tasks/lib/foreman_tasks.rb:39:in `sync_task'
/home/vagrant/git/foreman-tasks/lib/foreman_tasks/triggers.rb:22:in `sync_task'

Actions

Copy link