Bug 1651377

Summary: centralizing default index.html on nginx
Product: Red Hat Enterprise Linux 8 Reporter: Pat Riehecky <riehecky>
Component: nginxAssignee: Luboš Uhliarik <luhliari>
Status: CLOSED ERRATA QA Contact: icesalov
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.1CC: affix, athmanem, bnater, bperkins, cybernet2u, extras-qa, icesalov, jeremy, jkaluza, jorton, luhliari, pavel.lisy, peter.borsa, tadej.j, wtogami
Target Milestone: rc   
Target Release: 8.4   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1636235
: 1955560 (view as bug list) Environment:
Last Closed: 2021-05-18 15:45:09 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: 1896319    
Bug Blocks: 1955560    

Description Pat Riehecky 2018-11-19 21:03:58 UTC
+++ This bug was initially created as a clone of Bug #1636235 +++

Description of problem:
nginx provides a default welcome page with Fedora branding.  The new fedora-logos package (fedora-logos-httpd-30.0.0-1.fc30.noarch.rpm) now includes: /usr/share/fedora-testpage/index.html along with /usr/share/pixmaps/poweredby.png

Can the nginx package be modified to use this central index.html?

Version-Release number of selected component (if applicable):
nginx-1.12.1-14.fc29

How reproducible:
100%

Steps to Reproduce:
1.examine nginx for specific branding
2.see it contains an index.html
3.

Actual results:
Using locally maintained welcome page

Expected results:
Use new centrally maintained version.

Additional info:

--- Additional comment from Pat Riehecky on 2018-10-04 15:29:01 EDT ---

See also https://bugzilla.redhat.com/show_bug.cgi?id=1367535

Comment 1 cybernet 2020-02-01 10:20:04 UTC
bug status: still NEW :)

Comment 13 errata-xmlrpc 2021-05-18 15:45:09 UTC
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 (nginx:1.18 bug fix and enhancement update), 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/RHEA-2021:1834