Greetings.
It seems that somehow our buildvmhost-10/11/12 machines are not currently properly multipathed to the iscsi on the netapp.
Normally, multipath means there's a number of ways to reach the iscsi lun and the machine will use whichever one. With only one path (as it is now), all our iscsi connections will die next week when there's a netapp storage outage.
So, I would like to in turn take out buildvm's from koji, let them finish building and reboot the buildvmhost to get multipath back on track. I tried restarting the service, but that didn't do any good, it's in a weird state (likely from iscsi issues a number of weeks back).
Since we have signed off on Alpha, the buildvm's aren't critical to it's release.
+1s?
kevin
On Thu, Mar 24, 2016 at 08:05:29AM -0600, Kevin Fenzi wrote:
Greetings.
It seems that somehow our buildvmhost-10/11/12 machines are not currently properly multipathed to the iscsi on the netapp.
Normally, multipath means there's a number of ways to reach the iscsi lun and the machine will use whichever one. With only one path (as it is now), all our iscsi connections will die next week when there's a netapp storage outage.
So, I would like to in turn take out buildvm's from koji, let them finish building and reboot the buildvmhost to get multipath back on track. I tried restarting the service, but that didn't do any good, it's in a weird state (likely from iscsi issues a number of weeks back).
Since we have signed off on Alpha, the buildvm's aren't critical to it's release.
+1s?
+1 for me
Pierre
On Thu, Mar 24, 2016 at 08:05:29AM -0600, Kevin Fenzi wrote:
Greetings.
It seems that somehow our buildvmhost-10/11/12 machines are not currently properly multipathed to the iscsi on the netapp.
Normally, multipath means there's a number of ways to reach the iscsi lun and the machine will use whichever one. With only one path (as it is now), all our iscsi connections will die next week when there's a netapp storage outage.
So, I would like to in turn take out buildvm's from koji, let them finish building and reboot the buildvmhost to get multipath back on track. I tried restarting the service, but that didn't do any good, it's in a weird state (likely from iscsi issues a number of weeks back).
Since we have signed off on Alpha, the buildvm's aren't critical to it's release.
+1s?
+1 here.
+1 from me On Mar 24, 2016 10:02, "Ralph Bean" rbean@redhat.com wrote:
On Thu, Mar 24, 2016 at 08:05:29AM -0600, Kevin Fenzi wrote:
Greetings.
It seems that somehow our buildvmhost-10/11/12 machines are not currently properly multipathed to the iscsi on the netapp.
Normally, multipath means there's a number of ways to reach the iscsi lun and the machine will use whichever one. With only one path (as it is now), all our iscsi connections will die next week when there's a netapp storage outage.
So, I would like to in turn take out buildvm's from koji, let them finish building and reboot the buildvmhost to get multipath back on track. I tried restarting the service, but that didn't do any good, it's in a weird state (likely from iscsi issues a number of weeks back).
Since we have signed off on Alpha, the buildvm's aren't critical to it's release.
+1s?
+1 here.
infrastructure mailing list infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraprojec...
infrastructure@lists.fedoraproject.org