Bug 1077886 - YaST2 HTTP Module does not identify http and https services correctly.
YaST2 HTTP Module does not identify http and https services correctly.
Status: RESOLVED DUPLICATE of bug 1076837
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: YaST2
Current
Other Other
: P5 - None : Major (vote)
: ---
Assigned To: E-mail List
Jiri Srain
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-01-28 23:44 UTC by John Shand
Modified: 2018-01-30 11:11 UTC (History)
4 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
kanderssen: needinfo? (mchandras)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Shand 2018-01-28 23:44:41 UTC
when i run the yast2 module for http server, it installs correctly, however, when it comes to opening ports it comes up with an error saying apache service not found or something like that.  you may need to change this to http and https instead of apache.
Comment 1 Josef Reidinger 2018-01-29 12:13:35 UTC
knut can you please check it, if it is result of firewalld transformation?
Comment 2 Knut Alejandro Anderssen González 2018-01-29 12:23:56 UTC
For SuSEFirewall2 apache2 was providing the definition of the service. 

As the yast2-http-server module modifies the definition of the service we were thinking in continue providing it by the apache2 package as apache2 and apache2-ssl.

So will request the opinion of the firewalld maintainer and from the security team.

In general we adapted our modules using the firewalld defined services when not touched by YaST, but deployed the services definition when touched, but of course that could create doubts about both services (http and apache2).
Comment 3 Knut Alejandro Anderssen González 2018-01-29 12:27:13 UTC
This bug can be considered a duplicate of 1076837. So please, continue the discussion there.

*** This bug has been marked as a duplicate of bug 1076837 ***
Comment 4 Matthias Gerstner 2018-01-30 11:11:42 UTC
I will answer this in bug 1071548.