Description of problem:

The time in the 'Start Date' field for a sync plan and its associated recurring logic is displayed correctly in Red Hat Satellite's 6.13.4 web UI. But when running the 'hammer sync-plan info' or 'hammer recurring-logic info' commands against the sync plan and its associated recurring logic respectively, the time displayed in the output from the hammer commands is always lagging by 2 hours.

For example:

~~~

1. timedatectl
   Local time: Tue 2023-10-03 09:01:22 EDT
   Universal time: Tue 2023-10-03 13:01:22 UTC
   RTC time: Tue 2023-10-03 13:01:23
   Time zone: America/New_York (EDT, -0400)
   System clock synchronized: yes
   NTP service: active
   RTC in local TZ: no
   ~~~

~~~

1. hammer sync-plan list --organization Org_1
   --|----|-------------------|--------|-------|---------------|------------------
   ID | NAME | START DATE | INTERVAL | ENABLED | CRON EXPRESSION | RECURRING LOGIC ID
   --|----|-------------------|--------|-------|---------------|------------------
   1 | 1st | 2023/10/02 10:00:00 | daily | yes | | 15
   --|----|-------------------|--------|-------|---------------|------------------
   ~~~

~~~

1. hammer recurring-logic info --id 15
   ID: 15
   Cron line: 0 12 * * *
   Action: Run Sync Plan:
   Last occurrence: -
   Next occurrence: 2023-10-04 10:00:00 UTC
   Iteration: 1
   Iteration limit: Unlimited
   Repeat until: Unlimited
   State: active
   ~~~

The issue is observed no matter what time zone the Satellite server is configured with.

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

Red Hat Satellite 6.13.4.1-1

How reproducible:

Always

Steps to Reproduce:

1. Create a sync plan either from Satellite's web UI or using hammer commands like:

~~~

1. hammer sync-plan create --name hammer_syncplan2 --organization Org_1 --sync-date "2022-09-25T14:30:00 CEST" --enabled=true --interval daily
   ~~~

2. Cross-check the time in the 'Stat Date' field for the sync plan or its associated recurring logic in Satellite's web UI with the value returned by 'hammer sync-plan info' or 'hammer recurring-logic info' commands.

Actual results:

The time displayed in the output from the 'hammer sync-plan info' or 'hammer recurring-logic info' commands for the 'Start Date' field is lagging by 2 hours compared to the the time displayed in the 'Start Date' field in the web UI.

Expected results:

The values from hammer commands and the Satellite web UI match.

Additional info:

See the attached screenshots for illustration of the example mentioned in the description of the problem.