horizon lockout service parameters need to be cleaned up

Bug #1842960 reported by Tyler Smith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
Low
wanghao

Bug Description

Brief Description
-----------------
There are service parameters for horizon lockout settings. These are no longer used since we moved to vanilla horizon and abandoned our custom lockout feature, and should be removed:

| uuid | service | section | name | value | personality | resource |
+--------------------------------------+----------+-------------+-----------------------------+-------+-------------+----------+
| 2fffed95-6883-4291-b867-3afa54fa9418 | horizon | auth | lockout_retries | 3 | None | None |
| f520a7ff-aac1-4282-bfc9-f329a7f1218b | horizon | auth | lockout_seconds | 300 | None | None |

Code locations are in horizon puppet, helm overrides, armada manifest, and sysinv.

Severity
--------
Minor

Reproducibility
---------------
Reproducible

System Configuration
--------------------
all

Branch/Pull Time/Commit
-----------------------
latest

Test Activity
-------------
Documenting

description: updated
Revision history for this message
Ghada Khalil (gkhalil) wrote :

Low priority / not gating - code cleanup

Changed in starlingx:
importance: Undecided → Medium
status: New → Triaged
importance: Medium → Low
tags: added: stx.config
Changed in starlingx:
assignee: nobody → wanghao (wanghao749)
Revision history for this message
John Kung (john-kung) wrote :

This bug is duplicated and fixed via https://bugs.launchpad.net/starlingx/+bug/1950490

Changed in starlingx:
status: Triaged → Fix Released
Ghada Khalil (gkhalil)
tags: added: stx.8.0
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.