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:
Newly created sync plans always have Start Date set to "null" and it's not possible the update those sync plans without mentioning the start date every time.
Version-Release number of selected component (if applicable):
# rpm -q satellite katello
satellite-6.13.0-4.el8sat.noarch
katello-4.7.0-1.el8sat.noarch
How reproducible:
Always
Steps to Reproduce:
1. Install Satellite 6.13 ( snap 9 )
2. Login as "admin" user, Edit the "Admin" user of the satellite and change its timezone from "Browser Local" to "Kolkata" or "New Delhi"
3. Go to Content --> Sync PLans
4. Create a "Sync Plan" with all necessary options selected i.e. Start Date, Weekly\daily\monthly and the time to start the sync, etc
5. Once the Sync plan is created, Check back on the "Start Date"
6. Edit the Interval of the plan and try to set it to something else and save.
Actual results:
Point 4: Start Date 'Nil'
Point 5: An error occurred saving the Sync Plan: base Start Date and Time can't be blank
Expected results:
The start Date should not be "Nil' if it was selected during sync plan creation.
Additional info:
It's reproducible on 6.12 as well ( as long as we don't forget to perform Step 2 )
The only other change I had made in this Sat instance was to change the login user's TZ i.e. from Browser Local to IST ( Kolkata )
# hammer user info --login admin | grep Timezone -B1
Locale: default
Timezone: Kolkata
And then used that user to create the Sync plan.
I took Satellite cert exam today. They use 6.11 I believe, at least that's in the exam descriptions. I had troubles as this hit me during the exam. The cert test is done over remote VNC, and my locale on local laptop is Finnish. Also formats was chosen to have Finnish from the gnome settinga.
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.