On 11/23/2015 09:13 AM, Ján Tomko wrote:
> On Fri, Oct 30, 2015 at 11:13:21AM -0400, John Ferlan wrote:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1276198
>>
>> Prior to commit id '98322052' failure to saferead the block device would
>> cause an error to be logged and the device to be skipped
On Fri, Oct 30, 2015 at 11:13:21AM -0400, John Ferlan wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1276198
>
> Prior to commit id '98322052' failure to saferead the block device would
> cause an error to be logged and the device to be skipped while attempting
> to discover/create a stable
ping*2?
Tks -
John
On 10/30/2015 11:13 AM, John Ferlan wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1276198
>
> Prior to commit id '98322052' failure to saferead the block device would
> cause an error to be logged and the device to be skipped while attempting
> to discover/create a st
ping
Thanks -
John
On 10/30/2015 11:13 AM, John Ferlan wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1276198
>
> Prior to commit id '98322052' failure to saferead the block device would
> cause an error to be logged and the device to be skipped while attempting
> to discover/create a st
https://bugzilla.redhat.com/show_bug.cgi?id=1276198
Prior to commit id '98322052' failure to saferead the block device would
cause an error to be logged and the device to be skipped while attempting
to discover/create a stable target path for a new LUN (NPIV).
This was because virStorageBackendSC