Description of problem: 1. Background & custom logo image not showing in http service after upgrading to cfme-5.6.2.1 2. https service is showing correct customer background & customer image though 3. It was working in cfme-5.6.0.13-1 4. Customer is using only http service in production not https due to local VPN limitation 5. Customer is using modified httpd.config with previous bz case https://bugzilla.redhat.com/show_bug.cgi?id=1351417 6. Customer is the middle of upgrading CFME project which needs to use new feature in CFME 5.6.1 and this is show-stopper for the project Version-Release number of selected component (if applicable): # rpm -qa|grep cfme cfme-5.6.2.1-1.el7cf.x86_64 cfme-appliance-5.6.2.1-1.el7cf.x86_64 cfme-gemset-5.6.2.1-1.el7cf.x86_64 rh-ruby22-rubygem-redhat_access_cfme-1.0.3-1.el7cf.noarch How reproducible: #apply customer config on cfme-5.6.2.1 Steps to Reproduce: 1.Apply customer http.conf,ession_store.rb 2.Upload customized Background & custom logo image 3.Check http service(check https service) Actual results: https service is working as expected - showing customized background http is showing blank Expected results: http service is showing customized background Additional info: CEE reproduced in internal Red hat lab : https://10.65.7.236 http://10.65.7.236
Fatal error in production.log while accessing http service ########################################### [----] F, [2016-10-18T20:32:53.760282 #4048:13c9140] FATAL -- : [----] F, [2016-10-18T20:32:53.760382 #4048:13c9140] FATAL -- : ActionController::RoutingError (No route matches [GET] "/upload/custom_login_logo.png"): [----] F, [2016-10-18T20:32:53.760443 #4048:13c9140] FATAL -- : [----] F, [2016-10-18T20:32:53.760492 #4048:13c9140] FATAL -- : actionpack (5.0.0.1) lib/action_dispatch/middleware/debug_exceptions.rb:53:in `call' [----] F, [2016-10-18T20:32:53.760536 #4048:13c9140] FATAL -- : actionpack (5.0.0.1) lib/action_dispatch/middleware/show_exceptions.rb:31:in `call' [----] F, [2016-10-18T20:32:53.760594 #4048:13c9140] FATAL -- : railties (5.0.0.1) lib/rails/rack/logger.rb:36:in `call_app' [----] F, [2016-10-18T20:32:53.760676 #4048:13c9140] FATAL -- : railties (5.0.0.1) lib/rails/rack/logger.rb:26:in `call' [----] F, [2016-10-18T20:32:53.760725 #4048:13c9140] FATAL -- : request_store (1.3.1) lib/request_store/middleware.rb:9:in `call' [----] F, [2016-10-18T20:32:53.760783 #4048:13c9140] FATAL -- : actionpack (5.0.0.1) lib/action_dispatch/middleware/request_id.rb:24:in `call' [----] F, [2016-10-18T20:32:53.760830 #4048:13c9140] FATAL -- : rack (2.0.1) lib/rack/method_override.rb:22:in `call' [----] F, [2016-10-18T20:32:53.760915 #4048:13c9140] FATAL -- : rack (2.0.1) lib/rack/runtime.rb:22:in `call' [----] F, [2016-10-18T20:32:53.760992 #4048:13c9140] FATAL -- : activesupport (5.0.0.1) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call' [----] F, [2016-10-18T20:32:53.761056 #4048:13c9140] FATAL -- : actionpack (5.0.0.1) lib/action_dispatch/middleware/executor.rb:12:in `call' [----] F, [2016-10-18T20:32:53.761104 #4048:13c9140] FATAL -- : rack (2.0.1) lib/rack/sendfile.rb:111:in `call' [----] F, [2016-10-18T20:32:53.761156 #4048:13c9140] FATAL -- : railties (5.0.0.1) lib/rails/engine.rb:522:in `call' [----] F, [2016-10-18T20:32:53.761202 #4048:13c9140] FATAL -- : puma (3.3.0) lib/puma/configuration.rb:224:in `call' [----] F, [2016-10-18T20:32:53.761253 #4048:13c9140] FATAL -- : puma (3.3.0) lib/puma/server.rb:561:in `handle_request' [----] F, [2016-10-18T20:32:53.761319 #4048:13c9140] FATAL -- : puma (3.3.0) lib/puma/server.rb:406:in `process_client' [----] F, [2016-10-18T20:32:53.761369 #4048:13c9140] FATAL -- : puma (3.3.0) lib/puma/server.rb:271:in `block in run' [----] F, [2016-10-18T20:32:53.761413 #4048:13c9140] FATAL -- : puma (3.3.0) lib/puma/thread_pool.rb:111:in `call' [----] F, [2016-10-18T20:32:53.761456 #4048:13c9140] FATAL -- : puma (3.3.0) lib/puma/thread_pool.rb:111:in `block in spawn_thread' [----] F, [2016-10-18T20:32:53.761499 #4048:13c9140] FATAL -- : logging (2.1.0) lib/logging/diagnostic_context.rb:450:in `call' [----] F, [2016-10-18T20:32:53.761543 #4048:13c9140] FATAL -- : logging (2.1.0) lib/logging/diagnostic_context.rb:450:in `block in create_with_logging_context'
Hi Dan Sorry for chasing. I found workaround and updated it in this bz case. Can you please review & confirm whether it is feasible to deliver to customer ? Regards, Taeho
Hi Team Do you have any update on this case? This is Sev2 case issue, need to provide update to customer. Taeho
Better solution: Add line DocumentRoot /var/www/miq/vmdb/public to /etc/httpd/conf.d/manageiq-http.conf The final content of the file: Timeout 120 # HTTP Start-up error log ErrorLog /var/www/miq/vmdb/log/apache/miq_apache.log # Disable this section if using HTTP only RewriteEngine On Options SymLinksIfOwnerMatch RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^.*$ https://%{SERVER_NAME}%{REQUEST_URI} [L,R] # Enable this section if using HTTP only <VirtualHost *:80> DocumentRoot /var/www/miq/vmdb/public Include conf.d/manageiq-redirects-ui Include conf.d/manageiq-redirects-ws Include conf.d/manageiq-redirects-websocket ProxyPreserveHost on LogLevel warn <Location /assets/> Header unset ETag FileETag None ExpiresActive On ExpiresDefault "access plus 1 year" </Location> </VirtualHost> This is better than allowing the static assets through Rails. I will make sure the appliance config files contain this line or similar. Let me know if this works for you (I tested on 10.65.7.236).
upstream PR: https://github.com/ManageIQ/manageiq-appliance/pull/97
Verified in 5.8.0.11