Description of problem: When I try to update any field for Sync Plan entity in UI and push 'Save' button, 'Start Date' for it is transformed to 'Invalid Date' value and corresponding error 'An error occurred saving the Sync Plan: base Start Date and Time can't be blank' is displayed It seems that issue is specific for Firefox browser of any version Version-Release number of selected component (if applicable): 6.2 SNAP 9.2 How reproducible: Always Steps to Reproduce: 1. Create sync plan with default values (or add 10 days to start day for example) 2. Open just created entity 3. Try to change value for any field (let's say 'description' or 'interval') Actual results: Sync plan cannot be updated and error is displayed Expected results: Sync plan can be updated Additional info:
Created attachment 1150412 [details] Screenshot with issue for UI
Created attachment 1150413 [details] Part of the production log with error
From first glance, there is a script that executed against Start Date field each time you try to update something, but due some reasons it works improperly for all Firefox versions including latest. Works properly on latest Google Chrome Not sure about other browsers
The fix for bug 1200625 actually solves this issue. I am going to mark this one as a duplicate with a note on the other to also test for this condition. *** This bug has been marked as a duplicate of bug 1200625 ***
@Brad: The other one shows RFE which is misleading. Although the RFE implementation will fix this, this bug needs to stay open to track this issue. Can we please keep this bug open and move this to ON_QA when the other one moves to ON_QA? Please ping me if you have more questions.
Created attachment 1154646 [details] verified - syncplan update screenshot
VERIFIED on sat6.2.0 Beta (GA10) sync plan can be updated + saved successfully (see screenshot)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1501