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.
Hello Giovanni,
After looking up the info on this error, it seems the bug was in Chrome itself.
Could you please confirm if the issue still exists? And if so, what version of Chrome do you use when the issue occurs?
As for bug itself, I'd suggest to fix this by providing a default (UTC) timezone in case we can't determine timezone based on user preferences/configuration, so users can still use the application. Would that be a sufficient solution?
Comment 2Giovanni Formisano
2024-01-16 15:45:47 UTC
Hello Oleh,
thank you to reply me.
Actually, I have noticed that the problem is no longer there.
I didn't update Chrome and the version is still the same ( Version 120.0.6099.129 (Official Build) (64-bit) ) .
After a week, like magic, everything was working properly.
I also tried deleting the cookies, at the time, but that didn't fix it.
Thank you for the fast reply! Sorry for bothering you once more, but just to be sure:
What do you suggest, closing this as NOTABUG or continue with the BZ and fix as I proposed in https://bugzilla.redhat.com/show_bug.cgi?id=2254976#c1?
Comment 4Giovanni Formisano
2024-01-17 06:56:35 UTC
Hello Oleh,
thank you so much for your job.
Actually I didn't receive any case with this kind of issue, at the moment.
I my opinion I will leave like a BZ and propose to fix your solution in comment#1
Verified in Sat. stream snap 60:
satellite-6.16.0-0.5.stream.el8sat.noarch
foreman-3.11.0-0.4.develop.20240514184808git5b00e9e.el8sat.noarch
After Satellite installation, logging into web UI is successful.
Using Chromium 125.0.6422.141, tried with different existing timezones (Eurepe/*, Aisa/*, America/*), as well as non-standard ones, like, "Etc/unknown" or even "XXX/YYY".
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.