Red Hat Bugzilla – Bug 1460146
SyncPlan Start Date modified when creating and became Invalid when updating any sync plan field
Last modified: 2018-02-21 11:54:37 EST
Created attachment 1286347 [details]
Description of problem:
SyncPlan StartDate modified when creating and became Invalid when updating any sync plan field
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Goto Content > Sync Plan
2. Create a sync plan with start date for example 2017-16-15
1. The sync plan is created with Start Date 2017-16-14
2. Any attempt to update any field for example name or description or interval lead to error and the start date became with value Invalid Date
1. The start Date should not be changed by the server
2. The field in the are successfully updated
Created attachment 1286348 [details]
Created attachment 1286349 [details]
Created attachment 1286350 [details]
Created attachment 1286355 [details]
I have run several tests on the upstream Katello 3.4 build (tfm-rubygem-katello-18.104.22.168-2.el7.noarch) and am not seeing any errors.
created a plan with a start date of 2017-06-15 - no error
updated name, description, start date, enabled and interval - no error
Based on this, moving to POST for QE.
The package listed in comment 6 has been delivered to QA, so I am moving this to ON_QA.
This bug failed verification by automation, and manually
Move to ASSIGNED attach screenshots
Created attachment 1316652 [details]
sync plan creation stage and before saving
Created attachment 1316653 [details]
sync plan creation after submit
tested on satellite 6.3 snap 12
Since you have done a lot of timezone related work in the past, can you take a look at this one?
No code changes were made to address it; however, I was unable to reproduce it on my environment. The one key difference between our test scenarios is timezone.
Also, the current behavior seen is not the validation error on update, but the fact that the date selected during create, is not shown after the creation. Instead, it appears to be day-1. (Refer to the screenshots in comment 10 and comment 11).
Sure, thanks for the initial investigation.
Djebran can you provide some more information about the setup you have to reproduce this issue? I've tried changing my timezone in foreman, creating multiple sync plans, setting the hours field to different values, but I'm not able to see the issue.
Could be related to https://github.com/Katello/katello/pull/6872 (bug #1438845). Can you reproduce this in a recent snap?
Tested yesterday in a meeting with Dan and it was reproducible on satellite 6.3 snap 18.
*** Bug 1498793 has been marked as a duplicate of this bug. ***
Created redmine issue http://projects.theforeman.org/issues/21950 from this bug
I cannot reproduce this given the steps to reproduce. Please provide additional steps to reproduce.
I also cannot reproduce that behavior any more.
Verified on Sat 6.3 snap 33
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/RHSA-2018:0336