Hide Forgot
Created attachment 1592612 [details] evm.log Description of problem: When trying to subscribe the CFME with WebUi in Setting -> RedHatUpdates, I am getting an error in the evm.log about username and password required. The CFME stays unregistered when checking on the WebUI as well as with subscribtion-manager. Version-Release number of selected component (if applicable): cfme-5.10.7.1-1.el7cf.x86_64 How reproducible: 2/2 Steps to Reproduce: 1. Navigate to Settings -> CFME Region "Region 0 [0]" -> Red Hat Updates. 2. Fill the username, password. 3. Verify 4. Save Actual results: Message: Customer Information successfully saved in the web ui. After a short while: [----] E, [2019-07-22T10:47:54.084062 #12174:1212f68] ERROR -- : MIQ(MiqQueue#deliver) Message id: [161], Error: [username and password are required] [----] E, [2019-07-22T10:47:54.084741 #12174:1212f68] ERROR -- : [ArgumentError]: username and password are required Method:[block (2 levels) in <class:LogProxy>] [----] E, [2019-07-22T10:47:54.085205 #12174:1212f68] ERROR -- : /opt/rh/cfme-gemset/gems/linux_admin-1.2.2/lib/linux_admin/registration_system/subscription_manager.rb:29:in `organizations' in the evm.log Expected results: system subscribed * the Update Status shows something like registered * subscription-manager status; echo $? returns 0 Additional info:
Note that I have reported also BZ#1731962 on CFME 5.11 today.
I have been tracing down to the 5.9.4.7 and even there it was not working and I got the same error message in the log
I re-discovered this bug when verifying BZ#1731962. I am copy-pasting my findings from that bug: When the credentials typed-in are valid, they are saved and I see a notification about that, but when I *change* the password afterwards, I am allowed to save without verifying. This results in green notification with info that creds were saved, but then in the logs I see: :guid: fe9f25af-d5fe-4c7a-a611-81fcb0eae88a [----] I, [2019-08-12T08:31:07.634353 #7870:2ad4d3d005c0] INFO -- : MIQ(MiqEventHandler::Runner#message_sync_config) MIQ(MiqEventHandler::Runner) Synchronizing configuration complete... [----] E, [2019-08-12T08:31:08.064750 #7905:2ad4d3d005c0] ERROR -- : MIQ(MiqQueue#deliver) Message id: [200], Error: [username and password are required] [----] E, [2019-08-12T08:31:08.065311 #7905:2ad4d3d005c0] ERROR -- : [ArgumentError]: username and password are required Method:[block (2 levels) in <class:LogProxy>] [----] E, [2019-08-12T08:31:08.065807 #7905:2ad4d3d005c0] ERROR -- : /opt/rh/cfme-gemset/gems/linux_admin-1.2.4/lib/linux_admin/registration_system/subscription_manager.rb:29:in `organizations' /opt/rh/cfme-gemset/gems/linux_admin-1.2.4/lib/linux_admin/registration_system/subscription_manager.rb:15:in `validate_credentials' /opt/rh/cfme-gemset/gems/linux_admin-1.2.4/lib/linux_admin/registration_system.rb:14:in `method_missing' /var/www/miq/vmdb/app/models/registration_system.rb:76:in `verify_credentials' /var/www/miq/vmdb/app/models/miq_queue.rb:460:in `block in dispatch_method' /usr/share/ruby/timeout.rb:93:in `block in timeout' /usr/share/ruby/timeout.rb:33:in `block in catch' /usr/share/ruby/timeout.rb:33:in `catch' /usr/share/ruby/timeout.rb:33:in `catch' /usr/share/ruby/timeout.rb:108:in `timeout' /var/www/miq/vmdb/app/models/miq_queue.rb:458:in `dispatch_method' /var/www/miq/vmdb/app/models/miq_queue.rb:435:in `block in deliver' /var/www/miq/vmdb/app/models/user.rb:290:in `with_user_group' /var/www/miq/vmdb/app/models/miq_queue.rb:435:in `deliver' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:104:in `deliver_queue_message' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:137:in `deliver_message' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:155:in `block in do_work' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:149:in `loop' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:149:in `do_work' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:329:in `block in do_work_loop' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:326:in `loop' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:326:in `do_work_loop' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:153:in `run' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:127:in `start' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:22:in `start_worker' /var/www/miq/vmdb/app/models/miq_worker.rb:398:in `block in start_runner_via_fork' /opt/rh/cfme-gemset/gems/nakayoshi_fork-0.0.4/lib/nakayoshi_fork.rb:23:in `fork' /opt/rh/cfme-gemset/gems/nakayoshi_fork-0.0.4/lib/nakayoshi_fork.rb:23:in `fork' /var/www/miq/vmdb/app/models/miq_worker.rb:396:in `start_runner_via_fork' /var/www/miq/vmdb/app/models/miq_worker.rb:386:in `start_runner' /var/www/miq/vmdb/app/models/miq_worker.rb:437:in `start' /var/www/miq/vmdb/app/models/miq_worker.rb:269:in `start_worker' /var/www/miq/vmdb/app/models/miq_worker.rb:147:in `block in sync_workers' /var/www/miq/vmdb/app/models/miq_worker.rb:147:in `times' /var/www/miq/vmdb/app/models/miq_worker.rb:147:in `sync_workers' /var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:54: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:154:in `start' /var/www/miq/vmdb/app/models/miq_server.rb:245:in `start' /var/www/miq/vmdb/lib/workers/evm_server.rb:27:in `start' /var/www/miq/vmdb/lib/workers/evm_server.rb:48:in `start' /var/www/miq/vmdb/lib/workers/bin/evm_server.rb:4:in `<main>' [----] I, [2019-08-12T08:31:08.066101 #7905:2ad4d3d005c0] INFO -- : MIQ(MiqQueue#delivered) Message id: [200], State: [error], Delivered in [0.652010474] seconds [----] I, [2019-08-12T08:31:08.068745 #7905:2ad4d3d005c0] INFO -- : MIQ(MiqQueue#m_callback) Message id: I am not sure what is the expected behaviour, but I don't think exception in the log is right in this case. I think user should not be allowed to save without verification.