service is-active output check for "failed"#3574
Conversation
|
@blueorangutan package |
|
@DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-267 |
|
@blueorangutan test centos7 kvm-centos7 |
|
@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
GabrielBrascher
left a comment
There was a problem hiding this comment.
LGTM based on code and manual test.
I have tested and indeed the systemctl is-active cloudstack-management.service command returns active and failed. Regardless of calling a systemctl is-active cloudstack-management.service or systemctl is-failed cloudstack-management.service I got active and failed (that I found weird)
|
@blueorangutan package |
|
@DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-268 |
|
@blueorangutan test centos7 kvm-centos7 |
|
@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-345)
|
|
I'll have a quick look at those logs but I don't think these blueorangutan/Trillian errors are related to this change. |
Description
small change to check for the right output of the system call
Fixes: #3572
Types of changes
Screenshots (if appropriate):
How Has This Been Tested?
manual testing on a nested env so far.