tempest.api.network.admin.test_lbaas_agent_scheduler not supported

Bug #1475862 reported by Ryu Ishimoto
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-midonet
Invalid
Undecided
Unassigned

Bug Description

This is not a blocker, but we should definitely look at it. The test

setUpClass (tempest.api.network.admin.test_lbaas_agent_scheduler
    LBaaSAgentSchedulerTestJSON) FAIL

fails because our plugin reports the following supported extensions:

root@jenkins-centos7-kilo-controller ~(keystone_admin)$ neutron ext-list
+-----------------------+---------------------------------+
| alias | name |
+-----------------------+---------------------------------+
| service-type | Neutron Service Type Management |
| security-group | security-group |
| lbaas_agent_scheduler | Loadbalancer Agent Scheduler |
| binding | Port Binding |
| quotas | Quota management support |
| agent | agent |
| dhcp_agent_scheduler | DHCP Agent Scheduler |
| external-net | Neutron external network |
| router | Neutron L3 Router |
| extra_dhcp_opt | Neutron Extra DHCP opts |
| lbaas | LoadBalancing service |
+-----------------------+---------------------------------+

We should remove lbaas_agent_scheduler from our supported extensions as tempest relies on dynamically querying the extenions in order to know which tests to run.

Revision history for this message
Ryu Ishimoto (ryu-midokura) wrote :
Revision history for this message
yong sheng gong (gongysh) wrote :

why? I see we need to run dhcp agent in installation document. If there is not dhcp agent scheduler, how does it work?

Revision history for this message
yong sheng gong (gongysh) wrote :

sorry, it is lbaas_agent_scheduler.

Changed in networking-midonet:
assignee: nobody → yong sheng gong (gongysh)
assignee: yong sheng gong (gongysh) → nobody
Revision history for this message
yong sheng gong (gongysh) wrote :
Revision history for this message
Ryu Ishimoto (ryu-midokura) wrote :

Verified that this is no longer a problem.

Changed in networking-midonet:
status: New → Invalid
Changed in networking-midonet:
milestone: 1.0.0 → 1.0.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.