Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/

Bug 1093357

Summary: neutron agent-list report different status each click
Product: [Community] RDO Reporter: Ofer Blaut <oblaut>
Component: openstack-neutronAssignee: RHOS Maint <rhos-maint>
Status: CLOSED WORKSFORME QA Contact: Ofer Blaut <oblaut>
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: amuller, chrisw, lpeer, oblaut, twilson, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-22 15:05:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
CLI logs
none
logs from files none

Description Ofer Blaut 2014-05-01 14:08:26 UTC
Created attachment 891537 [details]
CLI logs

Description of problem:


When running neutron agent-list few times from admin tenant , the status result will be different ( see attached output )

agents do work and not report issue in the logs , i think it relate to rabbitMQ

issue is not reproduced on RHEL-OSP 4  A4

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


openstack-neutron-openvswitch-2014.1-11.el7.noarch
python-neutron-2014.1-11.el7.noarch
python-neutronclient-2.3.4-1.el7.noarch
openstack-neutron-2014.1-11.el7.noarch


How reproducible:


Steps to Reproduce:
1.run neutron agent-list few time on AIO setup with neutron 
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ofer Blaut 2014-05-01 14:20:01 UTC
Created attachment 891544 [details]
logs from files

Comment 2 Terry Wilson 2014-05-06 17:41:10 UTC
This sounds like what I see happening when agent_down_time/report_interval are configured with fairly low values. The new defaults should be 75/30. Are these values being specified in the configs? If debugging is turned on, can you verify what the settings are via the neutron server.log file?

Comment 3 Ofer Blaut 2014-05-07 12:53:17 UTC
both values are as appear  agent_down_time/report_interval  75/30
Debug is off , can't reproduce with selinux disabled

Comment 4 lpeer 2014-05-07 18:12:59 UTC
(In reply to Ofer Blaut from comment #3)
> both values are as appear  agent_down_time/report_interval  75/30
> Debug is off , can't reproduce with selinux disabled

Ofer, can you reproduce the issue at all?