Bug 1647938
Summary: | Update default RSS feed to point to new Blog location | |||
---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | John Spinks <jspinks> | |
Component: | WebUI | Assignee: | Marek Hulan <mhulan> | |
WebUI sub component: | Foreman | QA Contact: | Jameer Pathan <jpathan> | |
Status: | CLOSED ERRATA | Docs Contact: | ||
Severity: | medium | |||
Priority: | unspecified | CC: | cmarinea, egolov, jpathan, jspinks, mhulan, mmccune, sgraessl, sshtein | |
Version: | 6.4 | Keywords: | PrioBumpGSS | |
Target Milestone: | 6.5.0 | |||
Target Release: | Unused | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | tfm-rubygem-foreman_theme_satellite-3.0.1.4-1 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1684692 1684708 (view as bug list) | Environment: | ||
Last Closed: | 2019-05-14 12:38:40 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: |
Description
John Spinks
2018-11-08 15:13:08 UTC
verified @satellite 6.5.0 snap 4 Steps: 1.Log into Sat 2.Check notification drawer 3.Old RSS feed is displayed observation: - New RSS feed shown. - RSS URL in settings > notifications is: https://www.redhat.com/en/rss/blog/channel/red-hat-satellite I think it would be great to add this to a 6.4 z-stream, but this is PM decision. Blog team does not want us posting in both locations unless there is a critical need. Their ask is to have everyone move over to the new location. I missed that this was in my queue until now - sorry for the delay. *** Bug 1684692 has been marked as a duplicate of this bug. *** This bug was cloned and is still going to be included in the 6.4.3 release. It no longer has the sat-6.4.z+ flag and 6.4.3 Target Milestone Set which are now on the 6.4.z cloned bug. Please see the Clones field to track the progress of this bug in the 6.4.3 release. 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, 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-2019:1222 |