-
Notifications
You must be signed in to change notification settings - Fork 302
Global unit not starting with multiple MachineMetadata #1411
Comments
If you wish to schedule your unit on all your machines described above, just use this metadata: [X-Fleet]
MachineMetadata=rank=pet
MachineMetadata=rank=cattle
Global=true It will create following condition:
As for your current metadata: [X-Fleet]
MachineMetadata=role=api
MachineMetadata=rank=pet
Global=true it will create following condition:
If you create this unit: [X-Fleet]
MachineMetadata=role=api
MachineMetadata=rank=pet
MachineMetadata=rank=cattle
Global=true it will produce following condition:
|
Thanks for the clarification, you should add this to the docs. Why does it automatically [X-Fleet]
MachineMetadata="role=api" "rank=pet"
Global=true And in my case, there's a problem with this solution: [X-Fleet]
MachineMetadata=rank=pet
MachineMetadata=rank=cattle
Global=true I have other machines with What I'm doing right now is just assigning Hope this makes sense. |
@jeremejevs Probably we can add new feature which will make your life easier and preserve backward compatibility: #1368 As for the documentation, we will improve it soon. |
Yeah, I get that changing the behavior isn't an option, was just wondering about the rationale. Maybe some simple expression format could be developed for |
@jeremejevs it is better to post your thoughts in this ticket #1368 |
@jeremejevs NP |
I have a cluster looking like this:
And I have a service which looks like this:
It works fine, if I remove either one of the
MachineMetadata
and start it withfleetctl
, but if I leave both in, then... nothing happens. The unit does get submitted, but it doesn't start on any machine,fleetctl list-units
is empty andjournalctl -u my.service
is empty too.Is this a bug or just not supported?
The text was updated successfully, but these errors were encountered: