- Users - oVirt List Archives

hosted-engine --deploy fails on iSCSI while trying to connect to retrieved ipv6 address, even while forcing ipv4 with --4
by Guillaume Pavese 15 Mar '19

15 Mar '19

I try to deploy hosted-engine 4.3.2-rc2 on iSCSI I put a ipv4 portal address and targets get discovered. However they are are returned by the Synology hosts with both ipv4 and ipv6 adresses. LUN discovery then fails while attempting to connect to ipv6 address I tried hosted-engine --deploy --4 to force ipv4 but that fails too. Please specify the storage you would like: iscsi Please specify the iSCSI portal IP address: 10.199.9.16 Please specify the iSCSI portal port [3260]: Please specify the iSCSI discover user: Please specify the iSCSI discover password: Please specify the iSCSI portal login user: Please specify the iSCSI portal login password: [ INFO ] Discovering iSCSI targets [ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Prepare iSCSI parameters] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch host facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : iSCSI discover with REST API] [ INFO ] ok: [localhost] The following targets have been found: [1] iqn.2000-01.com.synology:SVC-STO-FR-301.Target-1.2dfed4a32a TPGT: 1, portals: 10.199.9.16:3260 fe80::211:32ff:fe6d:6ddb:3260 [2] iqn.2000-01.com.synology:SVC-STO-FR-301.Target-2.2dfed4a32a TPGT: 1, portals: 10.199.9.16:3260 fe80::211:32ff:fe6d:6ddb:3260 in Host's logs : mars 15 09:32:25 vs-inf-int-kvm-fr-304-210.hostics.fr iscsid[5983]:conn 0 login rejected: initiator error (02/00) mars 15 09:32:25 vs-inf-int-kvm-fr-304-210.hostics.fr iscsid[5983]: Connection1:0 to [target: iqn.2000-01.com.synology:SVC-STO-FR-301.Target-2.2dfed4a32a, portal: 10.199.9.16,3260] through [iface: default] is shutdown. mars 15 09:32:27 vs-inf-int-kvm-fr-304-210.hostics.fr iscsid[5983]: cannot make a connection to fe80::211:32ff:fe6d:6ddb:3260 (-1,22) ... mars 15 09:33:21 vs-inf-int-kvm-fr-304-210.hostics.fr iscsid[5983]: cannot make a connection to fe80::211:32ff:fe6d:6ddb:3260 (-1,22) mars 15 09:33:24 vs-inf-int-kvm-fr-304-210.hostics.fr iscsid[5983]: cannot make a connection to fe80::211:32ff:fe6d:6ddb:3260 (-1,22) mars 15 09:33:27 vs-inf-int-kvm-fr-304-210.hostics.fr vdsm[26174]: WARN Worker blocked: <Worker name=jsonrpc/1 running <Task <JsonRpcTask {'params': {u'connectionParams': [{u'port': u'3260', u'connection': u'fe80::211:32ff:fe6d:6ddb', u'iqn': u'iqn.2000-01.com.synology:SVC-STO-FR-301.Target-2.2dfed4a32a', u'user': u'', u'tpgt': u'1', u'ipv6_enabled': u'true', u'password': '********', u'id': u'00000000-0000-0000-0000-000000000000'}], u'storagepoolID': u'00000000-0000-0000-0000-000000000000', u'domainType': 3}, 'jsonrpc': '2.0', 'method': u'StoragePool.connectStorageServer', 'id': u'31411035-df1d-4b61-ac37-2a138dbdbb00'} at 0x7fcb904ef390> timeout=60, duration=60.00 at 0x7fcb904ef410> task#=10 at 0x7fcb905977d0>, traceback: File: "/usr/lib64/python2.7/threading.py", line 785, in __bootstrap self.__bootstrap_inner() File: "/usr/lib64/python2.7/threading.py", line 812, in __bootstrap_inner self.run() File: "/usr/lib64/python2.7/threading.py", line 765, in run self.__target(*self.__args, **self.__kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/common/concurrent.py", line 195, in run ret = func(*args, **kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 301, in _run self._execute_task() File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 315, in _execute_task task() File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 391, in __call__ self._callable() File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 262, in __call__ self._handler(self._ctx, self._req) File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 305, in _serveRequest response = self._handle_request(req, ctx) File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 345, in _handle_request res = method(**params) File: "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 198, in _dynamicMethod result = fn(*methodArgs) File: "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1095, in connectStorageServer connectionParams) File: "/usr/lib/python2.7/site-packages/vdsm/storage/dispatcher.py", line 74, in wrapper result = ctask.prepare(func, *args, **kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 108, in wrapper return m(self, *a, **kw) File: "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 1179, in prepare result = self._run(func, *args, **kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File: "<string>", line 2, in connectStorageServer 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 2411, in connectStorageServer conObj.connect() File: "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 488, in connect iscsi.addIscsiNode(self._iface, self._target, self._cred) File: "/usr/lib/python2.7/site-packages/vdsm/storage/iscsi.py", line 217, in addIscsiNode iscsiadm.node_login(iface.name, target.address, target.iqn) File: "/usr/lib/python2.7/site-packages/vdsm/storage/iscsiadm.py", line 327, in node_login portal, "-l"]) File: "/usr/lib/python2.7/site-packages/vdsm/storage/iscsiadm.py", line 122, in _runCmd return misc.execCmd(cmd, printable=printCmd, sudo=True, sync=sync) File: "/usr/lib/python2.7/site-packages/vdsm/common/commands.py", line 213, in execCmd (out, err) = p.communicate(data) File: "/usr/lib64/python2.7/site-packages/subprocess32.py", line 924, in communicate stdout, stderr = self._communicate(input, endtime, timeout) File: "/usr/lib64/python2.7/site-packages/subprocess32.py", line 1706, in _communicate orig_timeout) File: "/usr/lib64/python2.7/site-packages/subprocess32.py", line 1779, in _communicate_with_poll ready = poller.poll(self._remaining_time(endtime)) mars 15 09:33:27 vs-inf-int-kvm-fr-304-210.hostics.fr iscsid[5983]: cannot make a connection to fe80::211:32ff:fe6d:6ddb:3260 (-1,22) Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group

