Created attachment 1427268 [details]
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Have an appliance in podified environment
2. Go to Configuration -> Diagnostics -> Region -> Database
Tab is empty and error in production.log
It's blowing up in:
[----] F, [2018-04-26T13:54:51.933068 #277:82c7b0] FATAL -- : Error caught: [NoMethodError] undefined method `' for nil:NilClass
@database_details = Rails.configuration.database_configuration[Rails.env]
if @database_details["host"].in?([nil, "", "localhost", "127.0.0.1"])
It's blowing up in database_details because Rails.configuration.database_configuration[Rails.env] is nil.
database_details is called from build_backup_schedule_options_for_select. I guess we're using environment variables in pods to find the database. Does it even make sense to have the scheduled database backup screen for podified?
> Does it even make sense to have the scheduled database backup screen for podified?
Nope, database backup through the application won't work in podified so we shouldn't be showing any of that.
We have a convenience method to check this kind of thing. In this case we should only show the screen `unless MiqEnvironment.is_container?` 
Also, as a side note, we also have a method for checking if the database is running locally which would be better than redoing that logic in the controller (and would also fix this particular issue)