Use constants for protocol values in tests in load balancer comonents

Bug #1516296 reported by Manjeet Singh Bhatia
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Expired
Wishlist
Unassigned

Bug Description

I see direct values for protocols are used while testing listener and pool.
It would be good to use constants which are already defined. in functional and unit tests.

I was trying to implement its case insensitivity but since protocol value is hardcoded
in most tests so all the test were breaking.

The changes will be easy if we use already defined constants.

Tags: lbaas
Changed in neutron:
assignee: nobody → Manjeet Singh Bhatia (manjeet-s-bhatia)
tags: added: lbaas
description: updated
Revision history for this message
Priya Kanaujia (priya-kanaujia) wrote :

Can you please elaborate the issue? Where exactly values are hardcoded ?

Revision history for this message
Manjeet Singh Bhatia (manjeet-s-bhatia) wrote :

values are hardcoded in tests

Gary Kotton (garyk)
Changed in neutron:
importance: Undecided → Low
status: New → Confirmed
importance: Low → Wishlist
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This bug is > 240 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

Changed in neutron:
assignee: Manjeet Singh Bhatia (manjeet-s-bhatia) → nobody
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
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.