Bug 2135722
| Summary: | While scheduling Remote execution job using hammer cli, the job scheduled actually runs at UTC time instead of server's own timezone. | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Mohit Kushwah <mkushwah> |
| Component: | Hammer | Assignee: | Adam Ruzicka <aruzicka> |
| Status: | CLOSED ERRATA | QA Contact: | Peter Ondrejka <pondrejk> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.11.3 | CC: | arahaman, aruzicka, jwfrey, ofedoren, rlavi |
| Target Milestone: | 6.14.0 | Keywords: | Triaged, UserExperience |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | hammer-cli-3.7.0 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-11-08 14:18:02 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Upstream bug assigned to aruzicka Upstream bug assigned to aruzicka Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36418 has been resolved. Verified on Sat6.14 sn 7 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 (Important: Satellite 6.14 security and bug fix update), 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-2023:6818 |
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: # date Tue Oct 18 14:29:42 IST 2022 ~~~ # 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. # 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 # 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.