Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1460146 - SyncPlan Start Date modified when creating and became Invalid when updating any sync plan field
Summary: SyncPlan Start Date modified when creating and became Invalid when updating a...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Sync Plans
Version: 6.3.0
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: Unspecified
Assignee: Walden Raines
QA Contact: Peter Ondrejka
URL: http://projects.theforeman.org/issues...
Whiteboard:
: 1498793 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-09 09:05 UTC by Djebran Lezzoum
Modified: 2019-04-01 20:27 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot 1 (85.95 KB, image/png)
2017-06-09 09:05 UTC, Djebran Lezzoum 		no flags Details
screenshot 2 (86.36 KB, image/png)
2017-06-09 09:06 UTC, Djebran Lezzoum 		no flags Details
screenshot 3 (91.29 KB, image/png)
2017-06-09 09:06 UTC, Djebran Lezzoum 		no flags Details
screenshot 4 (95.49 KB, image/png)
2017-06-09 09:07 UTC, Djebran Lezzoum 		no flags Details
foreman-debug-output (4.39 MB, application/octet-stream)
2017-06-09 09:11 UTC, Djebran Lezzoum 		no flags Details
sync plan creation stage and before saving (49.24 KB, image/png)
2017-08-22 13:35 UTC, Djebran Lezzoum 		no flags Details
sync plan creation after submit (53.88 KB, image/png)
2017-08-22 13:36 UTC, Djebran Lezzoum 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 21950 0 None None None 2017-12-12 16:01:10 UTC

Description Djebran Lezzoum 2017-06-09 09:05:56 UTC 
Created attachment 1286347 [details]
screenshot 1

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):
* candlepin-2.0.35-1.el7.noarch
* candlepin-selinux-2.0.35-1.el7.noarch
* foreman-1.15.0-1.el7sat.noarch
* foreman-cli-1.15.0-1.el7sat.noarch
* foreman-compute-1.15.0-1.el7sat.noarch
* foreman-debug-1.15.0-1.el7sat.noarch
* foreman-discovery-image-3.1.1-22.el7sat.noarch
* foreman-ec2-1.15.0-1.el7sat.noarch
* foreman-gce-1.15.0-1.el7sat.noarch
* foreman-installer-1.15.0-1.el7sat.noarch
* foreman-installer-katello-3.4.0.1-1.el7sat.noarch
* foreman-libvirt-1.15.0-1.el7sat.noarch
* foreman-openstack-1.15.0-1.el7sat.noarch
* foreman-ovirt-1.15.0-1.el7sat.noarch
* foreman-postgresql-1.15.0-1.el7sat.noarch
* foreman-proxy-1.15.0-2.el7sat.noarch
* foreman-rackspace-1.15.0-1.el7sat.noarch
* foreman-selinux-1.15.0-1.el7sat.noarch
* foreman-vmware-1.15.0-1.el7sat.noarch
* katello-3.4.0-3.el7sat.noarch
* katello-ca-consumer-sat-r220-02.lab.eng.rdu2.redhat.com-1.0-1.noarch
* katello-certs-tools-2.4.0-1.el7sat.noarch
* katello-client-bootstrap-1.3.0-1.el7sat.noarch
* katello-common-3.4.0-3.el7sat.noarch
* katello-debug-3.4.0-3.el7sat.noarch
* katello-default-ca-1.0-1.noarch
* katello-installer-base-3.4.0.1-1.el7sat.noarch
* katello-selinux-3.0.2-1.el7sat.noarch
* katello-server-ca-1.0-1.noarch
* katello-service-3.4.0-3.el7sat.noarch
* openldap-2.4.40-13.el7.x86_64
* pulp-client-1.0-1.noarch
* pulp-docker-plugins-2.3.0-1.el7sat.noarch
* pulp-katello-1.0.2-1.el7sat.noarch
* pulp-ostree-plugins-1.2.1-1.el7sat.noarch
* pulp-puppet-plugins-2.12.2-1.el7sat.noarch
* pulp-puppet-tools-2.12.2-1.el7sat.noarch
* pulp-rpm-plugins-2.12.2-1.el7sat.noarch
* pulp-selinux-2.12.2-1.el7sat.noarch
* pulp-server-2.12.2-1.el7sat.noarch
* python-ldap-2.4.15-2.el7.x86_64
* tfm-rubygem-ldap_fluff-0.4.6-1.el7sat.noarch
* tfm-rubygem-net-ldap-0.15.0-1.el7sat.noarch


