On 12/04/18 11:54, mpho raffiki wrote:
> Hi Milan
>
> The issue is that debian does not have the proper symbolic link of the
> kernel device /dev/vport2p1. another issue for it not to work; is that
> when you look at the device attributes for vport2p1 the attribute name
> is something else under debian stretch (ATTR{name}=="ovirt-guest-agent.0" )
The Debian package (version 1.0.13.dfsg-2) includes the right udev rules
in /lib/udev/rules.d/55-ovirt-guest-agent.rules, so the problem is not
there. The issue is in the postinst script, which triggers based only on
the old name:
udevadm trigger --subsystem-match="virtio-ports" \
--attr-match="name=com.redhat.rhevm.vdsm"
udevadm settle
The debian/postinst script should be modified to trigger both for the
old name (which is used in oVirt 4.1 and below) and the new name (for
oVirt 4.2 and up):
udevadm trigger --subsystem-match="virtio-ports" \
--attr-match="name=ovirt-guest-agent.0"
I have built some internal packages including this change and the
upgrade process is flawless with this addition. This also works on
backports to jessie and stretch, not just for buster/sid.
Please find a patch attached in case it's useful.
Best regards,
Chris
--
Chris Boot
[email protected]
diff --git a/debian/postinst b/debian/postinst
index 9951cc715140..79686b01145a 100644
--- a/debian/postinst
+++ b/debian/postinst
@@ -9,6 +9,7 @@ if test -d /sys/class && \
test -e /proc/filesystems && \
! ischroot; then
udevadm trigger --subsystem-match="virtio-ports" --attr-match="name=com.redhat.rhevm.vdsm"
+ udevadm trigger --subsystem-match="virtio-ports" --attr-match="ovirt-guest-agent.0"
udevadm settle
fi
