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

vSphere Tags not working #1258

Open
gojeaqui opened this issue Jun 10, 2024 · 4 comments
Open

vSphere Tags not working #1258

gojeaqui opened this issue Jun 10, 2024 · 4 comments

Comments

@gojeaqui
Copy link

gojeaqui commented Jun 10, 2024

Hello,

I found this documentation: https://github.com/openshift/machine-api-operator/blob/master/docs/user/vsphere/tags.md to apply tags to the VMs.
In the doc it says:

machinesets may also be defined to attach tags to machines created by the machineset.

But when we put the tagIDs into the MachineSet the behaviour we are seeing is that the created Machine does not have the tagIDs.
Its like they were stripped in the process of creating the machine.
And this is the output of the Machine API Controller:

[openshift@PLBASTIONOCP1 ocp4-lh]$ oc logs machine-api-controllers-5f5465cd7f-f6rrc -c machine-controller
...
I0610 14:29:42.197854       1 warning_handler.go:65] KubeAPIWarningLogger "msg"="providerSpec.value: Unsupported value: \"tagIDs\": Unknown field (tagIDs) will be ignored"
...

About the cluster:

[openshift@PLBASTIONOCP1 ocp4-lh]$ oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.14.25   True        False         9d      Cluster version is 4.14.25
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 9, 2024
@gojeaqui
Copy link
Author

Is no one looking at the issues?

@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 27, 2024
@gojeaqui
Copy link
Author

/remove-lifecycle rotten

@openshift-ci openshift-ci bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants