Created attachment 1014180 [details] err Description of problem: Version-Release number of selected component (if applicable): 5.4.0.0.19.20150410165622_ad23806 How reproducible: 100% Steps to Reproduce: 1. Create a catalog item of type orchestration and click on order 2. Just click on submit (do not add any details). 3. Actual results: Error during 'Provisioning': undefined method `match' for nil:NilClass displayed on UI. see attached screenshot Expected results: Additional info: evm.log: [----] I, [2015-04-14T02:59:34.123980 #2046:4d9ea0] INFO -- : MIQ(MiqServer.heartbeat) Heartbeat [2015-04-14 06:59:34 UTC]...Complete [----] I, [2015-04-14T02:59:34.134356 #2046:4d9ea0] INFO -- : MIQ(MiqServer.populate_queue_messages) Fetched 1 miq_queue rows for queue_name=ems_1, wcount=5, priority=200 [----] E, [2015-04-14T02:59:38.658802 #2309:47fea0] ERROR -- : MIQ(catalog_controller-dialog_form_button_pressed): Error during 'Provisioning': undefined method `match' for nil:NilClass [----] I, [2015-04-14T02:59:39.020721 #2305:d1feac] INFO -- : MIQ(ScheduleWorker.do_work) Number of scheduled items to be processed: 6. [----] I, [2015-04-14T02:59:39.091274 #2305:d1feac] INFO -- : MIQ(MiqQueue.put) Message id: [39539], id: [], Zone: [default], Role: [], Server: [77f583fa-e0cf-11e4-a26f-fa163e49ce88], Ident: [generic], Target id: [], Instance id: [], Task id: [], Command: [MiqDbConfig.log_statistics], Timeout: [600], Priority: [90], S
Can you please provide the orchestration template you are using to create this issue? Was the dialog modified after creation? I am guessing not but would be good to verify. Bill - My guess here is the dialog is passing a nil because nothing was entered into the field and if that is the case we can work with eclarizi on this issue but would be good to do some validation first.
Milan, This has been resolved by your recent change in DialogFieldTextBox#validate method when the value is nil. Please provide your commit link and close this bug.
manageiq.git master: 2b44e891e05c13b4cb819c5a9e3e016c7dfb3013 *** This bug has been marked as a duplicate of bug 1206675 ***