CRTX-257648 - ESXi crond subtype-1 remove invalid outcome value - #45617
CRTX-257648 - ESXi crond subtype-1 remove invalid outcome value#45617akshotiamit-pa wants to merge 5 commits into
Conversation
…apture names The parsing rule built RE2 named-capture groups from changedValues[].name. Confluence audit field names contain dots (e.g. audit.logging.change.space.content.mode), which RE2 rejects in group names -> 'invalid named capture' runtime error. Add \. to the replex sanitize alternation so dots become underscores. Verified on tenant xdr-eu-2006800998707: the sole non-empty failing row carried a dotted name.
🤖 AI-Powered Code Review AvailableYou can leverage AI-powered code review to assist with this PR! Available Commands:
|
akshotiamit-pa
added
docs-approved
bypass.url
marketplace-ai-reviewer
removed
the
ready-for-ai-review
|
🤖 Analysis started. Please wait for results... |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
akshotiamit-pa
added
ready-for-pipeline-running
marketplace-ai-reviewer
removed
the
ready-for-ai-review
|
🤖 Analysis started. Please wait for results... |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This PR was automatically updated by a GitHub Action
To stop automatic version bumps, add the |
|
Validate summary Verdict: PR can be force merged from validate perspective? ✅ |
🔍 AI Triage Report AvailableAn automated triage report has been generated for this pipeline. Status:
|
akshotiamit-pa
added
research-mapping-approve
marketplace-ai-reviewer
removed
the
ready-for-ai-review
|
🤖 Analysis started. Please wait for results... |
🤖 AI Review DisclaimerThis review was generated by an AI-powered tool and may contain inaccuracies. Please be advised, and we extend our sincere apologies for any inconvenience this may cause. |
marketplace-ai-reviewer
left a comment
marketplace-ai-reviewer
left a comment
There was a problem hiding this comment.
Thank you for your contribution! No issues found. Great work! 👍
@marketplace-ai-reviewer, @akshotiamit-pa please review and approve the results generated by the AI Reviewer by responding 👍 on this comment.
3 participants
CRTX-257648 (B1)
ESXi crond subtype-1 (
event_type=150, event_sub_type=1, _product=Esxi) set the storyoutcomecolumn to the literalcrond process start, outside the allowed enum {SUCCESS, FAILED, UNKNOWN, NULL}, in 100% of rows.Root cause: the crond block set
xdm.event.operation_sub_type = "crond process start", and the virtualization story model surfacesoperation_sub_typeinto theoutcomecolumn. A crond start line reports no result, so the enum-correct value is NULL.Fix
Removed the
operation_sub_typeassignment for the crond block.xdm.event.operation = OPERATION_TYPE_PROCESS_STARTandsource.process.name = crondare retained, so process-start semantics and crond identity are preserved;outcomebecomes NULL.Verified on xdr-us-85898001 (read-only)
crond process start; 0 of 533,204 rows (3d, all distinct commands) contain any success/failure result.Satisfies AC1 + AC6. B2 (name/path) was fixed previously and is untouched.