Bug ID 960298
Summary YaST service manager can't enable foo@.service
Classification openSUSE
Product openSUSE Tumbleweed
Version 2015*
Hardware Other
OS openSUSE 13.2
Status NEW
Severity Normal
Priority P5 - None
Component YaST2
Assignee yast2-maintainers@suse.de
Reporter suse-beta@cboltz.de
QA Contact jsrain@suse.com
Found By Beta-Customer
Blocker ---

YaST service manager can't enable foo@.service (service files with parameters,
for example openvpn@.service

If I select "openvpn@", click "Start/Stop" to start it and then "OK" to
actually start it, I get an error message (translated back from german)

    Writing the configuration failed:
    openvpn@ can't be enabled. Failed to get properties: 
        Unit name openvpn@.service is not valid.

    Would you like to continue editing?

    [Continue] [Cancel]


Expected behaviour: When someone tries to enable a foo@ service, ask for the
parameter to use (= display an input field) and then enable
foo@<userinput>.service.


(not attaching any logs because this is very obvious and easy to reproduce)


You are receiving this mail because: