Bug 1461716 - Unable to register with RHSM after unregistering from sat6
Unable to register with RHSM after unregistering from sat6
Status: NEW
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance (Show other bugs)
5.8.0
Unspecified Unspecified
medium Severity medium
: GA
: cfme-future
Assigned To: Gregg Tanzillo
luke couzens
black:webui
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-15 05:20 EDT by luke couzens
Modified: 2017-06-20 11:46 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description luke couzens 2017-06-15 05:20:33 EDT
Description of problem:Unable to register with RHSM after unregistering from sat6


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


How reproducible:100%


Steps to Reproduce:
1.provision appliance
2.navigate to configuration-settings-region-Red Hat Updates
3.edit registration adding sat6 settings
4.register with sat6
5.wait for registration to complete
6.ssh to appliance
7.run the following to unregister appliance
8.subscription-manager remove --all
9.subscription-manager unregister
10.subscription-manager clean
11.mv -f /etc/rhsm/rhsm.conf.kat-backup /etc/rhsm/rhsm.conf
12.rpm -qa | grep katello-ca-consumer | xargs rpm -e
13.navigate back to configuration-settings-region-Red Hat Updates
14.edit registration using RHSM settings
15.Try registering with RHSM

Actual results: Nothing shown in the UI

Evm.log as follows:

[----] I, [2017-06-15T05:10:32.767980 #12024:41b130]  INFO -- : MIQ(MiqServer#register) Registering appliance...
[----] E, [2017-06-15T05:10:36.695427 #12024:41b130] ERROR -- : AwesomeSpawn: subscription-manager register exit code: 70
[----] E, [2017-06-15T05:10:36.695699 #12024:41b130] ERROR -- : AwesomeSpawn: Organization Default_Organization does not exist.

[----] E, [2017-06-15T05:10:36.696701 #12024:41b130] ERROR -- : MIQ(MiqQueue#deliver) Message id: [3797], Error: [subscription-manager register exit code: 70]
[----] E, [2017-06-15T05:10:36.697199 #12024:41b130] ERROR -- : [AwesomeSpawn::CommandResultError]: subscription-manager register exit code: 70  Method:[rescue in deliver]
[----] E, [2017-06-15T05:10:36.697391 #12024:41b130] ERROR -- : /opt/rh/cfme-gemset/gems/awesome_spawn-1.4.1/lib/awesome_spawn.rb:105:in `run!'
/opt/rh/cfme-gemset/gems/linux_admin-0.20.1/lib/linux_admin/common.rb:24:in `run!'
/opt/rh/cfme-gemset/gems/linux_admin-0.20.1/lib/linux_admin/registration_system/subscription_manager.rb:6:in `run!'
/opt/rh/cfme-gemset/gems/linux_admin-0.20.1/lib/linux_admin/registration_system/subscription_manager.rb:52:in `register'
/opt/rh/cfme-gemset/gems/linux_admin-0.20.1/lib/linux_admin/registration_system.rb:14:in `method_missing'
/var/www/miq/vmdb/app/models/miq_server/update_management.rb:82:in `register'
/var/www/miq/vmdb/app/models/miq_server/update_management.rb:61:in `attempt_registration'
/var/www/miq/vmdb/app/models/miq_server/update_management.rb:55:in `update_registration_status'
/var/www/miq/vmdb/app/models/miq_queue.rb:347:in `block in deliver'
/opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:91:in `block in timeout'
/opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:33:in `block in catch'
/opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:33:in `catch'
/opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:33:in `catch'
/opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:106:in `timeout'
/var/www/miq/vmdb/app/models/miq_queue.rb:343:in `deliver'
/var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:107:in `deliver_queue_message'
/var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:135:in `deliver_message'
/var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:153:in `block in do_work'
/var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:147:in `loop'
/var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:147:in `do_work'
/var/www/miq/vmdb/app/models/miq_worker/runner.rb:336:in `block in do_work_loop'
/var/www/miq/vmdb/app/models/miq_worker/runner.rb:333:in `loop'
/var/www/miq/vmdb/app/models/miq_worker/runner.rb:333:in `do_work_loop'
/var/www/miq/vmdb/app/models/miq_worker/runner.rb:155:in `run'
/var/www/miq/vmdb/app/models/miq_worker/runner.rb:130:in `start'
/var/www/miq/vmdb/app/models/miq_worker/runner.rb:21:in `start_worker'
/var/www/miq/vmdb/app/models/miq_worker.rb:339:in `block in start_runner'
/opt/rh/cfme-gemset/gems/nakayoshi_fork-0.0.3/lib/nakayoshi_fork.rb:24:in `fork'
/opt/rh/cfme-gemset/gems/nakayoshi_fork-0.0.3/lib/nakayoshi_fork.rb:24:in `fork'
/var/www/miq/vmdb/app/models/miq_worker.rb:337:in `start_runner'
/var/www/miq/vmdb/app/models/miq_worker.rb:348:in `start'
/var/www/miq/vmdb/app/models/miq_worker.rb:266:in `start_worker'
/var/www/miq/vmdb/app/models/miq_worker.rb:150:in `block in sync_workers'
/var/www/miq/vmdb/app/models/miq_worker.rb:150:in `times'
/var/www/miq/vmdb/app/models/miq_worker.rb:150:in `sync_workers'
/var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:53:in `block in sync_workers'
/var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:50:in `each'
/var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:50:in `sync_workers'
/var/www/miq/vmdb/app/models/miq_server.rb:160:in `start'
/var/www/miq/vmdb/app/models/miq_server.rb:251:in `start'
/var/www/miq/vmdb/lib/workers/evm_server.rb:65:in `start'
/var/www/miq/vmdb/lib/workers/evm_server.rb:91:in `start'
/var/www/miq/vmdb/lib/workers/bin/evm_server.rb:4:in `<main>'
[----] I, [2017-06-15T05:10:36.697692 #12024:41b130]  INFO -- : MIQ(MiqQueue#delivered) Message id: [3797], State: [error], Delivered in [4.451105042] seconds
[----] I, [2017-06-15T05:10:45.428108 #12051:41b130]  INFO -- : MIQ(MiqScheduleWorker::Runner#do_work) Number of scheduled items to be processed: 5.


Expected results: Registration completes successfully


Additional info:
It seems like the org name is causing the issue but there is no way in the UI to change this, once you validate sat6 credentials the org name is pulled from the server and there is no way to clear it unless I am missing something.

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