I'm working on the latest/master code. The above error is raised when trying to create a new cloud volume (similar error also raises for creating host-initiators and volume mapping).
I openned an issue on it:
Can you please update me about this issue.
Coststhat you see in one of the tabs doesn't even appear in the product
I first found it in src/dialog-user/services/dialogData.ts, but updating and restarting our evmserverd does not result in a change of that message to the end user when validation of the text field element fails.
yeah we don't run the source directly - we compile the code using webpack and that's what is run
Dear MIQ team,
we found a bug in M release. some fields are missing only in Morphy version (Not in master) when trying to create new physical storage.
We traced the problem to faulty variable initialization.
we have an hidden text field in the form that use to determine if we are in edit mode or new mode. the default value of the field is empty string, and in edit mode it set to 'yes'. for some reasone in the M release the default value (empty string) is not set correctly, and the fix for that is adding to that field the following attribute: initialValue: ''
I dont know why the default value is not working like we expect in the M release. in the master branch it works like expected (empty text fields have value of empty string by defualt).
I opened a PR to fix this issue (ManageIQ/manageiq-ui-classic#8014), but maybe you can explain me why its not working only in Morphy? is it because ddf version differences ? other dependecies diffs?
Not sure, but I am consistently getting PUMA error on the latest master
Puma starting in single mode... * Version 4.3.11 (ruby 2.7.2-p137), codename: Mysterious Traveller * Min threads: 5, max threads: 5 * Environment: development [----] E, [2022-03-21T11:04:16.225334 #4484:945c] ERROR -- evm: MIQ(MiqWorker::Runner) ID  PID  GUID [0d8c4da5-1b49-4f90-aa66-48ee4f75a5e1] An unhandled error has occurred: Address already in use - bind(2) for "0.0.0.0" port 5000 /Users/kuldip.nanda/.rvm/gems/ruby-2.7.2/gems/puma-4.3.11/lib/puma/binder.rb:229:in `initialize' /Users/kuldip.nanda/.rvm/gems/ruby-2.7.2/gems/puma-4.3.11/lib/puma/binder.rb:229:in `new' /Users/kuldip.nanda/.rvm/gems/ruby-2.7.2/gems/puma-4.3.11/lib/puma/binder.rb:229:in `add_tcp_listener' /Users/kuldip.nanda/.rvm/gems/ruby-2.7.2/gems/puma-4.3.11/lib/puma/binder.rb:106:in `block in parse' /Users/kuldip.nanda/.rvm/gems/ruby-2.7.2/gems/puma-4.3.11/lib/puma/binder.rb:90:in `each' /Users/kuldip.nanda/.rvm/gems/ruby-2.7.2/gems/puma-4.3.11/lib/puma/binder.rb:90:in `parse' /Users/kuldip.nanda/.rvm/gems/ruby-2.7.2/gems/puma-4.3.11/lib/puma/runner.rb:161:in `load_and_bind' /Users/kuldip.nanda/.rvm/gems/ruby-2.7.2/gems/puma-4.3.11/lib/puma/single.rb:98:in `run' /Users/kuldip.nanda/.rvm/gems/ruby-2.7.2/gems/puma-4.3.11/lib/puma/launcher.rb:172:in `run' /Users/kuldip.nanda/.rvm/gems/ruby-2.7.2/gems/puma-4.3.11/lib/rack/handler/puma.rb:73:in `run' /Users/kuldip.nanda/.rvm/gems/ruby-2.7.2/gems/rack-2.2.3/lib/rack/server.rb:327:in `start' /Users/kuldip.nanda/.rvm/gems/ruby-2.7.2/gems/railties-220.127.116.11/lib/rails/commands/server/server_command.rb:39:in `start' /Users/kuldip.nanda/projects/easy/githubfork/manageiq/app/models/mixins/miq_web_server_runner_mixin.rb:29:in `block in start_rails_server' /Users/kuldip.nanda/projects/easy/githubfork/manageiq/app/models/mixins/miq_web_server_runner_mixin.rb:27:in `tap' /Users/kuldip.nanda/projects/easy/githubfork/manageiq/app/models/mixins/miq_web_server_runner_mixin.rb:27:in `start_rails_server' /Users/kuldip.nanda/projects/easy/githubfork/manageiq/app/models/mixins/miq_web_server_runner_mixin.rb:16:in `run' /Users/kuldip.nanda/projects/easy/githubfork/manageiq/app/models/miq_worker/runner.rb:96:in `start' /Users/kuldip.nanda/projects/easy/githubfork/manageiq/lib/workers/bin/run_single_worker.rb:128:in `<main>' ERROR: An unhandled error has occurred: Address already in use - bind(2) for "0.0.0.0" port 5000. See log for details.
Please can anyone suggest/ any pointers how to resolve it
bin/webpack --watch --followin one terminal window all the time (first time it take 2 around minutes to finish). This automatically compiles js changes in couple of seconds after your changes. Make sure you have node 14.
I want to reload the datatable after the creation or deletion in any page.
After the delete task is added to queue, this method should be callled, and it will render the message.
I want to reload the datatable only in show_list page after the message is shown.
Can anybody help me on this issue?