Hide Forgot
Created attachment 1217087 [details] Screenshot of custom logos settings page Description of problem: After upgrading from 3.2 to 4.1 the custom logo is not displayed. The correct file (custom_logo.png) is in place in vmdb/public/upload and has the correct permissions. I have tried disabling/enabling the "Use Custom Logo Image option". I have also deleted the custom_logo.png file from the filesystem and re-uploading through the Web UI. When the custom_logo.png file is deleted from the filesystem the Web UI correctly reflects that "No custom logo image has been uploaded yet". [root@itmcf4rqui01 upload]# ls -alZ /var/www/miq/vmdb/public/upload drwxr-xr-x. root root system_u:object_r:httpd_sys_content_t:s0 . drwxr-xr-x. root root system_u:object_r:httpd_sys_content_t:s0 .. -rw-r--r--. root root system_u:object_r:httpd_sys_content_t:s0 custom_logo.png Attached is a screenshot showing the settings page. the logo appears to be blank (just a white block) as the image is a transparent png and the text is white so it shows on the dark background where the logo is supposed to be displayed). Version-Release number of selected component (if applicable): cfme-appliance-5.6.2.2-1.el7cf.x86_64 How reproducible: Always Steps to Reproduce: 1. Start with a 3.2 environment that is using a custom logo 2. Upgrade to 4.1 3. Place custom_logo.png in vmdb/public/upload and ensure correct permissions and SELinux context. 3. Custom logo will not be displayed in Web UI Actual results: Custom logo not displayed Expected results: Custom logo displayed Additional info:
Created attachment 1217091 [details] "Use Configuration Settings"
Assigning to Suyog for review. Suyog - see the above conversation for some notes about tenants and related settings. It might be good to call this one out as an example of what this configuration option is used for.