Bug 1775813
| Summary: | A publish content view displays (Invalid Date) for the date and time of when the content view was published. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Satyajit Das <sadas> | ||||
| Component: | Content Views | Assignee: | satellite6-bugs <satellite6-bugs> | ||||
| Status: | CLOSED ERRATA | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.6.0 | CC: | ahumbe, arahaman, bbuckingham, dchaudha, dhjoshi, gpadholi, janarula, jentrena, jjansky, jlenz, karnsing, kupadhya, onerleka, patalber, peter.vreman, rcavalca, rdesouza, sean, shtiwari, smajumda, swa, zhunting | ||||
| Target Milestone: | 6.12.0 | Keywords: | PrioBumpGSS, Reopened, Triaged, UserExperience | ||||
| Target Release: | Unused | Flags: | jlenz:
needinfo?
(onerleka) |
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-11-16 13:32:23 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1122832 | ||||||
| Attachments: |
|
||||||
|
Description
Satyajit Das
2019-11-22 21:08:33 UTC
Created attachment 1638932 [details]
Invalid date screenshot.
Invalid date screenshot.
Brad, Small additions regarding browsers: Viewing same URL (https://sat6.example.com/content_views?page=1&per_page=50&sortBy=name&sortOrder=ASC) looking at the last published column User profile: UTC Firefox 71.0 under Windows -> Invalid Date Chrome 79.0 under Windows -> OK User profile: BrowserTime Firefox 71.0 under Windows -> CET (GMT+1 or GMT+2 summertime) OK Chrome 79.0 under Windows -> UTC time User profile: CEST GMT+1 Firefox 71.0 under Windows -> CET (GMT+1 or GMT+2 summertime) OK Chrome 79.0 under Windows -> CET (GMT+1 or GMT+2 summertime) OK So there it is really browser dependent how dates are handled. Peter Currently reinstalling a fresh Sat 6.6 lab. I'm getting the error on: Fedora 31 / Firefox 74.0 with some extensions (ublock, privacy badger, etc.) and some about:config hardening / "browser timezone" setting I'm NOT getting the error on: Fedora 31 / Firefox 74.0 default config (no hardening or extensions) / "browser timezone" setting Hi John, Adding a needinfo for you for awareness. As part of the content publication workflow improvements, it would good to ensure that the behavior described by this bugzilla is no longer existing. Thanks! Created redmine issue https://projects.theforeman.org/issues/30334 from this bug Thanks Brad, I added it to the feature tracker so we can confirm it's fixed with the improvements. Confirmed that 'Invalid Date' is not displayed on screen, either in the current content views page or the new content view UI that will preview in Satellite 6.10. See screenshots attached above from Chrome 91 on Fedora 34 / current upstream master Also tested on Safari 14.1.1 ( 16611.2.7.1.4 ) with Katello 3.18. Closing as CURRENTRELEASE - please reopen if you're still seeing Invalid Date on current versions of Satellite. Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30334 has been resolved. Was able to test this on chrome 103.0.5060.134 and firefox 103. All CVs published was published with the correct date. There's no invalid date being displayed. I checked both the new cv and legacy cv. Both displayed correct date. Verified on 6.12 snap 3 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.12 Release), 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-2022:8506 |