Project

General

Profile

Actions
Copy link

Bug #34838

closed

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

Added by Jeremy Lenz over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Jeremy Lenz
Category:
Settings
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
2065015
Pull request:
https://github.com/theforeman/foreman/pull/9203
Fixed in Releases:
3.3.0
Found in Releases:
Red Hat JIRA:

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.

Actions
Copy link
 #1

Updated by Jeremy Lenz over 2 years ago

  • Project changed from Katello to Foreman
  • 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
  • Category deleted (Content Views)
Actions
Copy link
 #2

Updated by Jeremy Lenz over 2 years ago

  • Category set to Settings
Actions
Copy link
 #3

Updated by Jeremy Lenz over 2 years ago

  • Pull request https://github.com/theforeman/foreman/pull/9203 added
Actions
Copy link
 #4

Updated by The Foreman Bot over 2 years ago

  • Status changed from New to Ready For Testing
Actions
Copy link
 #5

Updated by The Foreman Bot over 2 years ago

  • Fixed in Releases 3.3.0 added
Actions
Copy link
 #6

Updated by Jeremy Lenz over 2 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link
 #7

Updated by Amit Upadhye over 2 years 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
Actions
Copy link

Also available in: Atom PDF