Bug 1394055 - RHEVM C&U Invalid Host doesn't display Error in Web UI
Summary: RHEVM C&U Invalid Host doesn't display Error in Web UI
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.7.1
Assignee: Chris Arcand
QA Contact: Ilanit Stein
URL:
Whiteboard: rhev:c&u
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-10 22:25 UTC by myoder
Modified: 2017-03-21 09:38 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-18 16:39:42 UTC
Category: Bug
Cloudforms Team: RHEVM
Target Upstream Version:


Attachments (Terms of Use)

Description myoder 2016-11-10 22:25:02 UTC
Description of problem: When validating C&U for a RHEV provider, when the hostname is incorrect the UI hangs until the connection times out.  After connection times out no message is displayed to the web UI.


Version-Release number of selected component (if applicable):
CFME 5.7.0.10-beta3.20161109111947_9a61b18

How reproducible:
Always

Steps to Reproduce:
1. Add RHEV Provider
2. Validate C&U with invalid hostname
3.

Actual results: UI hangs until connection times out, and does not display error message to the user.


Expected results: The UI should display an error message to the user.


Additional info:

Comment 3 Ilanit Stein 2016-11-22 07:47:35 UTC
Managed to reproduce on CFME-5.7.0.11 & RHV-4.0.5.

In hostname field, I entered a wrong IP address.
when entering a wrong FQDN, if fails instantly, and give error in the UI 
"Credential validation was not successful: could bot translate host name "istein-rhv40" to address: Name or service not known"