1 0

Centos7.5 virtual machine installation is slow
by xilazz＠126.com 15 Mar '19

15 Mar '19

Software version 4.3.1.1-1. The virtual machine performed post-installation setup tasks for a long time during the process of creating Centos7.5 system.I don't know if any of you have.

1 0

upgrading failed from 4.2 to 4.3
by Abhishek Sahni 15 Mar '19

15 Mar '19

Hello Users, I am trying to upgrade ovirt-engine running on bare metal, following below guide, https://ovirt.org/release/4.3.0/ and it is getting failed every time with the below errors, engine-setup ============================ [ INFO ] Stage: Setup validation During execution engine service will be stopped (OK, Cancel) [OK]: [ ERROR ] It seems that you are running your engine inside of the hosted-engine VM and are not in "Global Maintenance" mode. In that case you should put the system into the "Global Maintenance" mode before running engine-setup, or the hosted-engine HA agent might kill the machine, which might corrupt your data. [ ERROR ] Failed to execute stage 'Setup validation': Hosted Engine setup detected, but Global Maintenance is not set. [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20190314171026-wicgh1.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20190314171042-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed =================================== I was using hosted engine on nodes earlier but later remove the nodes and using ovirt egine on seperate bare-metal. Any pointers? -- ABHISHEK SAHNI Mob : +91-990-701-5143

2 2

Check in API if host is in state "reconfiguring networks"
by Eduardo Mayoral 14 Mar '19

14 Mar '19

Hi, I am writing some provisioning scripts using the python API in which I add a number of hosts to an ovirt engine. To minimize the time the script takes, I would like to call host_service.setup_network() and host_service.commit_net_config() for each host with async=True and then get into a loop checking every few seconds for the status of the hosts until all of them have finished (so I can go on with another task such as configuring storage). I was able to do something similar for the install phase checking if host.status equals HostStatus.MAINTENANCE , but I cannot find in the documentation how to check when a host is in status "reconfiguring network". The web interface shows this, so surely there must be a way, but I have not managed to find it in the API documentation. Could somebody help? Thanks in advance! -- Eduardo Mayoral Jimeno Systems engineer, platform department. Arsys Internet. emayoral(a)arsys.es - +34 941 620 105 - ext 2153

1 0

Re: Migrate HE between ISCSI storages
by Strahil 14 Mar '19

14 Mar '19

If you have the will, would you create a short but detailed instruction ? I think that it will be nice to have your experience documented in the ovirt docs. Best Regards, Strahil NikolovOn Mar 14, 2019 06:51, kiv(a)intercom.pro wrote: > > I went the other way. Created another HE one on a new host. On a separate server, make the export domain, connected it to both HE and migrated all vm through export / import between HE. Everything went quickly and without problems. > _______________________________________________ > 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/QR722D7VHFLPM…

1 0

Re: Migrate HE between ISCSI storages
by Strahil 13 Mar '19

13 Mar '19

I don't think you can do it from the UI. The problems is that there are several tar files that contain the location of the disks and that is being read by ovirt-ha-agent on all hosts. I think that someone with deeper experience can get involved. From System Administrator perspective I would just swap the target names (old gets new target name, new one gets old target name), but this is only if the iSCSI target is not used for anything else. Best Regards, Strahil NikolovOn Mar 11, 2019 11:25, kiv(a)intercom.pro wrote: > > Yes. > > Open Storage->Disks>Move_disk_HostedEngine: > > Error. > > The migrate of the disk of any other VM is successful. > _______________________________________________ > 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/M5QRRBKBGEIEV…

3 2

VM has been paused due to a storage I/O error
by xilazz＠126.com 13 Mar '19

13 Mar '19

Hi, everyone, there is a VM in the HostedEngine virtual machine that has been paused due to a storage I/O error, but engine manager services are normal, what is the problem?

3 3

Hi question about Version 3 API deprecation.
by Jacob Green 13 Mar '19

13 Mar '19

I see events in the event log of my 4.2.6.4-1.el7 ovirt engine that say the following. "Client from address "10.1.1.50" is using version 3 of the API, which has been deprecated since version 4.0 of the engine, and will no longer be supported starting with version 4.4. Make sure to update that client to use a supported versions of the API and the SDKs, before upgrading to version 4.4 of the engine." The question I have is the API of what precisely? I am just trying to determine what I need to update on the client machine to be supported. The client machines are using CentOS 7.4 or newer, and remote viewer to bring back windows desktops. I could assume it is "remote viewer" I need to update, but I thought I would ask here and see what is known about this error message. Thank you. -- Jacob Green Systems Admin

3 4

Re: ConnectStoragePoolVDS failed
by Strahil 13 Mar '19

13 Mar '19

There were some issues with the migration. Check that all files/directories are owned by vdsm:kvm . Best Regards, Strahil Nikolov

1 0

ConnectStoragePoolVDS failed
by Николаев Алексей 13 Mar '19

13 Mar '19

3 3