test_microbot fails to establish connection and fails

Bug #1883572 reported by Alexander Balderson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Charmed Kubernetes Testing
Incomplete
Undecided
Unassigned

Bug Description

The test_microbot test from the kubernetes test suite is failling because it cannot connect to the instance.

The pod logs show that the instance is up; and that the instance is getting requests:
10.1.49.1 - - [14/Jun/2020:10:00:44 +0000] "GET / HTTP/1.1" 200 351 "-" "kube-probe/1.18" "-"

crashdump is attached.

=================================== FAILURES ===================================
________________________________ test_microbot _________________________________
Traceback (most recent call last):
  File "/home/ubuntu/k8s-validation/jobs/integration/validation.py", line 331, in test_microbot
    raise MicrobotError("Microbot failed to start.")
integration.validation.MicrobotError: Microbot failed to start.
=============================== warnings summary ===============================
.tox/py3/lib/python3.6/site-packages/_pytest/junitxml.py:417
  /home/ubuntu/k8s-validation/.tox/py3/lib/python3.6/site-packages/_pytest/junitxml.py:417: PytestDeprecationWarning: The 'junit_family' default value will change to 'xunit2' in pytest 6.0.
  Add 'junit_family=xunit1' to your pytest.ini file to keep the current format in future versions of pytest and silence this warning.
    _issue_warning_captured(deprecated.JUNIT_XML_DEFAULT_FAMILY, config.hook, 2)

-- Docs: https://docs.pytest.org/en/latest/warnings.html
- generated xml file: /home/ubuntu/project/generated/kubernetes/k8s-suite/test_microbot-junit.xml -
----- generated html file: file:///home/ubuntu/k8s-validation/report.html ------
=========================== short test summary info ============================
FAILED jobs/integration/validation.py::test_microbot - integration.validation...
!!!!!!!!!!!!!!!!!!!!!!!!!! stopping after 1 failures !!!!!!!!!!!!!!!!!!!!!!!!!!!
======================== 1 failed, 1 warning in 35.39s =========================

Revision history for this message
Alexander Balderson (asbalderson) wrote :
Revision history for this message
George Kraft (cynerva) wrote :

This looks similar to https://bugs.launchpad.net/charmed-kubernetes-testing/+bug/1878231

Which was fixed by https://github.com/charmed-kubernetes/jenkins/commit/11a0b52a41eca2f23de7685b3eaff23a933272a5

Can you please tell us what commit of the jenkins repo you're running the tests from? Or at least confirm that the version you're running includes the above fix?

Changed in charmed-kubernetes-testing:
status: New → Incomplete
Changed in charmed-kubernetes-testing:
status: Incomplete → New
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.