Rollup index pattern error: must match one rollup index - #56732

Closes: #32765

Summary

Steps to reproduce:

1. Creating a new Rollup Job:
   • Open the Stack Management page and navigate to Elasticsearch -> Rollup Jobs;
   • Create a new Rollup Job (for my example I've created a rollup index pattern with name rollup-game-of-thrones by game-of-thrones index pattern);
   • Wait until data will be indexed (you can use 1m interval/delay to reduce time of indexing).
2. Creating a new Rollup Index Pattern:
   • Open Kibana -> Index patterns;
     Important: please don't refresh page after step #1 (Creating a new Rollup Job)
   • Create a new index pattern by Rollup Index Pattern:
     
   • type your Rollup Index in Index Pattern field;
     

Expected Result:

1. Next Step button should be enabled
2. Index Pattern should be valid. No error messages

Root cause analysis:

I found a problem in the RollupIndexPatternCreationConfig class. We are currently creating a new instance of this class only from the add method in IndexPatternCreationManager. This happens only once during a user session, because now we call it from the setup hook of rollup plugin, see src/legacy/core_plugins/management/public/np_ready/plugin.ts.

Now let's return back to /rollup_index_pattern_creation_config.js file and go to constructor function. Here we run the asynchronous method setRollupIndices, which was supposed to fill the internal fields of rollupIndicesCapabilities and rollupIndices. It happens only once and if the user created a new Rollup Index without refreshing the page, it is not available.

@cjcenizal I've moved setRollupIndices into getIndexPatternCreationOption method and looks like now all works fine. But I think instead of using constructor for IndexPatternCreationConfig we should implement 2 additional setup/start methods in future.

Checklist

• This was checked for cross-browser compatibility, including a check against IE11
• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for keyboard-only and screenreader accessibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately
• This includes a feature addition or change that requires a release note and was labeled appropriately