7:04 a.m.
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'
2019-01-12 20:37:58,241-0700 INFO (jsonrpc/7) [vdsm.api] START
createStorageDomain(storageType=1,
sdUUID=u'b30c64c4-4b1f-4ebf-828b-e54c330ae84c', domainName=u'nfsdata',
typeSpecificArg=u'192.168.19.155:/data/data', domClass=1,
domVersion=u'4',
block_size=None, max_hosts=2000, options=None)
from=::ffff:192.168.19.178,51042, flow_id=67743df7,
task_id=ad82f581-9638-48f1-bcd9-669b9809b34a (api:48)
2019-01-12 20:37:58,241-0700 INFO (jsonrpc/7) [vdsm.api] FINISH
createStorageDomain error=Invalid parameter: 'block_size=None'
from=::ffff:192.168.19.178,51042, flow_id=67743df7,
task_id=ad82f581-9638-48f1-bcd9-669b9809b34a (api:52)
2019-01-12 20:37:58,241-0700 ERROR (jsonrpc/7) [storage.TaskManager.Task]
(Task='ad82f581-9638-48f1-bcd9-669b9809b34a') Unexpected error (task:875)
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882,
in _run
return fn(*args, **kargs)
File "<string>", line 2, in createStorageDomain
File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in
method
ret = func(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2583,
in createStorageDomain
alignment = clusterlock.alignment(block_size, max_hosts)
File "/usr/lib/python2.7/site-packages/vdsm/storage/clusterlock.py", line
661, in alignment
raise se.InvalidParameterException('block_size', block_size)
InvalidParameterException: Invalid parameter: 'block_size=None'
2019-01-12 20:37:58,242-0700 INFO (jsonrpc/7) [storage.TaskManager.Task]
(Task='ad82f581-9638-48f1-bcd9-669b9809b34a') aborting: Task is aborted:
u"Invalid parameter: 'block_size=None'" - code 100 (task:1181)
2019-01-12 20:37:58,242-0700 ERROR (jsonrpc/7) [storage.Dispatcher] FINISH
createStorageDomain error=Invalid parameter: 'block_size=None'
(dispatcher:81)
2019-01-12 20:37:58,242-0700 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC
call StorageDomain.create failed (error 1000) in 0.00 seconds (__init__:312)
2019-01-12 20:37:58,541-0700 INFO (jsonrpc/1) [vdsm.api] START
disconnectStorageServer(domType=1,
spUUID=u'00000000-0000-0000-0000-000000000000', conList=[{u'tpgt':
u'1',
u'id': u'db7d16c8-7497-42db-8a75-81cb7f9d3350', u'connection':
u'192.168.19.155:/data/data', u'iqn': u'', u'user':
u'', u'ipv6_enabled':
u'false', u'protocol_version': u'auto', u'password':
'********', u'port':
u''}], options=None) from=::ffff:192.168.19.178,51042,
flow_id=7e4cb4fa-1437-4d5b-acb5-958838ecd54c,
task_id=1d004ea2-ae84-4c95-8c70-29e205efd4b1 (api:48)
2019-01-12 20:37:58,542-0700 INFO (jsonrpc/1) [storage.Mount] unmounting
/rhev/data-center/mnt/192.168.19.155:_data_data (mount:212)
2019-01-12 20:37:59,087-0700 INFO (jsonrpc/1) [vdsm.api] FINISH
disconnectStorageServer return={'statuslist': [{'status': 0,
'id':
u'db7d16c8-7497-42db-8a75-81cb7f9d3350'}]}
from=::ffff:192.168.19.178,51042,
flow_id=7e4cb4fa-1437-4d5b-acb5-958838ecd54c,
task_id=1d004ea2-ae84-4c95-8c70-29e205efd4b1 (api:54)
2019-01-12 20:37:59,089-0700 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC
call StoragePool.disconnectStorageServer succeeded in 0.55 seconds
(__init__:312)
Devin Acosta
12:18 p.m.
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'
2019-01-12 20:37:58,241-0700 INFO (jsonrpc/7) [vdsm.api] START
createStorageDomain(storageType=1,
sdUUID=u'b30c64c4-4b1f-4ebf-828b-e54c330ae84c', domainName=u'nfsdata',
typeSpecificArg=u'192.168.19.155:/data/data', domClass=1,
domVersion=u'4', block_size=None, max_hosts=2000, options=None)
from=::ffff:192.168.19.178,51042, flow_id=67743df7,
task_id=ad82f581-9638-48f1-bcd9-669b9809b34a (api:48)
2019-01-12 20:37:58,241-0700 INFO (jsonrpc/7) [vdsm.api] FINISH
createStorageDomain error=Invalid parameter: 'block_size=None'
from=::ffff:192.168.19.178,51042, flow_id=67743df7,
task_id=ad82f581-9638-48f1-bcd9-669b9809b34a (api:52)
2019-01-12 20:37:58,241-0700 ERROR (jsonrpc/7) [storage.TaskManager.Task]
(Task='ad82f581-9638-48f1-bcd9-669b9809b34a') Unexpected error (task:875)
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882,
in _run
return fn(*args, **kargs)
File "<string>", line 2, in createStorageDomain
File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in
method
ret = func(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2583,
in createStorageDomain
alignment = clusterlock.alignment(block_size, max_hosts)
File "/usr/lib/python2.7/site-packages/vdsm/storage/clusterlock.py",
line 661, in alignment
raise se.InvalidParameterException('block_size', block_size)
InvalidParameterException: Invalid parameter: 'block_size=None'
2019-01-12 20:37:58,242-0700 INFO (jsonrpc/7) [storage.TaskManager.Task]
(Task='ad82f581-9638-48f1-bcd9-669b9809b34a') aborting: Task is aborted:
u"Invalid parameter: 'block_size=None'" - code 100 (task:1181)
2019-01-12 20:37:58,242-0700 ERROR (jsonrpc/7) [storage.Dispatcher] FINISH
createStorageDomain error=Invalid parameter: 'block_size=None'
(dispatcher:81)
2019-01-12 20:37:58,242-0700 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC
call StorageDomain.create failed (error 1000) in 0.00 seconds (__init__:312)
2019-01-12 20:37:58,541-0700 INFO (jsonrpc/1) [vdsm.api] START
disconnectStorageServer(domType=1,
spUUID=u'00000000-0000-0000-0000-000000000000', conList=[{u'tpgt':
u'1',
u'id': u'db7d16c8-7497-42db-8a75-81cb7f9d3350', u'connection':
u'192.168.19.155:/data/data', u'iqn': u'', u'user':
u'', u'ipv6_enabled':
u'false', u'protocol_version': u'auto', u'password':
'********', u'port':
u''}], options=None) from=::ffff:192.168.19.178,51042,
flow_id=7e4cb4fa-1437-4d5b-acb5-958838ecd54c,
task_id=1d004ea2-ae84-4c95-8c70-29e205efd4b1 (api:48)
2019-01-12 20:37:58,542-0700 INFO (jsonrpc/1) [storage.Mount] unmounting
/rhev/data-center/mnt/192.168.19.155:_data_data (mount:212)
2019-01-12 20:37:59,087-0700 INFO (jsonrpc/1) [vdsm.api] FINISH
disconnectStorageServer return={'statuslist': [{'status': 0,
'id':
u'db7d16c8-7497-42db-8a75-81cb7f9d3350'}]}
from=::ffff:192.168.19.178,51042,
flow_id=7e4cb4fa-1437-4d5b-acb5-958838ecd54c,
task_id=1d004ea2-ae84-4c95-8c70-29e205efd4b1 (api:54)
2019-01-12 20:37:59,089-0700 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC
call StoragePool.disconnectStorageServer succeeded in 0.55 seconds
(__init__:312)
Devin Acosta
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XFEIW6MUHJK...
2:38 p.m.
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
?
Gianluca
5:33 p.m.
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
?
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...
9:14 p.m.
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
11:08 a.m.
Would this default issue also affect gluster storage ?
On Sun, 13 Jan 2019 at 18:16, Nir Soffer <nsoffer(a)redhat.com> wrote:
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
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XKBMGSI6AUE...
1:09 p.m.
On 1/13/19 7:14 PM, Nir Soffer wrote:
On Sun, Jan 13, 2019 at 4:35 PM Gianluca Cecchi
<gianluca.cecchi(a)gmail.com <mailto:gianluca.cecchi@gmail.com>> wrote:
On Sun, Jan 13, 2019 at 12:38 PM Gianluca Cecchi
<gianluca.cecchi(a)gmail.com <mailto:gianluca.cecchi@gmail.com>> wrote:
On Sun, Jan 13, 2019 at 10:20 AM Shani Leviim
<sleviim(a)redhat.com <mailto:sleviim@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 <mailto:linuxguru.co@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
Hi,
There are no yamls on the host but you can replace the binaries
describing the API:
* download 'vdsm-api' rpm that was built from the aforementioned
patch:
https://jenkins.ovirt.org/job/vdsm_standard-on-merge/184/artifact/build-a...
* copy 'usr/lib/python2.7/site-packages/vdsm/rpc/vdsm-api.pickle' from
the rpm to the same location on your host
Marcin
2:32 p.m.
On Mon, Jan 14, 2019 at 11:09 AM Marcin Sobczyk <msobczyk(a)redhat.com> wrote:
Hi,
There are no yamls on the host but you can replace the binaries describing
the API:
- download 'vdsm-api' rpm that was built from the aforementioned
patch:
https://jenkins.ovirt.org/job/vdsm_standard-on-merge/184/artifact/build-a...
- copy 'usr/lib/python2.7/site-packages/vdsm/rpc/vdsm-api.pickle' from
the rpm to the same location on your host
Marcin
Hi Marcin,
I confirm that after copying the file and continuing from where
interrupted
I was able to complete the wizard of the Hosted Engine Deployment in my HCI
with single host environment case.
Inside the admin portal I correctly see the Hosted Engine VM and its
storage domain. And I'm able to connect to its console
I'll try the whole deploy from scratch using this info.
Thanks,
Gianluca
4:31 p.m.
Importing usr/lib/python2.7/site-packages/vdsm/rpc/vdsm-api.pickle
from vdsm-api-4.30.5-2.gitf824ec2.el7.noarch.rpm
also fixes the issue for gluster storage
On Mon, 14 Jan 2019 at 11:34, Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
On Mon, Jan 14, 2019 at 11:09 AM Marcin Sobczyk
<msobczyk(a)redhat.com>
wrote:
>
> Hi,
>
> There are no yamls on the host but you can replace the binaries
> describing the API:
>
> - download 'vdsm-api' rpm that was built from the aforementioned
> patch:
>
https://jenkins.ovirt.org/job/vdsm_standard-on-merge/184/artifact/build-a...
> - copy 'usr/lib/python2.7/site-packages/vdsm/rpc/vdsm-api.pickle'
> from the rpm to the same location on your host
>
> Marcin
>
>
> Hi Marcin,
I confirm that after copying the file and continuing from where
interrupted I was able to complete the wizard of the Hosted Engine
Deployment in my HCI with single host environment case.
Inside the admin portal I correctly see the Hosted Engine VM and its
storage domain. And I'm able to connect to its console
I'll try the whole deploy from scratch using this info.
Thanks,
Gianluca
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/OMTCB5G4SB7...
5:03 p.m.
On Mon, Jan 14, 2019 at 2:32 PM Maton, Brett <matonb(a)ltresources.co.uk>
wrote:
Importing usr/lib/python2.7/site-packages/vdsm/rpc/vdsm-api.pickle
from vdsm-api-4.30.5-2.gitf824ec2.el7.noarch.rpm
also fixes the issue for gluster storage
>
>
It is gluster in my case too, but using HCI single host deployment feature.
That should/could be the "official" replacement for the previous all-in-one
type of installation
So the host connects through Gluster to its gluster network ip and you
should also be able in the future, if that is the case, to expand to three
node (yet to investigate in detail)
Gianluca
2136
days inactive
2137
days old
9 comments
6 participants
participants (6)
-
Devin Acosta -
Gianluca Cecchi -
Marcin Sobczyk -
Maton, Brett -
Nir Soffer -
Shani Leviim