How reproducible:
Always

Steps to Reproduce:
1. Goto Content > Sync Plan
2. Create a sync plan with start date for example 2017-16-15
3. 

Actual results:
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 


Expected results:
1. The start Date should not be changed by the server
2. The field in the are successfully updated


Additional info:
Comment 1 Djebran Lezzoum 2017-06-09 09:06:31 UTC 
Created attachment 1286348 [details]
screenshot 2
Comment 2 Djebran Lezzoum 2017-06-09 09:06:56 UTC 
Created attachment 1286349 [details]
screenshot 3
Comment 3 Djebran Lezzoum 2017-06-09 09:07:23 UTC 
Created attachment 1286350 [details]
screenshot 4
Comment 4 Djebran Lezzoum 2017-06-09 09:11:22 UTC 
Created attachment 1286355 [details]
foreman-debug-output
Comment 6 Brad Buckingham 2017-06-13 15:09:49 UTC 
I have run several tests on the upstream Katello 3.4 build (tfm-rubygem-katello-3.4.0.2-2.el7.noarch) and am not seeing any errors.

E.g. 
   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.
Comment 7 Bryan Kearney 2017-06-15 13:12:43 UTC 
The package listed in comment 6 has been delivered to QA, so I am moving this to ON_QA.
Comment 9 Djebran Lezzoum 2017-08-22 13:34:36 UTC 
This bug failed verification by automation, and manually
Move to ASSIGNED attach screenshots
Comment 10 Djebran Lezzoum 2017-08-22 13:35:46 UTC 
Created attachment 1316652 [details]
sync plan creation stage and before saving
Comment 11 Djebran Lezzoum 2017-08-22 13:36:48 UTC 
Created attachment 1316653 [details]
sync plan creation after submit
Comment 12 Djebran Lezzoum 2017-08-22 13:38:07 UTC 
tested on satellite 6.3 snap 12
Comment 13 Brad Buckingham 2017-09-22 14:54:34 UTC 
Walden,

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).
Comment 14 Walden Raines 2017-09-22 16:18:55 UTC 
Sure, thanks for the initial investigation.
Comment 15 Dan Seethaler 2017-09-26 14:34:38 UTC 
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.
Comment 16 Walden Raines 2017-10-03 14:31:28 UTC 
Could be related to https://github.com/Katello/katello/pull/6872 (bug #1438845).  Can you reproduce this in a recent snap?
Comment 17 Djebran Lezzoum 2017-10-03 15:01:22 UTC 
HI Walden, 

Tested yesterday in a meeting with Dan and it was reproducible on satellite 6.3 snap 18.
Comment 18 Brad Buckingham 2017-10-13 14:30:00 UTC 
*** Bug 1498793 has been marked as a duplicate of this bug. ***
Comment 19 Walden Raines 2017-12-12 15:08:10 UTC 
Created redmine issue http://projects.theforeman.org/issues/21950 from this bug
Comment 20 Walden Raines 2018-01-17 21:29:55 UTC 
I cannot reproduce this given the steps to reproduce.  Please provide additional steps to reproduce.
Comment 21 Djebran Lezzoum 2018-01-18 14:07:19 UTC 
Hi Walden!

I also cannot reproduce that behavior any more.
Comment 22 Peter Ondrejka 2018-01-24 15:04:13 UTC 
Verified on Sat 6.3 snap 33
Comment 23 Satellite Program 2018-02-21 16:54:37 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.