Bug 1335150 - When RHEV 3.6 and OSE are on the same appliance RHEV breaks the collection of metrics
Summary: When RHEV 3.6 and OSE are on the same appliance RHEV breaks the collection of...
Keywords:
Status: CLOSED DUPLICATE of bug 1332579
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: C&U Capacity and Utilization
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.6.0
Assignee: Greg Blomquist
QA Contact: Nandini Chandra
URL:
Whiteboard: C&U:rhev:openstack
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-11 12:41 UTC by ldomb
Modified: 2016-08-30 22:07 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-17 18:53:05 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description ldomb 2016-05-11 12:41:31 UTC
Description of problem:
I have a cfme appliance which manages RHEV  and OSE 3.1. 

As soon as the RHEV provider gets added metrics stop flowing in. Meaning RHEV affects OSE metrics. 

Version-Release number of selected component (if applicable):
5.5.3.4.20160407153134_b3e2a83 CFME
3.6.3.4-0.1.el6 RHEV
3.1 OSE

How reproducible:
Have a appliance and attach it to OSE. Let metrics flow in and check evm.logs to see that the metrics are coming in. Add the RHEV provider. You will see  metrics stop working. 

Steps to Reproduce:
1. Add OSE 3.1 with metrics enabled
2. Let metrics from OSE flow in. Make sure you see the data coming in
3. Add a RHEV 3.6 provider 
4. Check the logs again as metrics will stop working
5. Remove the RHEV provider and metrics start working again

Actual results:

Metrics stop working. I see this in the logs but I think its related to an EC2 provider which tries to poll for metrics and has the wrong keys. 

