Bug 2254976

Summary:	After satellite installation login page respond with "Invalid Timezone: Etc/Unknown"
Product:	Red Hat Satellite	Reporter:	Giovanni Formisano <gformisa>
Component:	Authentication	Assignee:	Oleh Fedorenko <ofedoren>
Status:	CLOSED MIGRATED	QA Contact:	Pavel Novotny <pnovotny>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.15.0	CC:	ahumbe, aruzicka, ehelms, mhulan, ofedoren, pnovotny, rlavi
Target Milestone:	stream	Keywords:	EasyFix, MigratedToJIRA, Triaged, UserExperience, WorkAround
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:38:46 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:

Comment 1 Oleh Fedorenko 2024-01-16 14:35:18 UTC

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 2 Giovanni 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.

Comment 3 Oleh Fedorenko 2024-01-16 16:00:46 UTC

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 4 Giovanni 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

Comment 6 Oleh Fedorenko 2024-01-19 13:47:03 UTC

Created redmine issue https://projects.theforeman.org/issues/37069 from this bug

Comment 7 Bryan Kearney 2024-03-15 12:03:31 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/37069 has been resolved.

Comment 8 Adam Ruzicka 2024-04-15 09:00:03 UTC

This is already in stream

Comment 9 Pavel Novotny 2024-06-05 11:56:59 UTC

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".

Comment 10 Eric Helms 2024-06-06 16:38:46 UTC

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.