On Sun, Jan 13, 2019 at 4:35 PM Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
On Sun, Jan 13, 2019 at 12:38 PM Gianluca Cecchi <
gianluca.cecchi(a)gmail.com> wrote:
> On Sun, Jan 13, 2019 at 10:20 AM Shani Leviim <sleviim(a)redhat.com> wrote:
>
>> Hi Devin,
>> This one was solved in the following patch:
>>
https://gerrit.ovirt.org/#/c/96746/
>>
>>
>> *Regards,*
>>
>> *Shani Leviim*
>>
>>
>> On Sun, Jan 13, 2019 at 10:13 AM Devin Acosta <linuxguru.co(a)gmail.com>
>> wrote:
>>
>>> I installed the latest 4.3 release candidate and tried to add an NFS
>>> mount to the Data Center, and it errors in the GUI with “Error while
>>> executing action New NFS Storage Domain: Invalid parameter”, then in the
>>> vdsm.log I see it is passing “block_size=None”. Does this regardless if NFS
>>> v3 or v4.
>>>
>>> InvalidParameterException: Invalid parameter: 'block_size=None'
>>>
>>>
> Hi,
> could be the same I have in this thread during single host HCI install:
>
https://www.mail-archive.com/users@ovirt.org/msg52875.html
>
It looks the same issue.
This was was broken for few days, and was fixed last week.
> ?
>
> Gianluca
>
I have not understood where to find the to-be-patched file vdsm-api.yml
It seems it is not in engine and host...
The yaml file is the source - on the host the file is stored in a binary
format
that is 100 times faster to load.
Marcin, do we have an easy way to update the yaml on a host without building
vdsm from source?
Nir