[----] E, [2016-05-11T03:30:35.138334 #30826:fcb994] ERROR -- : MIQ(MiqQueue#deliver) Message id: [347000002262317], Error: [undefined method `state' for nil:NilClass]
[----] E, [2016-05-11T03:30:35.138564 #30826:fcb994] ERROR -- : [NoMethodError]: undefined method `state' for nil:NilClass  Method:[rescue in deliver]
[----] E, [2016-05-11T03:30:35.138724 #30826:fcb994] ERROR -- : /opt/rh/cfme-gemset/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/transaction.rb:196:in `rescue in ensure in within_
new_transaction'
/opt/rh/cfme-gemset/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/transaction.rb:193:in `ensure in within_new_transaction'
/opt/rh/cfme-gemset/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/transaction.rb:193:in `within_new_transaction'
/opt/rh/cfme-gemset/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction'
/opt/rh/cfme-gemset/gems/activerecord-4.2.6/lib/active_record/transactions.rb:220:in `transaction'
/opt/rh/cfme-gemset/gems/activerecord-4.2.6/lib/active_record/transactions.rb:348:in `with_transaction_returning_status'
/opt/rh/cfme-gemset/gems/activerecord-4.2.6/lib/active_record/persistence.rb:250:in `update'
/var/www/miq/vmdb/app/models/metric/ci_mixin/processing.rb:83:in `block (3 levels) in perf_process'
/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/processing.rb:83:in `block (2 levels) in perf_process'
/var/www/miq/vmdb/app/models/metric/ci_mixin/processing.rb:69:in `each'
/var/www/miq/vmdb/app/models/metric/ci_mixin/processing.rb:69:in `block in perf_process'
/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/processing.rb:14:in `perf_process'
/var/www/miq/vmdb/app/models/metric/ci_mixin/capture.rb:177:in `perf_capture'
/var/www/miq/vmdb/app/models/miq_queue.rb:345:in `block in deliver'
/opt/rh/rh-ruby22/root/usr/share/ruby/timeout.rb:89:in `block in timeout'
/opt/rh/rh-ruby22/root/usr/share/ruby/timeout.rb:34:in `block in catch'
/opt/rh/rh-ruby22/root/usr/share/ruby/timeout.rb:34:in `catch'
/opt/rh/rh-ruby22/root/usr/share/ruby/timeout.rb:34:in `catch'
/opt/rh/rh-ruby22/root/usr/share/ruby/timeout.rb:104:in `timeout'
/var/www/miq/vmdb/app/models/miq_queue.rb:341: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:151:in `block in do_work'
/var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:145:in `loop'
/var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:145: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:29:in `start_worker'
/var/www/miq/vmdb/lib/workers/bin/worker.rb:2:in `<top (required)>'
/opt/rh/cfme-gemset/gems/railties-4.2.6/lib/rails/commands/runner.rb:60:in `load'
/opt/rh/cfme-gemset/gems/railties-4.2.6/lib/rails/commands/runner.rb:60:in `<top (required)>'
/opt/rh/cfme-gemset/gems/railties-4.2.6/lib/rails/commands/commands_tasks.rb:123:in `require'
/opt/rh/cfme-gemset/gems/railties-4.2.6/lib/rails/commands/commands_tasks.rb:123:in `require_command!'
/opt/rh/cfme-gemset/gems/railties-4.2.6/lib/rails/commands/commands_tasks.rb:90:in `runner'
/opt/rh/cfme-gemset/gems/railties-4.2.6/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
/opt/rh/cfme-gemset/gems/railties-4.2.6/lib/rails/commands.rb:17:in `<top (required)>'
/var/www/miq/vmdb/bin/rails:4:in `require'
/var/www/miq/vmdb/bin/rails:4:in `<main>'

Expected results:
Metrics should work

Additional info:

Comment 2 Juan Hernández 2016-05-12 11:31:50 UTC
That error looks like a timeout when connecting to the OSE metrics service, which causes rollback of a transaction that doesn't exist.

When you say that OSE metrics "flow in" what do you mean exactly? How are you checking that? In the log? Can you share the log messages that you see when the RHEV provider isn't configured and that you don't see when it is configured?

Comment 3 ldomb 2016-05-12 13:25:04 UTC
Juan, 

I have one appliance where I am running all the providers. It seems that it can handle VMWare Ec2 Azure and OpenStack, but if I add RHEV as well I am running into C/U collection issues. I think that might be rather a performance issue  issue than rhev itself (I know that I should split up the providers so its not an optimal setup). I added again the rhev provider this morning. This is what I see. First 

....

[----] I, [2016-05-12T08:45:02.288416 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 4 realtime metrics.
[----] I, [2016-05-12T08:45:02.292573 #2845:823994]  INFO -- : MIQ(MiqServer#populate_queue_messages) Fetched 7 miq_queue rows for queue_name=redhat, wcount=2, priority=200
[----] I, [2016-05-12T08:45:02.294013 #2845:823994]  INFO -- : MIQ(MiqServer#monitor_loop) Server Monitoring Complete - Timings: {:server_dequeue=>0.0031821727752685547, :server_monitor=>0.09629964828491211, :worker_monitor=>1.566796064376831, :worker_dequeue=>0.025244951248168945, :total_time=>1.6918208599090576}
[----] I, [2016-05-12T08:45:02.318688 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 9 realtime metrics.
[----] I, [2016-05-12T08:45:02.348869 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 8 realtime metrics.
[----] I, [2016-05-12T08:45:02.381805 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 9 realtime metrics.
[----] I, [2016-05-12T08:45:02.414838 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 10 realtime metrics.
[----] I, [2016-05-12T08:45:02.464964 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 16 realtime metrics.
[----] I, [2016-05-12T08:45:02.507637 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 9 realtime metrics.
[----] I, [2016-05-12T08:45:02.540080 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 10 realtime metrics.
[----] I, [2016-05-12T08:45:02.569496 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 7 realtime metrics.
[----] I, [2016-05-12T08:45:02.602491 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 10 realtime metrics.
[----] I, [2016-05-12T08:45:02.632700 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 9 realtime metrics.
[----] I, [2016-05-12T08:45:02.660633 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 7 realtime metrics.
[----] I, [2016-05-12T08:45:02.692552 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 6 realtime metrics.
[----] I, [2016-05-12T08:45:02.722685 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 8 realtime metrics.
[----] I, [2016-05-12T08:45:02.751127 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 7 realtime metrics.
[----] I, [2016-05-12T08:45:02.783281 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 11 realtime metrics.
[----] I, [2016-05-12T08:45:02.813234 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 6 realtime metrics.
[----] I, [2016-05-12T08:45:02.852807 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 10 realtime metrics.
[----] I, [2016-05-12T08:45:02.885515 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 8 realtime metrics.
[----] I, [2016-05-12T08:45:02.921543 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 9 realtime metrics.
[----] I, [2016-05-12T08:45:02.960251 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 10 realtime metrics.
[----] I, [2016-05-12T08:45:03.004661 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 11 realtime metrics.
[----] I, [2016-05-12T08:45:03.042772 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 9 realtime metrics.
[----] I, [2016-05-12T08:45:03.082411 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 13 realtime metrics.
[----] I, [2016-05-12T08:45:03.114660 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 7 realtime metrics.
[----] I, [2016-05-12T08:45:03.164359 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 13 realtime metrics.
[----] I, [2016-05-12T08:45:03.204771 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 14 realtime metrics.
[----] I, [2016-05-12T08:45:03.235112 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 7 realtime metrics.
[----] I, [2016-05-12T08:45:03.263876 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 6 realtime metrics.
[----] I, [2016-05-12T08:45:03.297289 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 9 realtime metrics.
[----] I, [2016-05-12T08:45:03.334396 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 9 realtime metrics.
[----] I, [2016-05-12T08:45:03.372586 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 11 realtime metrics.
[----] I, [2016-05-12T08:45:03.407799 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 9 realtime metrics.
[----] I, [2016-05-12T08:45:03.436285 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 8 realtime metrics.
[----] I, [2016-05-12T08:45:03.473486 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 9 realtime metrics.
[----] I, [2016-05-12T08:45:03.511209 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 10 realtime metrics.
[----] I, [2016-05-12T08:45:03.549125 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 11 realtime metrics.
[----] I, [2016-05-12T08:45:03.591726 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 10 realtime metrics.
[----] I, [2016-05-12T08:45:03.626586 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 7 realtime metrics.
[----] I, [2016-05-12T08:45:03.663896 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 8 realtime metrics.
[----] I, [2016-05-12T08:45:03.701584 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 8 realtime metrics.
[----] I, [2016-05-12T08:45:03.733681 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 9 realtime metrics.
[----] I, [2016-05-12T08:45:03.763061 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 6 realtime metrics.
[----] I, [2016-05-12T08:45:03.801048 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging 7 realtime metrics.
[----] I, [2016-05-12T08:45:03.824871 #3036:5af988]  INFO -- : MIQ(Metric::Purging.purge) Purging all realtime metrics older than [2016-05-12 08:39:53 UTC]...Complete - Deleted 222593 records and 0 associated tag values - Timings: {:query_oldest=>0.07824206352233887, :query_batch=>0.8838052749633789, :purge_metrics=>77.26498126983643, :total_time=>302.8659827709198}

Than a few minutes later

Target id: [], Instance id: [347000000000017], Task id: [], Command: [ManageIQ::Providers::Redhat::InfraManager::Host.perf_capture], Timeout: [600], Priority: [100], State: [ready], Deliver On: [], Data: [], Args: ["realtime"], Requeued
[----] E, [2016-05-12T08:45:44.159101 #3084:47d998] ERROR -- : MIQ(MiqQueue#deliver) Message id: [347000002316870], Error: [undefined method `metrics_collector_queue_name' for nil:NilClass]
[----] E, [2016-05-12T08:45:44.161631 #3084:47d998] ERROR -- : [NoMethodError]: undefined method `metrics_collector_queue_name' for nil:NilClass  Method:[rescue in deliver]
[----] E, [2016-05-12T08:45:44.161811 #3084:47d998] ERROR -- : /var/www/miq/vmdb/app/models/metric/ci_mixin/capture.rb:19:in `queue_name_for_metrics_collection'
/var/www/miq/vmdb/app/models/metric/ci_mixin/capture.rb:69:in `perf_capture_queue'
/var/www/miq/vmdb/app/models/metric/capture.rb:127:in `block in perf_capture_timer'
/var/www/miq/vmdb/app/models/metric/capture.rb:112:in `each'
/var/www/miq/vmdb/app/models/metric/capture.rb:112:in `perf_capture_timer'
/var/www/miq/vmdb/app/models/miq_queue.rb:345:in `block in deliver'
/opt/rh/rh-ruby22/root/usr/share/ruby/timeout.rb:89:in `block in timeout'
/opt/rh/rh-ruby22/root/usr/share/ruby/timeout.rb:34:in `block in catch'
/opt/rh/rh-ruby22/root/usr/share/ruby/timeout.rb:34:in `catch'
/opt/rh/rh-ruby22/root/usr/share/ruby/timeout.rb:34:in `catch'
/opt/rh/rh-ruby22/root/usr/share/ruby/timeout.rb:104:in `timeout'
/var/www/miq/vmdb/app/models/miq_queue.rb:341: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:151:in `block in do_work'
/var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:145:in `loop'
/var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:145: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:29:in `start_worker'
/var/www/miq/vmdb/lib/workers/bin/worker.rb:2:in `<top (required)>'
/opt/rh/cfme-gemset/gems/railties-4.2.6/lib/rails/commands/runner.rb:60:in `load'
/opt/rh/cfme-gemset/gems/railties-4.2.6/lib/rails/commands/runner.rb:60:in `<top (required)>'
/opt/rh/cfme-gemset/gems/railties-4.2.6/lib/rails/commands/commands_tasks.rb:123:in `require'
/opt/rh/cfme-gemset/gems/railties-4.2.6/lib/rails/commands/commands_tasks.rb:123:in `require_command!'
/opt/rh/cfme-gemset/gems/railties-4.2.6/lib/rails/commands/commands_tasks.rb:90:in `runner'
/opt/rh/cfme-gemset/gems/railties-4.2.6/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
/opt/rh/cfme-gemset/gems/railties-4.2.6/lib/rails/commands.rb:17:in `<top (required)>'
/var/www/miq/vmdb/bin/rails:4:in `require'
/var/www/miq/vmdb/bin/rails:4:in `<main>'
[----] I, [2016-05-12T08:45:44.162274 #3084:47d998]  INFO -- : MIQ(MiqQueue#delivered) Message id: [347000002316870], State: [error], Delivered in [3.255732357] seconds
[----] I, [2016-05-12T08:45:45.117533 #2845:823994]  INFO -- : MIQ(MiqServer#populate_queue_messages) Fetched 7 miq_queue rows for queue_name=redhat, wcount=2, priority=200

It also is still purging realtime data. 

The above error repeats itself every 4-5 minutes until I remove the rhev provider.

Comment 4 Juan Hernández 2016-05-12 17:49:28 UTC
OK, that errors gives some more information. If I understand correctly the requests for metrics collection are queued in a loop, and this is the same loop for all the providers. Once the request is queued correctly, it will be later de-queued (by a different worker), and executed. If you have two providers, "redhat" and "openshift", and they are queued in that order, then if the "redhat" queuing fails, the "openshift" queuing won't happen, because the loop will be aborted. This is apparently what is happening according to the trace in the previous comment. If this is correct (and I'm not 100% sure about that) then we still need to know why the queuing is failing. Are you sure you setup correctly the credentials for the RHEV-M "C & U"? Can you try to capture the traffic between the CFME appliance and the RHEV-M engine in port 5432? That is the port used by the PostgreSQL database, as in RHEV-M metric collection goes directly to the database.

Comment 5 ldomb 2016-05-17 13:12:48 UTC
Here is the validation traffic from cfme to rhev postrgresql 

[root@cfmeldo1 ~]# tcpdump -n "dst host 10.11.165.94 and port 5432"
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
09:10:34.045008 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [S], seq 608666180, win 29200, options [mss 1460,sackOK,TS val 2224815581 ecr 0,nop,wscale 7], length 0
09:10:34.045477 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [.], ack 652145670, win 229, options [nop,nop,TS val 2224815582 ecr 2307300723], length 0
09:10:34.045670 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [P.], seq 0:8, ack 1, win 229, options [nop,nop,TS val 2224815582 ecr 2307300723], length 8
09:10:34.046648 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [.], ack 2, win 229, options [nop,nop,TS val 2224815583 ecr 2307300725], length 0
09:10:34.046801 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [P.], seq 8:102, ack 2, win 229, options [nop,nop,TS val 2224815583 ecr 2307300725], length 94
09:10:34.047373 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [P.], seq 102:143, ack 15, win 229, options [nop,nop,TS val 2224815584 ecr 2307300725], length 41
09:10:34.049384 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [P.], seq 143:178, ack 315, win 237, options [nop,nop,TS val 2224815586 ecr 2307300727], length 35
09:10:34.050070 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [P.], seq 178:220, ack 356, win 237, options [nop,nop,TS val 2224815586 ecr 2307300728], length 42
09:10:34.050751 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [P.], seq 220:262, ack 371, win 237, options [nop,nop,TS val 2224815587 ecr 2307300729], length 42
09:10:34.051355 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [P.], seq 262:287, ack 422, win 237, options [nop,nop,TS val 2224815588 ecr 2307300729], length 25
09:10:34.052506 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [P.], seq 287:1041, ack 455, win 237, options [nop,nop,TS val 2224815589 ecr 2307300730], length 754
09:10:34.056183 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [.], ack 8647, win 365, options [nop,nop,TS val 2224815593 ecr 2307300734], length 0
09:10:34.056590 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [.], ack 14439, win 455, options [nop,nop,TS val 2224815593 ecr 2307300735], length 0
09:10:34.056625 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [.], ack 16839, win 493, options [nop,nop,TS val 2224815593 ecr 2307300735], length 0
09:10:34.056964 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [.], ack 25031, win 621, options [nop,nop,TS val 2224815593 ecr 2307300735], length 0
09:10:34.057305 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [.], ack 27927, win 666, options [nop,nop,TS val 2224815594 ecr 2307300735], length 0
09:10:34.057340 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [.], ack 33223, win 749, options [nop,nop,TS val 2224815594 ecr 2307300735], length 0
09:10:34.057741 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [.], ack 41415, win 877, options [nop,nop,TS val 2224815594 ecr 2307300736], length 0
09:10:34.057878 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [.], ack 43165, win 904, options [nop,nop,TS val 2224815594 ecr 2307300736], length 0
09:10:34.061882 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [P.], seq 1041:1061, ack 43165, win 904, options [nop,nop,TS val 2224815598 ecr 2307300736], length 20
09:10:34.062550 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [P.], seq 1061:1075, ack 43229, win 904, options [nop,nop,TS val 2224815599 ecr 2307300740], length 14
09:10:34.063219 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [P.], seq 1075:1089, ack 43293, win 904, options [nop,nop,TS val 2224815600 ecr 2307300741], length 14
09:10:34.063865 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [P.], seq 1089:1094, ack 43357, win 904, options [nop,nop,TS val 2224815600 ecr 2307300742], length 5
09:10:34.063883 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [F.], seq 1094, ack 43357, win 904, options [nop,nop,TS val 2224815600 ecr 2307300742], length 0
09:10:34.065174 IP 10.11.165.93.41023 > 10.11.165.94.postgres: Flags [.], ack 43358, win 904, options [nop,nop,TS val 2224815602 ecr 2307300743], length 0

Which is validated successful. I am also getting RHEV-M utilization metrics

Comment 7 Juan Hernández 2016-05-17 18:43:05 UTC
Keenan, may be the same than bug 1332579 ?

Comment 8 Keenan Brock 2016-05-17 18:53:05 UTC
Juan,

thanks. yes, same thing. It is in master and darga

*** This bug has been marked as a duplicate of bug 1332579 ***


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