Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(fleet) fix minor issues in the installer bootstrap #25267

Merged
merged 1 commit into from
Apr 30, 2024

Conversation

arbll
Copy link
Member

@arbll arbll commented Apr 30, 2024

Two issues discovered during the rollout:

  • /tmp mounted as noexec => this PR moves the bootstraped installer to a tmp under /opt/datadog-installer
  • some customers are running the install script in a loop, we need to avoid re-bootstraping everytime (and later re-installing)

Two issues discovered during the rollout:
- `/tmp` mounted as `noexec` => this PR moves the bootstraped installer to a tmp under `/opt/datadog-installer`
- some customers are running the install script in a loop, we need to avoid re-bootstraping everytime (and later re-installing)
@arbll arbll requested a review from a team as a code owner April 30, 2024 14:22
@arbll arbll added qa/done Skip QA week as QA was done before merge and regressions are covered by tests changelog/no-changelog team/fleet-automation labels Apr 30, 2024
@pr-commenter
Copy link

pr-commenter bot commented Apr 30, 2024

Test changes on VM

Use this command from test-infra-definitions to manually test this PR changes on a VM:

inv create-vm --pipeline-id=33254649 --os-family=ubuntu

@arbll arbll merged commit e8dacca into 7.54.0-installer-0.0.x Apr 30, 2024
137 of 160 checks passed
@arbll arbll deleted the arbll/installer-rollout-2 branch April 30, 2024 15:03
arbll added a commit that referenced this pull request May 11, 2024
* fix(installer): Use gcr.io by default instead of public.ecr.aws (#25255)

* (fleet) fix minor issues in the installer bootstrap (#25267)

Two issues discovered during the rollout:
- `/tmp` mounted as `noexec` => this PR moves the bootstraped installer to a tmp under `/opt/datadog-installer`
- some customers are running the install script in a loop, we need to avoid re-bootstraping everytime (and later re-installing)

* (fleet) use rootTmpDir for both MkdirTemp in the bootstrap

* (fleet) use actual package size to check if we have enough disk space

This PR uses the changes in DataDog/datadog-packages#11 to properly compute the required disk space to install a package. Previously we were requiring 3GiB for any package.

* purge

* update test

* pass test

* properly remove all with go

* remove noisy warn

* (fleet) fix a warn log in telemetry

```
2024/05/03 08:04:57 Datadog Tracer v1.61.0 WARN: ddtrace/tracer: deprecated config WithServiceName should not be used with `WithService` or `DD_SERVICE`; integration service name will not be set.
```

* (fleet) default to US1 for the telemetry website when DD_SITE isn't set

* fix missing bootstrap

* quick fix

---------

Co-authored-by: Baptiste Foy <baptiste.foy@datadoghq.com>
Co-authored-by: Raphael Gavache <raphael.gavache@datadoghq.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/no-changelog qa/done Skip QA week as QA was done before merge and regressions are covered by tests team/fleet-automation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant