github-actions[bot] commented on issue #14715:
URL: https://github.com/apache/cloudstack/issues/14715#issuecomment-6980112451

   > [!WARNING]
   > threat detection engine error
   > The threat detection engine encountered an error and could not complete 
analysis. This is a tooling failure, not a security finding.
   >
   > <!-- gh-aw-threat-engine-error -->
   >
   > <details>
   > <summary>What happened</summary>
   >
   > The threat detection engine failed to produce results.
   >
   > Review the [workflow run 
logs](https://github.com/apache/cloudstack/actions/runs/44314035050) for 
details.
   >
   > </details>
   
   ## 🎯 Triage report
   
   `registerTemplate` and `registerIso` accept a `url` up to 2048 characters, 
but the `vm_template.url` column is `VARCHAR(1024)`. URLs of 1025 to 2048 
characters pass API validation and then fail when the row is written, returning 
a generic internal error. The reporter hit this with a roughly 1700-character 
presigned S3 URL. The suggested fixes are to widen the column to 2048 in an 
upgrade script, or to lower the API parameter length to 1024 so the error names 
the limit.
   
   ### 📊 Assessment
   
   | Dimension | Value | Reasoning |
   | --- | --- | --- |
   | **Type** | type:bug | Mismatch between API validation and the DB column 
leads to a failure with a poor error |
   | **Component** | component:api, component:templates | Parameter validation 
in register commands; template table schema |
   | **Severity** | Severity:Minor | Only URLs of 1025 to 2048 characters fail; 
shorter URLs (e.g. long-lived credentials) work |
   | **Labels** | type:bug, component:api, component:templates, Severity:Minor 
| Based on the issue text and the reporter's source references |
   | **Coding agent** | Suitable | Fix is specified: widen the column in an 
upgrade script, or lower the parameter length |
   
   ### 🔗 Similar issues
   
   - #8669 (related, closed) — the original URL length failure at the old 
255-character limit; fixed by #8675 in 4.19.1
   - #13916 (related) — direct download template size is incorrect; same 
template registration path
   
   <details>
   <summary>💡 Notes and suggestions</summary>
   
   - Reproduction: pad a template URL to between 1025 and 2048 characters, then 
call `registerTemplate`. Compare with a URL of 1024 characters or fewer.
   - Check the widening option against the upgrade path. The sibling tables 
already use 2048, so widening would make the schema consistent.
   - Check whether `registerIso` has the same mismatch; the reporter's source 
reading covers it.
   
   </details>
   
   > Triage by Copilot (automated)
   
   > Generated by [Daily Issue 
Triage](https://github.com/apache/cloudstack/actions/runs/44314035050) · 
copilot · haiku55 · \~4 AIC · ⊞ 3.8K · 
[â—·](https://github.com/search?q=repo%3Aapache%2Fcloudstack+%22gh-aw-workflow-call-id%3A+apache%2Fcloudstack%2Fdaily-issue-triage%22&type=issues)
   
   <details>
   <summary><sub>Add this agentic workflow to your repo</sub></summary>
   
   To install this agentic workflow, run
   
   ```
   gh aw add 
githubnext/agentics/workflows/daily-issue-triage.md@139fa09ef17cde4135e696ff8e7af09bc5ddfa6e
   ```
   
   </details>
   
   <!-- gh-aw-workflow-call-id: apache/cloudstack/daily-issue-triage -->
   
   <!-- gh-aw-agentic-workflow: Daily Issue Triage, engine: copilot, model: 
claude-haiku-5.5, id: 44314035050, workflow_id: daily-issue-triage, run: 
https://github.com/apache/cloudstack/actions/runs/44314035050 -->
   
   <!-- gh-aw-execution: 
{"version":1,"repo_id":"9759448","repository":"apache/cloudstack","aw_workflow_id":"daily-issue-triage","run_id":"44314035050","run_attempt":"1","run_url":"https://github.com/apache/cloudstack/actions/runs/44314035050","publishing_job":{"key":"safe_outputs","check_run_id":"134838345283"}}
 -->


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to