Bug 1437145

Not in any build yet, please move to ON_QA when this actually is in some build.

Qe are taking early build to test and as Gil moved this, I'm moving it back.

Testing with ovirt-guest-agent-common-1.0.14-1.el7.noarch from brew, there is package only for el7, so I can't test el6, also it's not present in any build as of now.

I have 'ignored_nics = eth1' in guest agent config in general section but the IP from eth1 set as static with local IP is still reported to guest agent.

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

This is not ON_QA, it shouldn't have been moved by  Gil Klein 2017-07-27 11:32:29 CEST

oVirt 4.2.0 has been released on Dec 20th 2017. Please check if this has been included and move to QE or consider re-targeting this bug to next milestone

I'm little bit late to the game because the automation already retargeted the bug, but yes, it should be ON_QA.

Using version 1.0.14-1

This works for docker0, but when I set eth0 in /etc/ovirt-guest-agent.conf with 'ignored_nics = eth0' in general section it is still reported

        <reported_devices>
            <reported_device href="/ovirt-engine/api/vms/$vm_id/reporteddevices/$id" id="$id">
                <name>eth0</name>
                <description>guest reported data</description>
                <ips>
                    <ip>
                        <address>$ip</address>
                        <version>v4</version>
                    </ip>
                    <ip>
                        <address>$ipv6_ip</address>
                        <version>v6</version>
                    </ip>
                </ips>
                <mac>
                    <address>$mac</address>
                </mac>
                <type>network</type>
            </reported_device>
        </reported_devices>

(In reply to Petr Matyáš from comment #9)
> Using version 1.0.14-1

Try with latest version 1.0.14-3

(In reply to Tomáš Golembiovský from comment #10)
> (In reply to Petr Matyáš from comment #9)
> > Using version 1.0.14-1
> 
> Try with latest version 1.0.14-3

That's not how this works, that's not how any of this works :D

And no, with ovirt-guest-agent-common-1.0.14-3.el7ev.noarch it's still reporting eth0 even when it's defined in /etc/ovirt-guest-agent.conf with 'ignored_nics = eth0'.

(In reply to Petr Matyáš from comment #11)
> (In reply to Tomáš Golembiovský from comment #10)
> > (In reply to Petr Matyáš from comment #9)
> > > Using version 1.0.14-1
> > 
> > Try with latest version 1.0.14-3
> 
> That's not how this works, that's not how any of this works :D
> 
> And no, with ovirt-guest-agent-common-1.0.14-3.el7ev.noarch it's still
> reporting eth0 even when it's defined in /etc/ovirt-guest-agent.conf with
> 'ignored_nics = eth0'.

Tomáš, can you please take a look at the issue?

It turns out the problem is caching of the data in engine. I'm moving the bug back to QA and I opened a separate bug on engine.

Verified on ovirt-guest-agent-common-1.0.14-3.el7ev

Specific NIC can be blacklisted, however only when GA was not yet started, in ovirt-guest-agent.conf. If it was already running it already reported the data and thus it's saved (cached) in the DB. At least till bug#1546675 is not solved.

You can delete the specific line from the DB (table vm_guest_agent_interfaces) and not have it reported in the engine any more if you like.

This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.

Hi Tomas
I'm reviewing the doc text and I'm not sure what to make of the known bug that you discuss. Are you implying that the known bug is a small/irrelevant issue, and that most customers will only be using the feature for new VMs?

Usually, we do not reference other bugs in a specific bug's release note text. Either the issue is a known issue and will be defined as such anyway in it's definition at the time of release, or i simply need to say that currently the feature does is available for new VMs only.

clearing the needinfo, there's nothing more to add here

well, except that with qemu-guest-agent reporting there is no such blacklisting available and you again get all the interfaces and addresses, including the loopback and 127.0.0.1 which we filter in ovirt-guest-agent by default for a long time