Bug 40659 - service state wrong detected due to docker
service state wrong detected due to docker
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: Docker
UCS 4.1
Other Linux
: P5 normal (vote)
: UCS 4.1-4-errata
Assigned To: Philipp Hahn
Felix Botner
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-15 15:13 CET by Florian Best
Modified: 2016-12-21 15:32 CET (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.103
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2016-02-15 15:13:58 CET
If there are services like Apache running in the docker container the host system detects the univention-service as 'running' even if it doesn't run on the host system but only in the docker container.

curl -XPOST 'http://Administrator:univention@localhost:8090/command/services/query' | python -m json.tool

        {
            "autostart": "yes", 
            "description": "Web-Server", 
            "isRunning": true, 
            "service": "apache2"
        }, 

pstree shows the only apache running is:
     ├─docker─┬─2*[docker───5*[{docker}]]
     │        ├─init.debian─┬─apache2───5*[apache2]

I think this can cause more problems than only this. Every script which parses the output of 'ps' must be checked.
Comment 1 Philipp Hahn univentionstaff 2016-12-02 15:23:30 CET
4.1-4:
r74939 | Bug #40659 S4/AD: Fix check for running connector
r74938 | Bug #40659 ucr.service: Ignore docker children
4.2-0:
r74941 | Bug #40659 S4/AD: Fix check for running connector
r74940 | Bug #40659 ucr.service: Ignore docker children

Package: univention-config-registry
Version: 11.0.0-9.505.201612021514
Branch: ucs_4.1-0
Scope: errata4.1-4

Package: univention-ad-connector
Version: 10.0.2-14.514.201612021516
Branch: ucs_4.1-0
Scope: errata4.1-4

Package: univention-s4-connector
Version: 10.0.3-5.626.201612021517
Branch: ucs_4.1-0
Scope: errata4.1-4

r74942 | Bug #40659: Ignore Docker children YAML
 univention-config-registry.yaml univention-ad-connector.yaml univention-s4-connector.yaml
Comment 2 Philipp Hahn univentionstaff 2016-12-02 15:46:42 CET
r74944 | Bug #40659: Copyright 2016
r74943 | Bug #40659: Work around missing start-stop-daemon --remove-pidfile

Package: univention-ad-connector
Version: 10.0.2-15.515.201612021541
Branch: ucs_4.1-0
Scope: errata4.1-4

Package: univention-s4-connector
Version: 10.0.3-6.627.201612021542
Branch: ucs_4.1-0
Scope: errata4.1-4

r74945 | Bug #40659: Ignore Docker children YAML
 univention-ad-connector.yaml univention-s4-connector.yaml
Comment 3 Philipp Hahn univentionstaff 2016-12-05 12:11:01 CET
r74961 | Bug #40659: Fix check for running AD connector UCS-4.1-4
r74963 | Bug #40659: Fix check for running AD connector UCS-4.2-0

Package: univention-ad-connector
Version: 10.0.2-16.516.201612051207
Branch: ucs_4.1-0
Scope: errata4.1-4

r74962 | Bug #40659: Fix check for running AD connector YAML
Comment 4 Felix Botner univentionstaff 2016-12-05 13:58:37 CET
OK - univention-config-registry.yaml
OK - service check
OK - merged to 4.2-0

OK - univention-ad-connector.yaml
OK - init script service definition
OK - merged to 4.2-0

OK - univention-s4-connector.yaml
OK - init script service definition
OK - merged to 4.2-0
Comment 6 Philipp Hahn univentionstaff 2016-12-21 15:32:53 CET
<http://errata.software-univention.de/ucs/4.1/365.html>