Project

General

Profile

Bug #34838

"Sync Connect Timeout" setting takes invalid value and shows update successful but doesn't reflect the change for invalid values

Added by Jeremy Lenz 2 months ago. Updated 21 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Settings
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=2065015

Description of problem:
"Sync Connect Timeout" settings takes invalid value and shows update successful but doesn't reflect the change for invalid values.

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

How reproducible:
Always

Steps to Reproduce:
UI:
1. Administer -> Settings -> Content -> Sync Connection Timeout
2. Edit the value to any invalid value eg. -1 and submit it

CLI:
hammer settings set --id sync_connect_timeout_v2 --value -1

Actual results:
UI:
Displays value updated successfully but doesn't get reflected on the value

CLI:
Setting [sync_connect_timeout_v2] updated to [60].

Expected results:
Error should be displayed for invalid values

Additional info:
This behavior is consistent on CLI, API and UI.

Associated revisions

Revision 662c4a3a (diff)
Added by Jeremy Lenz about 2 months ago

Fixes #34838 - Add errors when setting values are invalid (#9203)

History

#1 Updated by Jeremy Lenz 2 months ago

  • Category deleted (Content Views)
  • Subject changed from "Sync Connect Timeout" settings takes invalid value and shows update successful but doesn't reflect the change for invalid values to "Sync Connect Timeout" settings takes invalid value and shows update successful but doesn't reflect the change for invalid values
  • Project changed from Katello to Foreman

#2 Updated by Jeremy Lenz 2 months ago

  • Category set to Settings

#3 Updated by Jeremy Lenz 2 months ago

  • Pull request https://github.com/theforeman/foreman/pull/9203 added

#4 Updated by The Foreman Bot about 2 months ago

  • Status changed from New to Ready For Testing

#5 Updated by The Foreman Bot about 2 months ago

  • Fixed in Releases 3.3.0 added

#6 Updated by Jeremy Lenz about 2 months ago

  • Status changed from Ready For Testing to Closed

#7 Updated by Amit Upadhye 21 days ago

  • Subject changed from "Sync Connect Timeout" settings takes invalid value and shows update successful but doesn't reflect the change for invalid values to "Sync Connect Timeout" setting takes invalid value and shows update successful but doesn't reflect the change for invalid values

Also available in: Atom PDF