OpenShift installer on OpenStack does not provide the userTags field to add custom tags to created virtual machines
wkulhanek opened this issue · 4 comments
Since my bugzilla (https://bugzilla.redhat.com/show_bug.cgi?id=1868517) got closed for some reason... and since I've been asked to file an issue:
Description of problem:
Every OpenShift release including 4.5(.5).
Every Cloud Platform (AWS, Azure, GCP) has a customization field "userTags" - for example "platform.aws.userTags" for the install-config.yaml.
OpenStack does not - which makes it really hard to find the VMs that have been created as part of cluster.
Actual results:
Tried adding "platform.openstack.userTags" to the install-config.yaml. Nothing happened.
Expected results:
Tags set on the VMs in OpenStack
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
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
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen
.
Mark the issue as fresh by commenting/remove-lifecycle rotten
.
Exclude this issue from closing again by commenting/lifecycle frozen
./close
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.