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.
Created attachment 1991849[details]
Screenshot showing Start Date of the recurring logic associated with the sync plan
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:
~~~
# 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
~~~
~~~
# 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
---|------|---------------------|----------|---------|-----------------|-------------------
~~~
~~~
# 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:
~~~
# 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.
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Created attachment 1991849 [details] Screenshot showing Start Date of the recurring logic associated with the sync plan 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: ~~~ # 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 ~~~ ~~~ # 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 ---|------|---------------------|----------|---------|-----------------|------------------- ~~~ ~~~ # 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: ~~~ # 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.