Hi, Do you actually use puppet over ovirt-node? This is unsupported.
Regards, Alon ----- Original Message ----- > From: "ybronhei" <[email protected]> > To: "Trey Dockendorf" <[email protected]> > Cc: "users" <[email protected]>, "Fabian Deutsch" <[email protected]>, "Dan > Kenigsberg" <[email protected]>, "Itamar > Heim" <[email protected]>, "Douglas Landgraf" <[email protected]>, "Alon > Bar-Lev" <[email protected]> > Sent: Tuesday, August 5, 2014 8:32:04 PM > Subject: Re: [ovirt-users] Proper way to change and persist vdsm > configuration options > > Hey, > > Just noticed something that I forgot about.. > before filing new BZ, see in ovirt-host-deploy README.environment [1] > the section: > VDSM/configOverride(bool) [True] > Override vdsm configuration file. > > changing it to false will keep your vdsm.conf file as is after deploying > the host again (what happens after node upgrade) > > [1] > https://github.com/oVirt/ovirt-host-deploy/blob/master/README.environment > > please check if that what you meant.. > > Thanks, > Yaniv Bronhaim. > > On 08/05/2014 08:12 AM, Trey Dockendorf wrote: > > I'll file BZ. As far as I can recall this has been an issue since 3.3.x as > > I have been using Puppet to modify values and have had to rerun Puppet > > after installing a node via GUI and when performing update from GUI. Given > > that it has occurred when VDSM version didn't change on the node it seems > > likely to be something being done by Python code that bootstraps a node and > > performs the other tasks. I won't have any systems available to test with > > for a few days. New hardware specifically for our oVirt deployment is on > > order so should be able to more thoroughly debug and capture logs at that > > time. > > > > Would using vdsm-reg be a better solution for adding new nodes? I only > > tried using vdsm-reg once and it went very poorly...lots of missing > > dependencies not pulled in from yum install I had to install manually via > > yum. Then the node was auto added to newest cluster with no ability to > > change the cluster. Be happy to debug that too if there's some docs that > > outline the expected behavior. > > > > Using vdsm-reg or something similar seems like a better fit for puppet > > deployed nodes, as opposed to requiring GUI steps to add the node. > > > > Thanks > > - Trey > > On Aug 4, 2014 5:53 AM, "ybronhei" <[email protected]> wrote: > > > >> On 07/31/2014 01:28 AM, Trey Dockendorf wrote: > >> > >>> I'm running ovirt nodes that are stock CentOS 6.5 systems with VDSM > >>> installed. I am using iSER to do iSCSI over RDMA and to make that > >>> work I have to modify /etc/vdsm/vdsm.conf to include the following: > >>> > >>> [irs] > >>> iscsi_default_ifaces = iser,default > >>> > >>> I've noticed that any time I upgrade a node from the engine web > >>> interface that changes to vdsm.conf are wiped out. I don't know if > >>> this is being done by the configuration code or by the vdsm package. > >>> Is there a more reliable way to ensure changes to vdsm.conf are NOT > >>> removed automatically? > >>> > >> > >> Hey, > >> > >> vdsm.conf shouldn't wiped out and shouldn't changed at all during upgrade. > >> other related conf files (such as libvirtd.conf) might be overrided to > >> keep > >> defaults configurations for vdsm. but vdsm.conf should persist with user's > >> modification. from my check, regular yum upgrade doesn't touch vdsm.conf > >> > >> Douglas can you verify that with node upgrade? might be specific to that > >> flow.. > >> > >> Trey, can file a bugzilla on that and describe your steps there? > >> > >> Thanks > >> > >> Yaniv Bronhaim, > >> > >>> > >>> Thanks, > >>> - Trey > >>> _______________________________________________ > >>> Users mailing list > >>> [email protected] > >>> http://lists.ovirt.org/mailman/listinfo/users > >>> > >>> > >> > >> -- > >> Yaniv Bronhaim. > >> > > > _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
