Description of problem: Other than the ovirtmgmt for all the other interfaces ovirt will set as ON_BOOT=no. Because of this issue when server comes up back the interface will not be brought up and the bricks which is attached to this interface will be shown down in the UI. Version-Release number of selected component (if applicable): vdsm-4.16.16-1.3.el6rhs.x86_64 How reproducible: Always Steps to Reproduce: 1. Create network from UI. 2. Now assign this logical network to the gluster network. 3. Create a volume. 4. reboot the system. Actual results: The interfaces which are attached to gluster network does not have onboot=yes in the ifcfg files. Expected results: The interfaces which are attached to gluster network should have onboot=yes set in the ifcfg files. Additional info:
As mentioned in Bug 1215011 comment 2, will set the vdsm.conf's net_persistence=ifcfg till a proper solution is available
Created attachment 1038558 [details] patch This patch fixes the issue by using the workaround ie adds net_persistence=ifcfg config entry into /etc/vdsm/vdsm.conf
Hi Bala, I do not see net_persistence=ifcfg in /etc/vds/vdsm.conf file. Below are the contents of my /etc/vdsm/vdsm.conf file. cat /etc/vdsm/vdsm.conf [vars] ssl = true [addresses] management_port = 54321 can you please help me understand what is the exact fix made for this?
Once you have installed vdsm-gluster package, it updates/creates vdsm.conf file with the config of net_persistence=ifcfg in [vars].
Moving this bug back because, once vdsm is installed on the node i see the changes being reflected in the /etc/vdsm/vdsm.conf. I see a line with net_persistence=ifcfg in [vars] But once the node is added to rhsc, all the changes vanishes and the following content is seen in the vdsm.conf file. cat /etc/vdsm/vdsm.conf [vars] ssl = true [addresses] management_port = 54321
host-deploy/bootstrap needs to be fixed to keep the changes.
Even with onboot=no on the interface attached to glusternw, the interface is UP after reboot. So closing this for now. Please reopen if the issue is faced again