The test: - test_ipactl_scenario_check
test_ipactl_scenario_check
are failing in [testing_ipa-4.9_latest] Nightly PR #1241 with the errors:
E subprocess.CalledProcessError: Command '['ipactl', 'status']' returned non-zero exit status 3. ... DEBUG ipatests.pytest_ipa.integration.host.Host.master.cmd125:transport.py:513 RUN ['ipactl', 'status'] DEBUG ipatests.pytest_ipa.integration.host.Host.master.cmd125:transport.py:557 Directory Service: RUNNING DEBUG ipatests.pytest_ipa.integration.host.Host.master.cmd125:transport.py:557 1 service(s) are not running DEBUG ipatests.pytest_ipa.integration.host.Host.master.cmd125:transport.py:557 krb5kdc Service: RUNNING DEBUG ipatests.pytest_ipa.integration.host.Host.master.cmd125:transport.py:557 kadmin Service: RUNNING DEBUG ipatests.pytest_ipa.integration.host.Host.master.cmd125:transport.py:557 named Service: RUNNING DEBUG ipatests.pytest_ipa.integration.host.Host.master.cmd125:transport.py:557 httpd Service: RUNNING DEBUG ipatests.pytest_ipa.integration.host.Host.master.cmd125:transport.py:557 ipa-custodia Service: RUNNING DEBUG ipatests.pytest_ipa.integration.host.Host.master.cmd125:transport.py:557 pki-tomcatd Service: STOPPED DEBUG ipatests.pytest_ipa.integration.host.Host.master.cmd125:transport.py:557 ipa-otpd Service: RUNNING DEBUG ipatests.pytest_ipa.integration.host.Host.master.cmd125:transport.py:557 ipa-ods-exporter Service: RUNNING DEBUG ipatests.pytest_ipa.integration.host.Host.master.cmd125:transport.py:557 ods-enforcerd Service: RUNNING DEBUG ipatests.pytest_ipa.integration.host.Host.master.cmd125:transport.py:557 ipa-dnskeysyncd Service: RUNNING DEBUG ipatests.pytest_ipa.integration.host.Host.master.cmd125:transport.py:217 Exit code: 3 ERROR ipatests.pytest_ipa.integration.host.Host.master.cmd125:host.py:201 stderr: 1 service(s) are not running
Full report
Note: The tests - test_ipaca_no_redirect - test_hostname_parameter seem to be failing due to the network issues
test_ipaca_no_redirect
test_hostname_parameter
I'm inclined to close this. It hasn't failed since, so 4 months ago, so 16+ runs.
It appears that it took too long for the CA to start up which could have been due in part to environmental issues on the box (other load, etc).
I agree with @rcritten, we can close this one and re-open if the issue happens again.
Metadata Update from @frenaud: - Issue close_status updated to: worksforme - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.