As mentioned in the latter issue, this can be reproduced by trying to update from Okta 2.11.0 to 2.12.0.
On these cases a rollover should be performed by Fleet on upgrade.
Current workaround is to update the package using the install API with ignoreMappingUpdateErrors=true and rollover the data stream. For example for a local environment and the logs-okta.system-69312 data stream:
curl -X POST "https://localhost:5601/api/fleet/epm/packages/okta/2.12.0?ignoreMappingUpdateErrors=true" -H "Content-Type: application/json" -H "kbn-xsrf: true" -u elastic:changeme -k
curl -X POST "https://localhost:9200/logs-okta.system-69312/_rollover" -k -u elastic:changeme
Same issue as reported in https://github.com/elastic/kibana/issues/183496 for custom integrations is happening also for integrations distributed in packages, as reported in https://github.com/elastic/integrations/issues/10972.
As mentioned in the latter issue, this can be reproduced by trying to update from Okta 2.11.0 to 2.12.0.
On these cases a rollover should be performed by Fleet on upgrade.
Current workaround is to update the package using the install API with
ignoreMappingUpdateErrors=true
and rollover the data stream. For example for a local environment and thelogs-okta.system-69312
data stream: