Bug 1313292

Summary:

systemctl service wildcards do not capture services properly

Product:

[Fedora] Fedora

Reporter:

clime

Component:

systemd-ui

Assignee:

Lennart Poettering <lpoetter>

Status:

CLOSED EOL

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

unspecified

Docs Contact:

Priority:

unspecified

Version:

CC:

kay, lpoetter, mschmidt, tadej.j, zbyszek

Target Milestone:

---

Target Release:

---

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2016-12-20 19:09:06 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Attachments:

Description	Flags
copr-dist-git service file	none

Description clime 2016-03-01 10:46:09 UTC

root@coprbox /home/clime/6D-RAW $ systemctl list-units --all | grep copr
  copr-backend-jobgrab.service                                                                                                                          loaded    inactive dead      Copr Backend service, Job Grabber component
  copr-backend-log.service                                                                                                                              loaded    inactive dead      Copr Backend service, Log Handler component
  copr-backend-vmm.service                                                                                                                              loaded    inactive dead      Copr Backend service, Virtual Machine Management component
● copr-backend.service                                                                                                                                  loaded    failed   failed    Copr Backend service, Workers controller
  copr-dist-git.service                                                                                                                                 loaded    inactive dead      copr aux service to import srpm into dist-git
  copr-mock-frontend.service                                                                                                                            loaded    inactive dead      COPR mock for the frontend component
root@coprbox /home/clime/6D-RAW $ systemctl start copr-*.service
root@coprbox /home/clime/6D-RAW $ systemctl list-units --all | grep copr
  copr-backend-jobgrab.service                                                                                                                          loaded    active   running   Copr Backend service, Job Grabber component
  copr-backend-log.service                                                                                                                              loaded    active   running   Copr Backend service, Log Handler component
  copr-backend-vmm.service                                                                                                                              loaded    active   running   Copr Backend service, Virtual Machine Management component
  copr-backend.service                                                                                                                                  loaded    active   running   Copr Backend service, Workers controller
  copr-dist-git.service                                                                                                                                 loaded    inactive dead      copr aux service to import srpm into dist-git
  copr-mock-frontend.service                                                                                                                            loaded    inactive dead      COPR mock for the frontend component


copr-dist-git.service is still "inactive dead" after running systemctl start copr-*.service

I would expect it to be failed/failed or active/running. I checked its journalctl logs and according to them it does not get any start signal.

If I don't use wildcard, then the service starts properly:

root@coprbox /home/clime/6D-RAW $ systemctl start copr-dist-git.service
root@coprbox /home/clime/6D-RAW $ systemctl list-units --all | grep copr
  session-1022.scope                                                                                                                                    loaded    active   running   Session 1022 of user copr
  copr-backend-jobgrab.service                                                                                                                          loaded    active   running   Copr Backend service, Job Grabber component
  copr-backend-log.service                                                                                                                              loaded    active   running   Copr Backend service, Log Handler component
  copr-backend-vmm.service                                                                                                                              loaded    active   running   Copr Backend service, Virtual Machine Management component
  copr-backend.service                                                                                                                                  loaded    active   running   Copr Backend service, Workers controller
  copr-dist-git.service                                                                                                                                 loaded    active   running   copr aux service to import srpm into dist-git
  copr-mock-frontend.service                                                                                                                            loaded    inactive dead      COPR mock for the frontend component

It might be some silly mistake of mine but as there is no logging of systemctl start/stop commands is not very present in this case (I was also looking for --vebose but not such option exists), it is hard to tell. It would nice if it outputed which services it is starting in which order.

Comment 1 clime 2016-03-05 18:43:30 UTC

Sorry for the broken formatting.

Comment 2 clime 2016-03-09 08:38:23 UTC

Created attachment 1134418 [details]
copr-dist-git service file

Comment 3 clime 2016-03-09 08:43:21 UTC

Here is a cleaner example:

$ systemctl list-units 'copr-dist-git.service'
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

$ systemctl start 'copr-dist-git*' && systemctl list-units 'copr-dist-git.service'
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

$ systemctl start 'copr-dist-git.service' && systemctl list-units 'copr-dist-git.service'
UNIT                  LOAD   ACTIVE SUB     DESCRIPTION
copr-dist-git.service loaded active running copr aux service to import srpm into dist-git

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

---

You can see that systemctl start 'copr-dist-git*' did not start the service but systemctl start 'copr-dist-git.service' did. Not sure what is so special about copr-dist-git.service that wildcards work differently for it than for e.g. copr-backend.service (see the first post).

Comment 4 Fedora End Of Life 2016-11-24 15:51:49 UTC

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2016-12-20 19:09:06 UTC

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.