Bug 44672

Summary: cockpit в P10 не включает службу
Product: Branch p10 Reporter: Ахламов Петр <petr-akhlamov>
Component: cockpitAssignee: qa-team <qa-team>
Status: CLOSED NOTABUG QA Contact: qa-p10 <qa-p10>
Severity: normal    
Priority: P5 CC: amakeenk, slev
Version: не указана   
Hardware: x86_64   
OS: Linux   

Description Ахламов Петр 2022-12-18 01:38:32 MSK 
После установки cockpit в P10 и выполнения systemctl enable cockpit, systemd выдает ошибку:

The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
 
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.

И служба при запуске системы не включается, только вручную или хаком.
Comment 1 Alexander Makeenkov 2022-12-18 09:36:19 MSK 
Это не ошибка, сервис так реализован.

(Ответ для Ахламов Петр на комментарий #0)
> Possible reasons for having this kind of units are:
> • A unit may be started when needed via activation (socket, path, timer,
>   D-Bus, udev, scripted systemctl call, ...).

Попробуйте:
# systemctl enable cockpit.socket && reboot

И напишите сюда о результатах.
Comment 2 Ахламов Петр 2022-12-18 11:12:54 MSK 
Да, все работает.