Plugins » Katello

Description¶

The LoadingState class component in webpack/components/LoadingState/LoadingState.js sets a setTimeout in componentDidMount but never clears it in componentWillUnmount. This causes a React warning ("Cannot update state on an unmounted component") when the component unmounts before the timeout fires.

This bug was introduced in commit 4c976ff (Fixes #24288 - add a delay for loading state) and has existed since then. It was not caught until #39307 (Migrate SetOrganization component from PF3 to PF5, PR #11734) added tests that unmount a component wrapping LoadingState quickly enough to trigger the warning. PR #11734 did not modify LoadingState itself.

Impact¶

The test environment (global_test_setup.js) promotes console.error to thrown errors, so the React unmount warning becomes a test failure. This breaks 4 of 5 tests in SetOrganization.test.js in CI (katello-master-source-release): 2 direct failures from the unmount error, plus 2 cascading failures.

Steps to Reproduce¶

1. Run: bundle exec npm run test:plugins katello
2. Observe SetOrganization.test.js failures
3. Root cause: LoadingState unmount warning thrown as error

Root Cause¶

webpack/components/LoadingState/LoadingState.js lines 15-18:

componentDidMount() {
  setTimeout(() => {
    this.setState({ render: true });
  }, this.props.timeout);
}

The timeout ID is not stored, and there is no componentWillUnmount to clear it.

CI Log¶

See katello-master-source-release build logs from 2026-05-19. 1 suite failed (SetOrganization.test.js), 158 suites passed; 4 tests failed, 956 passed.