After 3.5->3.6 upgrade, OVF update error every hour
After upgrading an oVirt cluster from 3.5 to 3.6, I am getting the following error every hour: Failed to update OVF disks ce8647c6-f936-4633-8a7b-e7dcb45d8ebb, OVF data isn't updated on those OVF stores (Data Center Middle-Earth, Storage Domain equallogic). Looking in the vdsm log on the SPM node, it looks like the problem is that an attempt was made to lvextend an LV to 2m, but the LV is already 128m, so the extend failed (not needed). I've attached the log entries for that task. Any suggestions, ideas how to fix, etc.? -- Chris Adams <cma@cmadams.net>
Chris, Make sure you have vdsm >= 4.17.35 installed. -----Original Message----- From: <users-bounces@ovirt.org> on behalf of Chris Adams <cma@cmadams.net> Date: Thursday, 6 April 2017 at 16:29 To: "users@ovirt.org" <users@ovirt.org> Subject: [ovirt-users] After 3.5->3.6 upgrade, OVF update error every hour After upgrading an oVirt cluster from 3.5 to 3.6, I am getting the following error every hour: Failed to update OVF disks ce8647c6-f936-4633-8a7b-e7dcb45d8ebb, OVF data isn't updated on those OVF stores (Data Center Middle-Earth, Storage Domain equallogic). Looking in the vdsm log on the SPM node, it looks like the problem is that an attempt was made to lvextend an LV to 2m, but the LV is already 128m, so the extend failed (not needed). I've attached the log entries for that task. Any suggestions, ideas how to fix, etc.? -- Chris Adams <cma@cmadams.net>
That version of vdsm doesn't seem to be in the ovirt-3.6 repos - where would I get it? My plan is to continue upgrading to 4.0 and then 4.1. Does that version (or newer) come from 4.0+? If so, is it safe to upgrade to 4.0 with the older vdsm, or should I update vdsm first (to eliminate this error)? Thanks. Once upon a time, Pavel Gashev <Pax@acronis.com> said:
Chris,
Make sure you have vdsm >= 4.17.35 installed.
-----Original Message----- From: <users-bounces@ovirt.org> on behalf of Chris Adams <cma@cmadams.net> Date: Thursday, 6 April 2017 at 16:29 To: "users@ovirt.org" <users@ovirt.org> Subject: [ovirt-users] After 3.5->3.6 upgrade, OVF update error every hour
After upgrading an oVirt cluster from 3.5 to 3.6, I am getting the following error every hour:
Failed to update OVF disks ce8647c6-f936-4633-8a7b-e7dcb45d8ebb, OVF data isn't updated on those OVF stores (Data Center Middle-Earth, Storage Domain equallogic).
Looking in the vdsm log on the SPM node, it looks like the problem is that an attempt was made to lvextend an LV to 2m, but the LV is already 128m, so the extend failed (not needed). I've attached the log entries for that task.
Any suggestions, ideas how to fix, etc.?
-- Chris Adams <cma@cmadams.net>
-- Chris Adams <cma@cmadams.net>
I’d suggest to update it from http://thepax.gitlab.io/ovirt36/ -----Original Message----- From: Chris Adams <cma@cmadams.net> Date: Thursday, 6 April 2017 at 18:47 To: Pavel Gashev <Pax@acronis.com> Cc: "users@ovirt.org" <users@ovirt.org> Subject: Re: [ovirt-users] After 3.5->3.6 upgrade, OVF update error every hour That version of vdsm doesn't seem to be in the ovirt-3.6 repos - where would I get it? My plan is to continue upgrading to 4.0 and then 4.1. Does that version (or newer) come from 4.0+? If so, is it safe to upgrade to 4.0 with the older vdsm, or should I update vdsm first (to eliminate this error)? Thanks. Once upon a time, Pavel Gashev <Pax@acronis.com> said:
Chris,
Make sure you have vdsm >= 4.17.35 installed.
-----Original Message----- From: <users-bounces@ovirt.org> on behalf of Chris Adams <cma@cmadams.net> Date: Thursday, 6 April 2017 at 16:29 To: "users@ovirt.org" <users@ovirt.org> Subject: [ovirt-users] After 3.5->3.6 upgrade, OVF update error every hour
After upgrading an oVirt cluster from 3.5 to 3.6, I am getting the following error every hour:
Failed to update OVF disks ce8647c6-f936-4633-8a7b-e7dcb45d8ebb, OVF data isn't updated on those OVF stores (Data Center Middle-Earth, Storage Domain equallogic).
Looking in the vdsm log on the SPM node, it looks like the problem is that an attempt was made to lvextend an LV to 2m, but the LV is already 128m, so the extend failed (not needed). I've attached the log entries for that task.
Any suggestions, ideas how to fix, etc.?
-- Chris Adams <cma@cmadams.net>
-- Chris Adams <cma@cmadams.net>
participants (2)
-
Chris Adams -
Pavel Gashev