In evm.log error on no metrics credentials defined:
[----] E, [2016-11-22T02:37:24.138730 #4229:8eb138] ERROR -- : MIQ(ManageIQ::Providers::Redhat::InfraManager::MetricsCapture#perf_collect_metrics) [realtime] for: [ManageIQ::Providers::Redhat::InfraManager::Vm], [500], [vm_prov_from_cfme_1] Unhandled exception during perf data collection: [no metrics credentials defined], class: [RuntimeError]
[----] E, [2016-11-22T02:37:24.138865 #4229:8eb138] ERROR -- : MIQ(ManageIQ::Providers::Redhat::InfraManager::MetricsCapture#perf_collect_metrics) [realtime] for: [ManageIQ::Providers::Redhat::InfraManager::Vm], [500], [vm_prov_from_cfme_1]   Timings at time of error: {:server_dequeue=>0.002027750015258789, :server_monitor=>0.05881381034851074, :capture_state=>1.9621622562408447, :rhevm_connect=>0.05370020866394043, :total_time=>3.3707308769226074, :db_find_storage_files=>0.034336090087890625, :init_attrs=>0.008500099182128906, :db_find_prev_perfs=>0.03811001777648926, :process_perfs=>1.1021857261657715, :process_perfs_tag=>0.004864931106567383, :process_bottleneck=>0.12062454223632812}
[----] E, [2016-11-22T02:37:24.138991 #4229:8eb138] ERROR -- : [RuntimeError]: no metrics credentials defined  Method:[rescue in perf_collect_metrics]
[----] E, [2016-11-22T02:37:24.139115 #4229:8eb138] ERROR -- : /var/www/miq/vmdb/app/models/manageiq/providers/redhat/infra_manager/metrics_capture.rb:7:in `perf_init_rhevm'
/var/www/miq/vmdb/app/models/manageiq/providers/redhat/infra_manager/metrics_capture.rb:39:in `block in perf_collect_metrics'
/var/www/miq/vmdb/gems/pending/util/extensions/miq-benchmark.rb:11:in `realtime_store'
/var/www/miq/vmdb/gems/pending/util/extensions/miq-benchmark.rb:30:in `realtime_block'
/var/www/miq/vmdb/app/models/manageiq/providers/redhat/infra_manager/metrics_capture.rb:39:in `perf_collect_metrics'
/var/www/miq/vmdb/app/models/metric/ci_mixin/capture.rb:6:in `perf_collect_metrics'
/var/www/miq/vmdb/app/models/metric/ci_mixin/capture.rb:157:in `block in perf_capture'
/var/www/miq/vmdb/gems/pending/util/extensions/miq-benchmark.rb:11:in `realtime_store'
/var/www/miq/vmdb/gems/pending/util/extensions/miq-benchmark.rb:30:in `realtime_block'
/var/www/miq/vmdb/app/models/metric/ci_mixin/capture.rb:154:in `perf_capture'
/var/www/miq/vmdb/app/models/metric/ci_mixin/capture.rb:94:in `perf_capture_realtime'
/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:106:in `deliver_queue_message'
/var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:134:in `deliver_message'
/var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:152:in `block in do_work'
/var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:146:in `loop'
/var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:146:in `do_work'
/var/www/miq/vmdb/app/models/miq_worker/runner.rb:334:in `block in do_work_loop'
/var/www/miq/vmdb/app/models/miq_worker/runner.rb:331:in `loop'
/var/www/miq/vmdb/app/models/miq_worker/runner.rb:331: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:128: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:343:in `block in start'
/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:341:in `start'
/var/www/miq/vmdb/app/models/miq_worker.rb:270: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:52: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/worker_management/monitor.rb:22:in `monitor_workers'
/var/www/miq/vmdb/app/models/miq_server.rb:345:in `block in monitor'
/var/www/miq/vmdb/gems/pending/util/extensions/miq-benchmark.rb:11:in `realtime_store'
/var/www/miq/vmdb/gems/pending/util/extensions/miq-benchmark.rb:30:in `realtime_block'
/var/www/miq/vmdb/app/models/miq_server.rb:345:in `monitor'
/var/www/miq/vmdb/app/models/miq_server.rb:367:in `block (2 levels) in monitor_loop'
/var/www/miq/vmdb/gems/pending/util/extensions/miq-benchmark.rb:11:in `realtime_store'
/var/www/miq/vmdb/gems/pending/util/extensions/miq-benchmark.rb:30:in `realtime_block'
/var/www/miq/vmdb/app/models/miq_server.rb:367:in `block in monitor_loop'
/var/www/miq/vmdb/app/models/miq_server.rb:366:in `loop'
/var/www/miq/vmdb/app/models/miq_server.rb:366:in `monitor_loop'
/var/www/miq/vmdb/app/models/miq_server.rb:249:in `start'
/var/www/miq/vmdb/lib/workers/evm_server.rb:65:in `start'
/var/www/miq/vmdb/lib/workers/evm_server.rb:92:in `start'
/var/www/miq/vmdb/lib/workers/bin/evm_server.rb:4:in `<main>'
[----] E, [2016-11-22T02:37:24.139253 #4229:8eb138] ERROR -- : MIQ(MiqQueue#deliver) Message id: [455021], Error: [no metrics credentials defined]
[----] E, [2016-11-22T02:37:24.139376 #4229:8eb138] ERROR -- : [RuntimeError]: no metrics credentials defined  Method:[rescue in deliver]
[----] E, [2016-11-22T02:37:24.139430 #4229:8eb138] ERROR -- : /var/www/miq/vmdb/app/models/manageiq/providers/redhat/infra_manager/metrics_capture.rb:7:in `perf_init_rhevm'

Comment 4 Ilanit Stein 2016-11-22 08:56:21 UTC
Adding clarification to comment #3:

Problem occurred only when entering wrong IP address.


When entering some wrong fqdn, there is instant error in the UI.

The error from the log I mentioned, refer to the case a wrong IP address is entered, while in UI spinner rotates, and eventually do not show any error.

Comment 6 Oved Ourfali 2017-01-04 07:26:32 UTC
Hi Chris.
Will this get in to 5.7.1?

Comment 7 Chris Arcand 2017-01-05 18:29:38 UTC
This should already be fixed, IIRC. Should be a dupe of this: https://bugzilla.redhat.com/show_bug.cgi?id=1393032

Can you confirm this is still an issue?

Comment 8 Oved Ourfali 2017-01-07 08:52:23 UTC
Ilanit - can you re-test?

Comment 9 Ilanit Stein 2017-01-08 07:38:21 UTC
This is still issue on 5.7.0.17/RHV-4.0.5 (CF-4.2 GA version).

When validating C&U for a RHV provider, 
when the hostname is a wrong IP address,
UI hangs until the connection times out.  
After connection times out no message is displayed to the web UI.
and in evm.log,
there is the same error mentioned in comment #3

Comment 10 Oved Ourfali 2017-01-09 11:03:52 UTC
Chris - can you take a look?

Comment 11 Chris Arcand 2017-01-11 17:24:36 UTC
I have tested this and do not see any issue. The prompt correctly returns the right message when the hostname (either via DNS or direct IP) is correct and instantly when it's incorrect. Can't reproduce.

Comment 13 myoder 2017-01-18 15:07:53 UTC
Hey Chris,

This was probably just an error in the beta version and has been taken care of.  You can close this ticket as you are unable to reproduce this issue.

Thanks,
Michael


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