Drop redundant rootPath from fleet installer config#46719
Conversation
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
26 successful checks with minimal change (< 2 KiB)
On-wire sizes (compressed)
|
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: a88881b Optimization Goals: ✅ No significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | -2.80 | [-5.79, +0.18] | 1 | Logs |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | ddot_metrics_sum_cumulative | memory utilization | +0.52 | [+0.37, +0.67] | 1 | Logs |
| ➖ | ddot_metrics | memory utilization | +0.34 | [+0.11, +0.57] | 1 | Logs |
| ➖ | quality_gate_metrics_logs | memory utilization | +0.20 | [+0.00, +0.40] | 1 | Logs bounds checks dashboard |
| ➖ | quality_gate_idle_all_features | memory utilization | +0.18 | [+0.15, +0.22] | 1 | Logs bounds checks dashboard |
| ➖ | otlp_ingest_metrics | memory utilization | +0.15 | [-0.01, +0.30] | 1 | Logs |
| ➖ | quality_gate_logs | % cpu utilization | +0.01 | [-1.50, +1.51] | 1 | Logs bounds checks dashboard |
| ➖ | uds_dogstatsd_to_api_v3 | ingress throughput | +0.00 | [-0.12, +0.13] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.00 | [-0.42, +0.42] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.13, +0.12] | 1 | Logs |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.01 | [-0.10, +0.09] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | -0.02 | [-0.48, +0.44] | 1 | Logs |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | -0.05 | [-0.42, +0.32] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulativetodelta_exporter | memory utilization | -0.06 | [-0.29, +0.17] | 1 | Logs |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | -0.07 | [-0.11, -0.02] | 1 | Logs |
| ➖ | file_tree | memory utilization | -0.16 | [-0.21, -0.11] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | -0.17 | [-0.22, -0.13] | 1 | Logs bounds checks dashboard |
| ➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | -0.23 | [-0.28, -0.18] | 1 | Logs |
| ➖ | ddot_metrics_sum_delta | memory utilization | -0.31 | [-0.50, -0.12] | 1 | Logs |
| ➖ | docker_containers_memory | memory utilization | -0.33 | [-0.41, -0.26] | 1 | Logs |
| ➖ | otlp_ingest_logs | memory utilization | -0.34 | [-0.43, -0.24] | 1 | Logs |
| ➖ | ddot_logs | memory utilization | -0.53 | [-0.59, -0.47] | 1 | Logs |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | -0.81 | [-0.89, -0.73] | 1 | Logs |
| ➖ | docker_containers_cpu | % cpu utilization | -2.80 | [-5.79, +0.18] | 1 | Logs |
Bounds Checks: ✅ Passed
| perf | experiment | bounds_check_name | replicates_passed | links |
|---|---|---|---|---|
| ✅ | docker_containers_cpu | simple_check_run | 10/10 | |
| ✅ | docker_containers_memory | memory_usage | 10/10 | |
| ✅ | docker_containers_memory | simple_check_run | 10/10 | |
| ✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
| ✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
| ✅ | file_to_blackhole_1000ms_latency | lost_bytes | 10/10 | |
| ✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
| ✅ | file_to_blackhole_100ms_latency | lost_bytes | 10/10 | |
| ✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | |
| ✅ | file_to_blackhole_500ms_latency | lost_bytes | 10/10 | |
| ✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | |
| ✅ | quality_gate_idle | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_idle | memory_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_logs | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_logs | lost_bytes | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_logs | memory_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | cpu_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | lost_bytes | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | memory_usage | 10/10 | bounds checks dashboard |
Explanation
Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%
Performance changes are noted in the perf column of each table:
- ✅ = significantly better comparison variant performance
- ❌ = significantly worse comparison variant performance
- ➖ = no significant change in performance
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
CI Pass/Fail Decision
✅ Passed. All Quality Gates passed.
- quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
pkg/fleet/installer/config/config.go
Outdated
| // Set proper ownership and permissions for the file | ||
| fullPath := filepath.Join(rootPath, path) | ||
| if err := setFileOwnershipAndPermissions(ctx, fullPath, spec); err != nil { | ||
| if err := setFileOwnershipAndPermissions(ctx, filepath.Join(root.Name(), path), spec); err != nil { |
There was a problem hiding this comment.
❓ question
should setFileOwnershipAndPermissions use os.Root instead of filepath.Join ?
There was a problem hiding this comment.
@clarkb7 I've added a 2nd commit that I hope addresses your comment, esp.:
use
os.RootAPIs where possible instead of reconstructing full paths at call sites.
root.Chown()is not used as it requires numeric uid/gid:file.Chown()still handles the name lookup internally and requires a full path.
### What does this PR do? Remove the `rootPath` parameter from `FileOperation.apply()`, replacing `filepath.Join(rootPath, ...)` calls with `filepath.Join(root.Name(), ...)`. ### Motivation Address a trivial TODO, follow-up of #46592: once `root.RemoveAll()` replaced the last os-level `filepath.Join(rootPath, ...)` call, `rootPath`'s sole remaining purpose was feeding `setFileOwnershipAndPermissions`. `root.Name()` returns the equivalent value. ### Describe how you validated your changes Existing unit tests pass unchanged.
### What does this PR do? Pass `*os.Root` into `setFileOwnershipAndPermissions` and use `root.Chmod()` in place of `os.Chmod()`. ### Motivation Address review comment in #46719: use `os.Root` APIs where possible instead of reconstructing full paths at call sites. `root.Chown()` is not used as it requires numeric uid/gid: `file.Chown()` still handles the name lookup internally and requires a full path. ### Describe how you validated your changes Existing unit tests pass unchanged.
cf7906d to
b774baf
Compare
Files inventory check summaryFile checks results against ancestor cded3a15: Results for datadog-agent_7.77.0~devel.git.778.b774baf.pipeline.98033369-1_amd64.deb:Detected file changes:
|
What does this PR do?
rootPathparameter fromFileOperation.apply(), replacingfilepath.Join(rootPath, ...)calls withfilepath.Join(root.Name(), ...).*os.RootintosetFileOwnershipAndPermissionsand useroot.Chmod()in place ofos.Chmod(), but:root.Chown()is not used as it requires numeric uid/gid,file.Chown()still handles the name lookup internally and requires a full path.Motivation
os.RootAPI in fleet installer config #46592: onceroot.RemoveAll()replaced the last os-levelfilepath.Join(rootPath, ...)call,rootPath's sole remaining purpose was feedingsetFileOwnershipAndPermissions:root.Name()returns the equivalent value,os.RootAPIs where possible instead of reconstructing full paths at call sites.Describe how you validated your changes
Existing unit tests pass unchanged.