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

Fix: Support vmtoolsd from $PATH #368

Merged
merged 3 commits into from
Mar 5, 2024

Conversation

4ch3los
Copy link
Contributor

@4ch3los 4ch3los commented Mar 1, 2024

What this PR does / why we need it:

This PR adjusts the osp for flatcar on VMware cloud director. We now use the vmtoolsd binary from Path by default and only fallback to the old path if it does not exist. This is needed as newer flatcar releases have moved the binary to another location.

What type of PR is this?

/kind bug

Special notes for your reviewer:

Backwards compatibility is kept by falling back to the old path if binary was not found in $PATH

Does this PR introduce a user-facing change? Then add your Release Note here:

Fixes the network setup on vmware cloud director with flatcar, pool ips and the latest images 

Documentation:

NONE

…tools to another location

Signed-off-by: Kai Fink <kai.fink@yahoo.de>
@kubermatic-bot kubermatic-bot added kind/bug Categorizes issue or PR as related to a bug. release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. docs/none Denotes a PR that doesn't need documentation (changes). sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Mar 1, 2024
@kubermatic-bot
Copy link
Contributor

Hi @4ch3los. Thanks for your PR.

I'm waiting for a kubermatic member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kubermatic-bot kubermatic-bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 1, 2024
@kron4eg
Copy link
Member

kron4eg commented Mar 1, 2024

It's a matter of taste of course, I'd just add /usr/share/oem/bin/ to the $PATH and run vmtoolsd without pathprefix

Signed-off-by: Kai Fink <kai.fink@yahoo.de>
@kron4eg
Copy link
Member

kron4eg commented Mar 5, 2024

/cc @ahmedwaleedmalik

Copy link
Member

@ahmedwaleedmalik ahmedwaleedmalik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 5, 2024
@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahmedwaleedmalik

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 5, 2024
@ahmedwaleedmalik
Copy link
Member

pull-operating-system-manager-yamllint

./deploy/osps/default/osp-flatcar.yaml
  58:1      error    trailing spaces  (trailing-spaces)

/lgtm cancel

@4ch3los can you please take a look

@kubermatic-bot kubermatic-bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 5, 2024
Signed-off-by: Kai Fink <kai.fink@yahoo.de>
@kron4eg
Copy link
Member

kron4eg commented Mar 5, 2024

/test pull-operating-system-manager-yamllint

@kron4eg
Copy link
Member

kron4eg commented Mar 5, 2024

/lgtm

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 5, 2024
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: d8b24ff54905d51786c65f61b53a1b936c1d35c1

@kubermatic-bot kubermatic-bot merged commit e31b599 into kubermatic:main Mar 5, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. docs/none Denotes a PR that doesn't need documentation (changes). kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants