Description of problem:

While scheduling Remote execution job using hammer cli, the job scheduled actually runs at UTC time instead of server's own timezone(Default Timezone in satellite).

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

Satellite 6.11

How reproducible:

Steps to reproduce:

• Schedule Remote job using hammer cli:

1. date
   Tue Oct 18 14:29:42 IST 2022
   ~~~
2. hammer -d job-invocation create --job-template "Run Command - SSH Default" --organization-id "1" --location-id "2" --inputs command=date --search-query "client.example.com" --start-at "2022-10-18 14:35:00"
   ~~~
   We can see:
   Scheduled to start at: 2022-10-18 20:05:00 +0530
   Evaluated at: 2022-10-18 14:30:20 +0530

• Rerun the same job from Web UI, running on the server's timezone.

1. hammer job-invocation info --id 18
   —
   ID: 18
   Description: Run date
   Status: queued
   Success: N/A
   Failed: N/A
   Pending: N/A
   Missing: 0
   Total: N/A
   Start: '2022-10-18 14:36:00 +0530'
   Randomized ordering: false
   Job Category: Commands
   Mode: future
   Hosts:

• Name: client.example.com

1. date
   Tue Oct 18 14:35:08 IST 2022

• It is running on the expected timezone while running from Web UI.

Actual results:

• Scheduled remote job through hammer cli scheduled for 5:30 hours later than actual timezone.

Expected results:

• hammer should schedule the job same as running from Web UI on the server's timezone.