Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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.
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.