Skip to content
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.

fleetctl list-unit-files not fully populated for global units #1072

Open
bcwaldon opened this issue Dec 19, 2014 · 1 comment
Open

fleetctl list-unit-files not fully populated for global units #1072

bcwaldon opened this issue Dec 19, 2014 · 1 comment
Labels
kind/bug

Comments

@bcwaldon
Copy link
Contributor

I started a global unit ping.service in a three-node cluster:

$ fleetctl list-unit-files
UNIT            HASH    DSTATE      STATE   TARGET
ping.service    a5e03d5 launched    -       -

$ fleetctl list-units
UNIT            MACHINE                     ACTIVE  SUB
ping.service    c5bb3cdf.../172.17.8.102    active  running
ping.service    d368d34e.../172.17.8.103    active  running
ping.service    f4b6d7de.../172.17.8.101    active  running

Note that all three machines are running ping.service, but the DSTATE and TARGET columns are empty. We clearly cannot use the same approach as non-global units, but we can make an attempt:

$ fleetctl list-unit-files
UNIT            HASH    DSTATE      STATE       TARGET
ping.service    a5e03d5 launched    launched(3) global
other.service   d368d34 loaded      loaded      f4b6d7de.../172.17.8.101
@bcwaldon bcwaldon added the bug label Dec 19, 2014
@bcwaldon bcwaldon added this to the v0.10.0 milestone Dec 19, 2014
@bcwaldon bcwaldon mentioned this issue Jan 7, 2015
Merged
@bcwaldon bcwaldon removed this from the v0.10.0 milestone Apr 13, 2015
wuqixuan pushed a commit to wuqixuan/fleet that referenced this issue Jun 26, 2015
fleetctl: list-unit-files fully populated for global units
fe4d0f2 
Now, fleetctl list-unit-files command can show exact number
of the machines running the unit in STATE column as below:

localhost # fleetctl list-unit-files
UNIT                    HASH    DSTATE          STATE           TARGET
world_glob.service      66439c2 launched        launched(2)     global

Fixes coreos#1072
@wuqixuan wuqixuan mentioned this issue Jun 26, 2015
Closed
wuqixuan pushed a commit to wuqixuan/fleet that referenced this issue Jul 6, 2015
fleetctl: list-unit-files fully populated for global units
cbef098 
Now, fleetctl list-unit-files command can show exact number
of the machines running the unit in STATE column as below:

localhost # fleetctl list-unit-files
UNIT                    HASH    DSTATE          STATE           TARGET
world_glob.service      66439c2 launched        launched(2)     global

Fixes coreos#1072
@jonboulle jonboulle added kind/bug and removed bug labels Sep 24, 2015
@zeisss
Copy link
Contributor

zeisss commented Oct 8, 2015

How would this look like, when one machine has a failed state? So generally, how does this behave with mixed states on different machines?

dongsupark pushed a commit to dongsupark/fleet that referenced this issue Apr 27, 2016
fleetctl: list-unit-files fully populated for global units
16e5ce5 
Now, fleetctl list-unit-files command can show exact number
of the machines running the unit in STATE column as below:

localhost # fleetctl list-unit-files
UNIT                    HASH    DSTATE          STATE           TARGET
world_glob.service      66439c2 launched        launched(2)     global

Originally written by wuqixuan <[email protected]>
Supersedes coreos#1272
Fixes: coreos#1072
dongsupark pushed a commit to dongsupark/fleet that referenced this issue Apr 29, 2016
fleetctl: list-unit-files fully populated for global units
75ebc39 
Now, fleetctl list-unit-files command can show exact number
of the machines running the unit in STATE column as below:

localhost # fleetctl list-unit-files
UNIT                    HASH    DSTATE          STATE           TARGET
world_glob.service      66439c2 launched        launched(2)     global

Originally written by wuqixuan <[email protected]>
Supersedes coreos#1272
Fixes: coreos#1072
dongsupark pushed a commit to dongsupark/fleet that referenced this issue May 2, 2016
fleetctl: list-unit-files fully populated for global units
02cbb7e 
Now, fleetctl list-unit-files command can show exact number
of the machines running the unit in STATE column as below:

localhost # fleetctl list-unit-files
UNIT                    HASH    DSTATE          STATE           TARGET
world_glob.service      66439c2 launched        launched(2)     global

Originally written by wuqixuan <[email protected]>
Supersedes coreos#1272
Fixes: coreos#1072
@dongsupark dongsupark mentioned this issue May 2, 2016
Open
dongsupark pushed a commit to dongsupark/fleet that referenced this issue May 2, 2016
fleetctl: list-unit-files fully populated for global units
37e59a2 
Make "fleetctl list-unit-files" able to show exact number
of the machines running the unit in STATE column as below:

localhost # fleetctl list-unit-files
UNIT                    HASH    DSTATE          STATE           TARGET
world_glob.service      66439c2 launched        launched(2)     global

Originally written by wuqixuan <[email protected]>
Supersedes coreos#1272
Fixes: coreos#1072
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
kind/bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@zeisss @bcwaldon @jonboulle