Description of problem: We are seeing two different issues. 1. Updating service dialogs customization doesn't work. Whenever we try to do any change in service dialog it’s not letting us save… first click it will work and then try to change some other or save it will just get hung and refresh will kick us out to login page. 2. Drop down list empty value issue… attachment 1 [details].png attachment 2 [details].png Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This sounds a lot like something we've dealt before with this exact dialog. Here's two related BZs: https://bugzilla.redhat.com/show_bug.cgi?id=1354635 https://bugzilla.redhat.com/show_bug.cgi?id=1435758 The first should have some instructions on how to increase the memcache size so that this dialog can be loaded and edited/added to (but please consider removing things instead of adding!). Realistically, we won't be continuing to support the old dialog editor, and the new dialog editor supports this large dialog without a memcache increase. I think if you need a workaround for now, follow the steps in the first linked BZ to increase the memcache size and that should fix the issue until the new dialog editor is the standard. If it does not, please report back and let us know.
It looks to be be correctly configured: Advanced settings: :memcache_server_opts: "-l 127.0.0.1 -I 5M" config/initializers/session_store.rb: :cache => Dalli::Client.new(Settings.session.memcache_server, :namespace => "MIQ:VMDB", :value_max_bytes => 10.megabytes), The log line comes from here: https://github.com/ManageIQ/manageiq-ui-classic/blob/69bec0a8db7b0385c0837545e7d4614e7ccaff2f/app/controllers/application_controller.rb#L1896-L1897 It's hardcoded to 100 KB here: https://github.com/ManageIQ/manageiq-ui-classic/blob/69bec0a8db7b0385c0837545e7d4614e7ccaff2f/app/controllers/mixins/controller_constants.rb#L9 That log line is independent from the dalli client or the memcached setting. You would get an error from dalli client if it couldn't store an object into memcached due to object size. Something like this: "Value for #{key} over max size: #{@options[:value_max_bytes]} <= #{value.bytesize}" https://github.com/petergoldstein/dalli/blob/v2.7.6/lib/dalli/server.rb#L478
Erik noticed this error in the evm.log: "Warning! ActionDispatch::Session::MemCacheStore failed to save session. Content dropped." This is the message to look for in the evm.log to see if the saving of the session was dropped by memcached because it was too large. That comes from rack: rack-2.0.3/lib/rack/session/abstract/id.rb-354- if not data = write_session(req, session_id, session_data, options) rack-2.0.3/lib/rack/session/abstract/id.rb:355: req.get_header(RACK_ERRORS).puts("Warning! #{self.class.name} failed to save session. Content dropped.") rack-2.0.3/lib/rack/session/abstract/id.rb-356- elsif options[:defer] and not options[:renew] rack-2.0.3/lib/rack/session/abstract/id.rb-357- req.get_header(RACK_ERRORS).puts("Deferring cookie for #{session_id}") if $VERBOSE rack-2.0.3/lib/rack/session/abstract/id.rb-358- else We tested this locally and found that you have to change the advanced settings :memcache_server_opts: "-l 127.0.0.1 -I 10M" and config/initializers/session_store.rb: :cache => Dalli::Client.new(Settings.session.memcache_server, :namespace => "MIQ:VMDB", :value_max_bytes => 10.megabytes) Then you must restart the server process.
Follow up to the last comment, after you save the configuration and restart the server, you should see memcached running with the desired max size (-I) value: # ps -ef |grep memcached memcach+ 2506 1 0 12:39 ? 00:00:00 /usr/bin/memcached -u memcached -p 11211 -m 64 -c 1024 -l 127.0.0.1 -I 10
*** This bug has been marked as a duplicate of bug 1354635 ***