Project

General

Profile

Actions

Bug #37447

closed

Getting "TypeError: Cannot read properties of undefined (reading '0')" error when trying to rerun a REX job

Added by Karolína Małyjurková 8 months ago. Updated 4 months ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Found in Releases:

Description

Description of problem:

Getting the following error in the Web UI when trying to rerun a REX job
~~
TypeError: Cannot read properties of undefined (reading '0') in I in div in div in m in v in t in t in c in f in d in div in l in p in y in t in n in a in C in s in div in b in IntlProvider in I18nProviderWrapper(b) in d in StoreProvider(I18nProviderWrapper(b)) in DataProvider(StoreProvider(I18nProviderWrapper(b)))
~~

In the production log we saw 404 not found.
~~
Started GET "/ui_job_wizard/job_invocation?id=188" for xx.xx.xx.xx
Processing by UiJobWizardController#job_invocation as JSON
Parameters: {"id"=>"188"}
Rendered common/404.html.erb within layouts/application (Duration: 8.0ms | Allocations: 8402)
Rendered layouts/base.html.erb (Duration: 50.2ms | Allocations: 17979)
Rendered layout layouts/application.html.erb (Duration: 70.1ms | Allocations: 38762)
Completed 404 Not Found in 98ms (Views: 70.7ms | ActiveRecord: 4.8ms | Allocations: 47911)
~~

How reproducible:
Easy

Steps to Reproduce:
1. Login as an admin user. Set the current location to "Any Location"
2. Clone the "Run Command - Script Default" job template. Assign the current organizations. Don't assign any locations.
3. Run a command job by using the cloned job template.
4. Set the current location to one of the location.
5. In the job page, Click "Rerun" button

Actual results:
Web UI shows the following error:
~~
TypeError: Cannot read properties of undefined (reading '0') in I in div in div in m in v in t in t in c in f in d in div in l in p in y in t in n in a in C in s in div in b in IntlProvider in I18nProviderWrapper(b) in d in StoreProvider(I18nProviderWrapper(b)) in DataProvider(StoreProvider(I18nProviderWrapper(b)))
~~

Expected results:
Web UI should handle the 404 not found response and print out a meaningful error message to the end user.

Additional info:
Unset the current location allowed the page to view properly.

Actions #1

Updated by The Foreman Bot 8 months ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_remote_execution/pull/894 added
Actions #2

Updated by Karolína Małyjurková 8 months ago

  • Status changed from Ready For Testing to Assigned
Actions #3

Updated by The Foreman Bot 4 months ago

  • Status changed from Assigned to Ready For Testing
Actions #4

Updated by The Foreman Bot 4 months ago

  • Fixed in Releases foreman_remote_execution-13.2.5 added
Actions #5

Updated by Karolína Małyjurková 4 months ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF