Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.0, 3.1.1, 3.2.0-devel
    • Fix Version/s: 3.1.2
    • Component/s: Node Controller
    • Labels:
      None
    • Security:
      No
    • SLA:
      Not Applicable
    • Rank:
      2|hzy7nr:

      Description

      Over time, when a node machine is under high IO load, the NC libvirt connection starts behaving badly (blocking, returning false positive/negatives, etc). When we refresh the libvirt connection periodically, observed symptoms vanish.

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            dmitrii Dmitrii Zagorodnov added a comment -

            QA implications: As long as our automated tests pass for all hypervisors there should not be any danger of reopening the hypervisor connection before each libvirt invocation.

            Show
            dmitrii Dmitrii Zagorodnov added a comment - QA implications: As long as our automated tests pass for all hypervisors there should not be any danger of reopening the hypervisor connection before each libvirt invocation.

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development