Hide Forgot
Description of problem: The VDSM API Version negotiation has a problem where it keeps sending the 'api-version' message to the guest agent, even though the negotiation has already taken place. This happens in cases where the VDSM version is supporting a lower API Version then the guest agent. As this is the case between 3.5 and 3.6 VDSM (4.16.20) @ 3.5 supports API Version 1 ovirt-guest-agent (1.0.11) @ 3.6 supports API Version 2 Version-Release number of selected component (if applicable): vdsm-4.16.20 How reproducible: 100% Steps to Reproduce: 1. setup a 3.5 cluster with 3.5 vdsm installed (4.16.20) 2. create a CentOS 7 VM with the latest guest agent from 3.6 (1.0.11) through epel Actual results: Every two seconds (with every heart beat) an api-version message is sent to the guest agent (seen in the logs on INFO level) Expected results: Negotiation only once per migration/vm start/ovirt-guest-agent start or VDSM restart
Bugs moved pre-mature to ON_QA since they didn't have target release. Notice that only bugs with a set target release will move to ON_QA.
Reproduced as per description. Verified behaviour with vdsm-4.17.26-0.el7ev on host and ovirt-guest-agent-common-1.0.11-3.el7.noarch on guest. Message appear only on first communication.