OVirt new cluster host only logins on one iSCSI
Hello all, I have a Hosted engine Setup, 2 physical hosts, 1 for virtualization and another for managing OVirt. I've setup the storage via iSCSI, with 2 sessions tcp: [1] *.*.*.*:3260,1 iqn.1992**************** (non-flash) tcp: [2] *.*.*.*:3260,2 iqn.1992**************** (non-flash) Everything is working as expected until I added a new physical host to the cluster. The new host only establishes 1 iSCSI session. If I add the session manually afterwards: iscsiadm -m node -l I do get both sessions but if I put the host in maintenance it only logs out from the one that the OVirt made. Is there a way to force the new added host to login in the same iscsi targets as the other host? OVirt Engine Version: 4.0.5.5-1.el7.centos CentOS Linux release 7.3.1611 (Core) Regards, -- Duarte Fernandes Rocha <dfr@eurotux.com>
On Thu, Mar 2, 2017 at 5:55 PM, Duarte Fernandes Rocha <dfr@eurotux.com> wrote:
Hello all,
I have a Hosted engine Setup, 2 physical hosts, 1 for virtualization and another for managing OVirt.
The host that runs the engine VM could also run other VMs at the same time. On the other side, only if both the hosts could run the engine VM, ovirt-ha-agent is ensuring HA: HA on a single host is not HA.
I've setup the storage via iSCSI, with 2 sessions
tcp: [1] *.*.*.*:3260,1 iqn.1992**************** (non-flash)
tcp: [2] *.*.*.*:3260,2 iqn.1992**************** (non-flash)
Everything is working as expected until I added a new physical host to the cluster. The new host only establishes 1 iSCSI session.
If I add the session manually afterwards:
iscsiadm -m node -l
I do get both sessions but if I put the host in maintenance it only logs out from the one that the OVirt made.
Is there a way to force the new added host to login in the same iscsi targets as the other host?
Deploy it as an hosted-engine host from the webui.
OVirt Engine Version: 4.0.5.5-1.el7.centos
CentOS Linux release 7.3.1611 (Core)
Regards,
--
Duarte Fernandes Rocha <dfr@eurotux.com>
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi Simone, Thanks for your reply. Maybe I did not explain myself correctly.
I have a Hosted engine Setup, 2 physical hosts, 1 for virtualization and another for managing OVirt.
The host that runs the engine VM could also run other VMs at the same time. On the other side, only if both the hosts could run the engine VM, ovirt-ha-agent is ensuring HA: HA on a single host is not HA.
The engine is installed on a host with no virtualization capabilities, it is only used for managing the host agents.
I've setup the storage via iSCSI, with 2 sessions
tcp: [1] *.*.*.*:3260,1 iqn.1992**************** (non-flash)
tcp: [2] *.*.*.*:3260,2 iqn.1992**************** (non-flash)
Everything is working as expected until I added a new physical host to the cluster. The new host only establishes 1 iSCSI session.
If I add the session manually afterwards:
iscsiadm -m node -l
I do get both sessions but if I put the host in maintenance it only logs out from the one that the OVirt made.
Is there a way to force the new added host to login in the same iscsi targets as the other host?
Deploy it as an hosted-engine host from the webui.
The other host is not deployed (which is working properly) as a "hosted-engine", do I need re- deploy it as a "hosted-engine"? I am not using a Self Hosted Engine VM. Sorry for the confusion/mixup, I am new to OVirt. Regards, -- Duarte Fernandes Rocha <dfr@eurotux.com>
On Thu, Mar 2, 2017 at 6:46 PM, Duarte Fernandes Rocha <dfr@eurotux.com> wrote:
Hi Simone,
Hi,
Thanks for your reply. Maybe I did not explain myself correctly.
I have a Hosted engine Setup, 2 physical hosts, 1 for virtualization and
another for managing OVirt.
The host that runs the engine VM could also run other VMs at the same time.
On the other side, only if both the hosts could run the engine VM,
ovirt-ha-agent is ensuring HA: HA on a single host is not HA.
The engine is installed on a host with no virtualization capabilities, it is only used for managing the host agents.
If you run 'hosted-engine --deploy', it creates a VM for you and it installes the engine there. You can check it running hosted-engine --vm-status Instead if you directly run engine-engine setup on bare metal you are going to directly install the engine on bare metal. In that case you the server where you install the engine has no direct access to the LUN used to create the storage domains.
I've setup the storage via iSCSI, with 2 sessions
tcp: [1] *.*.*.*:3260,1 iqn.1992**************** (non-flash)
tcp: [2] *.*.*.*:3260,2 iqn.1992**************** (non-flash)
Everything is working as expected until I added a new physical host to the
cluster. The new host only establishes 1 iSCSI session.
If I add the session manually afterwards:
iscsiadm -m node -l
I do get both sessions but if I put the host in maintenance it only logs
out from the one that the OVirt made.
Is there a way to force the new added host to login in the same iscsi
targets as the other host?
Deploy it as an hosted-engine host from the webui.
The other host is not deployed (which is working properly) as a "hosted-engine", do I need re-deploy it as a "hosted-engine"?
I am not using a Self Hosted Engine VM.
Sorry for the confusion/mixup, I am new to OVirt.
Regards,
--
Duarte Fernandes Rocha <dfr@eurotux.com>
Hello,
Thanks for your reply. Maybe I did not explain myself correctly.
I have a Hosted engine Setup, 2 physical hosts, 1 for virtualization
and
another for managing OVirt.
The host that runs the engine VM could also run other VMs at the same
time.
On the other side, only if both the hosts could run the engine VM,
ovirt-ha-agent is ensuring HA: HA on a single host is not HA.
The engine is installed on a host with no virtualization capabilities, it is only used for managing the host agents.
Instead if you directly run engine-engine setup on bare metal you are going to directly install the engine on bare metal. In that case you the server where you install the engine has no direct access to the LUN used to create the storage domains.
Yes, I run the engine on "bare metal". I do not want for this server to see the storage domain. I have server-engine, server-host1 and now server-host2. server-engine has only the OVirt engine server-host1 is my main server runing now several VMs, with 4 storage domains via iSCSI server-host2 is a new server I added to the default cluster. All is working well except server-host2 has only one iSCSI session established and server-host1 has two sessions (the storage has two iSCSI interfaces active-backup) and server-host1 has two paths to every storage domain and server-host2 only has one. I think it could be because at the time I was adding the server to the cluster (web UI) I was also allowing it on the storage iSCSI and maybe the iscsi was not available the first time it tried to connect.... But I already tried removing the host and re-adding but i still only creates on2 iscsi session. Regards, -- Duarte Fernandes Rocha <dfr@eurotux.com>
Hi, Could it be because of this: /http://www.ovirt.org/documentation/admin-guide/chap-Storage//[1] Adding iSCSI Storage ... Important: If more than one path access is required, ensure to discover and log in to the target through all the required paths. Modifying a storage domain to add additional paths is currently not supported. It's true that the second iscsi path was discovered later, and on the host1 I am not able to put on maintenance to check if both iscsi sessions are disconnected, but according to that documentation it is not currectly suported. Is there a way to do it without removing the storage and importing it again (this is not an option at this point..)? Regards, -- Duarte Fernandes Rocha <dfr@eurotux.com> Administrador de Sistemas Sénior | Engenheiro de Software Eurotux Informática, S.A. | www.eurotux.com Tel: (+351) 253680300 - Suporte: (+351) 253680301 Fax: (+351) 253680319 -------- [1] http://www.ovirt.org/documentation/admin-guide/chap-Storage/
Hello, For anyone interested this is how I solved the problem. First, please note that as I mentioned earlier the OVirt documentation states that ALL the iscsi sessions/paths must be configured when adding the storage domain: http://www.ovirt.org/documentation/admin-guide/chap-Storage/ Adding iSCSI Storage ... Important: If more than one path access is required, ensure to discover and log in to the target through all the required paths. Modifying a storage domain to add additional paths is currently not supported. So one way to fix this issue is: 1. Put the Storage domain under maintenance 2. Remove the storage domain from the datacenter (do not wipe/format) 3. Import storage domain using all the iscsi paths Another way that I think is better because it does not involve deleting the storage domain is to use the REST API and/or OVirt Shell. The storage domain must be in maintenance and the iscsi storage connection must exist. The upside is that the storage domain does not have to be deleted and imported which may not be easy if there are VMs using that storage domain. First we need to have the storage domain ID and the storage connection ID (this one I got using the first method on an empty LUN) [oVirt shell (connected)]# list storagedomains id : d591d9f0-..... name : ISO_DOMAIN description: ISO_DOMAIN id : 7d30dff2-..... name : LUN description: ISCSI LUN [oVirt shell (connected)]# list storageconnections id : b793b463-..... id : 65300f39-.... [oVirt shell (connected)]# show storageconnection 65300f39-ac93-423a-9692-15984f842ae2 id : 65300f39-..... address : ip.addr.x.x port : 3260 target : iqn.1992-04.... type : iscsi username: username With this info make a POST request to the API using curl #!/bin/sh -ex # https://ovirt.addr/ovirt-engine/api/storagedomains/STORAGE-DOMAIN-ID/storage... url="https://ovirt.addr/ovirt-engine/api/storagedomains/521fcfdc-...../storagecon..." User="admin at internal" password="*********" curl \ --insecure \ --user "${user}:${password}" \ --request POST \ --header "Accept: application/xml" --header "Content-Type: application/xml" \ --data ' <storage_connection id="430ee71d-......"> </storage_connection> ' \ "${url}" If there are easier/simpler ways please let me know =) -- Duarte Fernandes Rocha <dfr@eurotux.com>
How to find the relation between "list storagedomains" and "list storageconnections"? 2017-03-07 17:55 GMT+01:00 Duarte Fernandes Rocha <dfr@eurotux.com>:
Hello,
For anyone interested this is how I solved the problem.
First, please note that as I mentioned earlier the OVirt documentation states that ALL the iscsi sessions/paths must be configured when adding the storage domain:
http://www.ovirt.org/documentation/admin-guide/chap-Storage/
Adding iSCSI Storage
...
Important: If more than one path access is required, ensure to discover and log in to the target through all the required paths. Modifying a storage domain to add additional paths is currently not supported.
So one way to fix this issue is:
1. Put the Storage domain under maintenance
2. Remove the storage domain from the datacenter (do not wipe/format)
3. Import storage domain using all the iscsi paths
Another way that I think is better because it does not involve deleting the storage domain is to use the REST API and/or OVirt Shell.
The storage domain must be in maintenance and the iscsi storage connection must exist. The upside is that the storage domain does not have to be deleted and imported which may not be easy if there are VMs using that storage domain.
First we need to have the storage domain ID and the storage connection ID (this one I got using the first method on an empty LUN)
[oVirt shell (connected)]# list storagedomains
id : d591d9f0-.....
name : ISO_DOMAIN
description: ISO_DOMAIN
id : 7d30dff2-.....
name : LUN
description: ISCSI LUN
[oVirt shell (connected)]# list storageconnections
id : b793b463-.....
id : 65300f39-....
[oVirt shell (connected)]# show storageconnection 65300f39-ac93-423a-9692- 15984f842ae2
id : 65300f39-.....
address : ip.addr.x.x
port : 3260
target : iqn.1992-04....
type : iscsi
username: username
With this info make a POST request to the API using curl
#!/bin/sh -ex
# https://ovirt.addr/ovirt-engine/api/storagedomains/STORAGE-DOMAIN-ID/ storageconnections
url="https://ovirt.addr/ovirt-engine/api/storagedomains/521fcfdc-...../ storageconnections"
User="admin at internal"
password="*********"
curl \
--insecure \
--user "${user}:${password}" \
--request POST \
--header "Accept: application/xml" --header "Content-Type: application/xml" \
--data '
<storage_connection id="430ee71d-......">
</storage_connection>
' \
"${url}"
If there are easier/simpler ways please let me know =)
--
Duarte Fernandes Rocha <dfr@eurotux.com>
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi,
How to find the relation between "list storagedomains" and "list storageconnections"?
To find out which storage connections a specific storage domain is using you could do: show storagedomain STORAGE_DOMAIN-ID or with curl via REST API curl --insecure --user user --request GET https://ovirt.host/ovirt-engine/api/storagedomains/STORAGE_DOMAIN_ID But it does not give the storage connection ID, I used the storage-volume_group-logical_unit-address storage-volume_group-logical_unit-portal to match them with the storage connection...there might be a way but I do not know :( Regards, -- Duarte Rocha <dfr@eurotux.com>
participants (3)
-
Duarte Fernandes Rocha -
Marcin Kruk -
Simone Tiraboschi