[ovirt-users] Re: ovirt-ha-agent

2021-01-18 Thread Aries Ahito
its fine now. i just shutdown and start the engine using hosted-engine
--vm-shutdown hosted-engine --vm-start

thank you very much

On Mon, 18 Jan 2021, 21:19 Yedidyah Bar David,  wrote:

> After you removed the hosts, and before you added them again: Did you
> reinstall the OS? If not, there might be some mess left behind.
> I suggest to try again: Remove a host, reinstall the OS on it, then
> add it back and make sure you choose "Deploy". Then give it some time
> to update (should not be more than a few minutes, let's say 1 hour).
> If it still does not look good, please check/share all relevant logs.
> Thanks.
>
> Best regards,
>
> On Mon, Jan 18, 2021 at 3:14 PM Aries Ahito 
> wrote:
> >
> > i tried all to remove all the hosts. run clean self hosted engine
> deployment. then i tried to add host again. and in hosted-engine tab. i
> tick drop down and chose "deploy".
> >
> > after adding all host have active ovirt-ha-agent and have score of
> (3400) when i tried to migrate the hosted-engine it keeps on failing.
> except for number 8 hosts. i can now migrated from host 1 and host 8. but
> rest of the hosts keeps failing..
> >
> > On Sun, Jan 17, 2021 at 4:15 PM Aries Ahito 
> wrote:
> >>
> >> 1. yes
> >>
> >> 2. yes it can migrate any of the hosts
> >>
> >> 3. yes we just tried the new ovirt 4.4. then we decided to used fiber
> ports and have it bonded. so we reinstalled everything from sratch.
> >>
> >> 4. Host 1 and the rest of the hosta was completely reinstalled from
> sratch.  even our separate glusterfs storage we deleted the volumes bricks
> and redo everything. ok ill check it later thanks for your prompt response.
> >>
> >>
> >>
> >>
> >> On Sun, 17 Jan 2021, 16:01 Yedidyah Bar David,  wrote:
> >>>
> >>> On Sun, Jan 17, 2021 at 9:41 AM Aries Ahito 
> wrote:
> >>> >
> >>> > Hi Yedidyah. yep we reinstall everything from scratch even the
> operating system we reinstalled it. so technically its a fresh install.
> >>> >
> >>> > after successfully setting up the hosted-engine we did add  the rest
> of the node. when i check the node status. its says ovirt agent HA N/A
> >>>
> >>> Let me understand:
> >>>
> >>> 1. You had a hosted-engine setup. You started this by deploying on one
> >>> host, let's call it host1, and then added another one, let's call it
> >>> host2. Right? Perhaps you had more than 2, that's not the point, for
> >>> now.
> >>>
> >>> 2. At this point, you could migrate engine VM from host1 to host2 and
> >>> back and it all worked.
> >>>
> >>> 3. Then you decided to reinstall. It sounds like you reinstalled the
> >>> OS on host1, and then did another hosted-engine deployment there. Did
> >>> you also use backup? --restore-from-file? Did you use new storage?
> >>> Existing? If existing, did you clear it before reinstalling?
> >>>
> >>> 4. Assuming that you somehow got to a good state re host1, host2 now
> >>> still points at the old hosted-engine storage domain, so does not
> >>> "see" the new deployment. You should reinstall the OS there, and then
> >>> add it as a host to the new engine. Make sure you mark the checkbox
> >>> "hosted-engine" in "Add host" dialog.
> >>>
> >>> Best regards,
> >>>
> >>> >
> >>> > On Sun, 17 Jan 2021, 15:32 Yedidyah Bar David, 
> wrote:
> >>> >>
> >>> >> On Sat, Jan 16, 2021 at 4:31 AM Ariez Ahito <
> aristotleah...@gmail.com> wrote:
> >>> >> >
> >>> >> > last dec i installed hosted-engine seems to be working, we can
> migrate the engine to different host. but we need to reinstall everything
> because of gluster additional configuration.
> >>> >> > so we did installed hosted-engine. but as per checking. we cannot
> migrate the engine to other hosts. and the ovirt-ha-agent and
> ovirt-ha-broker is status is inactive (dead) what are we missing?
> >>> >>
> >>> >> Please clarify what exact steps you took.
> >>> >>
> >>> >> Did you reinstall everything? How?
> >>> >>
> >>> >> Did you reinstall just one host? How?
> >>> >>
> >>> >> Best regards,
> >>> >> --
> >>> >> Didi
> >>> >>
> >>>
> >>>
> >>> --
> >>> Didi
> >>>
> >
> >
> > --
> > Aristotle D. Ahito
> > --
> >
>
>
> --
> Didi
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/Z3JMZLZMHKC3JFDHKL2DAHNKVQ4TRV2B/


[ovirt-users] Re: ovirt-ha-agent

2021-01-17 Thread Aries Ahito
1. yes

2. yes it can migrate any of the hosts

3. yes we just tried the new ovirt 4.4. then we decided to used fiber ports
and have it bonded. so we reinstalled everything from sratch.

4. Host 1 and the rest of the hosta was completely reinstalled from
sratch.  even our separate glusterfs storage we deleted the volumes bricks
and redo everything. ok ill check it later thanks for your prompt response.




On Sun, 17 Jan 2021, 16:01 Yedidyah Bar David,  wrote:

> On Sun, Jan 17, 2021 at 9:41 AM Aries Ahito 
> wrote:
> >
> > Hi Yedidyah. yep we reinstall everything from scratch even the operating
> system we reinstalled it. so technically its a fresh install.
> >
> > after successfully setting up the hosted-engine we did add  the rest of
> the node. when i check the node status. its says ovirt agent HA N/A
>
> Let me understand:
>
> 1. You had a hosted-engine setup. You started this by deploying on one
> host, let's call it host1, and then added another one, let's call it
> host2. Right? Perhaps you had more than 2, that's not the point, for
> now.
>
> 2. At this point, you could migrate engine VM from host1 to host2 and
> back and it all worked.
>
> 3. Then you decided to reinstall. It sounds like you reinstalled the
> OS on host1, and then did another hosted-engine deployment there. Did
> you also use backup? --restore-from-file? Did you use new storage?
> Existing? If existing, did you clear it before reinstalling?
>
> 4. Assuming that you somehow got to a good state re host1, host2 now
> still points at the old hosted-engine storage domain, so does not
> "see" the new deployment. You should reinstall the OS there, and then
> add it as a host to the new engine. Make sure you mark the checkbox
> "hosted-engine" in "Add host" dialog.
>
> Best regards,
>
> >
> > On Sun, 17 Jan 2021, 15:32 Yedidyah Bar David,  wrote:
> >>
> >> On Sat, Jan 16, 2021 at 4:31 AM Ariez Ahito 
> wrote:
> >> >
> >> > last dec i installed hosted-engine seems to be working, we can
> migrate the engine to different host. but we need to reinstall everything
> because of gluster additional configuration.
> >> > so we did installed hosted-engine. but as per checking. we cannot
> migrate the engine to other hosts. and the ovirt-ha-agent and
> ovirt-ha-broker is status is inactive (dead) what are we missing?
> >>
> >> Please clarify what exact steps you took.
> >>
> >> Did you reinstall everything? How?
> >>
> >> Did you reinstall just one host? How?
> >>
> >> Best regards,
> >> --
> >> Didi
> >>
>
>
> --
> Didi
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BTYWWJRTY7YPZLOXJ5UVQSJMLJ6N7XPA/


[ovirt-users] Re: ovirt-ha-agent

2021-01-16 Thread Aries Ahito
Hi Yedidyah. yep we reinstall everything from scratch even the operating
system we reinstalled it. so technically its a fresh install.

after successfully setting up the hosted-engine we did add  the rest of the
node. when i check the node status. its says ovirt agent HA N/A

On Sun, 17 Jan 2021, 15:32 Yedidyah Bar David,  wrote:

> On Sat, Jan 16, 2021 at 4:31 AM Ariez Ahito 
> wrote:
> >
> > last dec i installed hosted-engine seems to be working, we can migrate
> the engine to different host. but we need to reinstall everything because
> of gluster additional configuration.
> > so we did installed hosted-engine. but as per checking. we cannot
> migrate the engine to other hosts. and the ovirt-ha-agent and
> ovirt-ha-broker is status is inactive (dead) what are we missing?
>
> Please clarify what exact steps you took.
>
> Did you reinstall everything? How?
>
> Did you reinstall just one host? How?
>
> Best regards,
> --
> Didi
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WWAGEHTFSHMTMZNBV7RPTPX42Z3CTBD2/


[ovirt-users] Re: Adding host to hosted engine fails

2020-12-17 Thread Aries Ahito
im using ovirt 4.4
of course glusterd is running since i already manage to deploy
hosted-engine on node1
ill attached again the vdsm logs.

On Thu, Dec 17, 2020 at 5:29 PM Ritesh Chikatwar 
wrote:

> Hello,
>
>
> Which version of ovirt are you using?
> Can you make sure gluster service is running or not because i see an error
> as Could not connect to storageServer.
> Also please share the engine log as well and a few more lines after the
> error occurred in vdsm.
>
> Ritesh
>
> On Thu, Dec 17, 2020 at 12:00 PM Ariez Ahito 
> wrote:
>
>> here is our setup
>> stand alone glusterfs storage replica3
>> 10.33.50.33
>> 10.33.50.34
>> 10.33.50.35
>>
>> we deployed hosted-engine and managed to connect to our glusterfs storage
>>
>> now we are having issues adding hosts
>>
>> here is the logs
>> dsm.gluster.exception.GlusterVolumesListFailedException: Volume list
>> failed: rc=1 out=() err=['Command {self.cmd} failed with rc={self.rc}
>> out={self.out!r} err={self.err!r}']
>> 2020-12-17 14:22:27,106+0800 INFO  (jsonrpc/4)
>> [storage.StorageDomainCache] Invalidating storage domain cache (sdc:74)
>> 2020-12-17 14:22:27,106+0800 INFO  (jsonrpc/4) [vdsm.api] FINISH
>> connectStorageServer return={'statuslist': [{'id':
>> 'afa2d41a-d817-4f4a-bd35-5ffedd1fa65b', 'status': 4149}]}
>> from=:::10.33.0.10,50058, flow_id=6170eaa3,
>> task_id=f00d28fa-077f-403a-8024-9f9b533bccb5 (api:54)
>> 2020-12-17 14:22:27,107+0800 INFO  (jsonrpc/4) [jsonrpc.JsonRpcServer]
>> RPC call StoragePool.connectStorageServer took more than 1.00 seconds to
>> succeed: 3.34 (__init__:316)
>> 2020-12-17 14:22:27,213+0800 INFO  (jsonrpc/6) [vdsm.api] START
>> connectStorageServer(domType=7,
>> spUUID='1abdb9e4-3f85-11eb-9994-00163e4e4935', conList=[{'password':
>> '', 'vfs_type': 'glusterfs', 'port': '', 'mnt_options':
>> 'backup-volfile-servers=gluster3:gluster4', 'iqn': '', 'connection':
>> 'gluster3:/VOL2', 'ipv6_enabled': 'false', 'id':
>> '2fb6989d-b26b-42e7-af35-4e4cf718eebf', 'user': '', 'tpgt': '1'},
>> {'password': '', 'vfs_type': 'glusterfs', 'port': '',
>> 'mnt_options': 'backup-volfile-servers=gluster3:gluster4', 'iqn': '',
>> 'connection': 'gluster3:/VOL3', 'ipv6_enabled': 'false', 'id':
>> 'b7839bcd-c0e3-422c-8f2c-47351d24b6de', 'user': '', 'tpgt': '1'}],
>> options=None) from=:::10.33.0.10,50058, flow_id=6170eaa3,
>> task_id=cfeb3401-54b9-4756-b306-88d4275c0690 (api:48)
>> 2020-12-17 14:22:29,058+0800 INFO  (periodic/1) [vdsm.api] START
>> repoStats(domains=()) from=internal,
>> task_id=e9648d47-2ffb-4387-9a72-af41ab51adf7 (api:48)
>> 2020-12-17 14:22:29,058+0800 INFO  (periodic/1) [vdsm.api] FINISH
>> repoStats return={} from=internal,
>> task_id=e9648d47-2ffb-4387-9a72-af41ab51adf7 (api:54)
>> 2020-12-17 14:22:30,512+0800 ERROR (jsonrpc/6) [storage.HSM] Could not
>> connect to storageServer (hsm:2444)
>>
>>
>> in the events  tab
>> The error message for connection gluster3:/ISO returned by VDSM was:
>> Failed to fetch Gluster Volume List
>> The error message for connection gluster3:/VOL1 returned by VDSM was:
>> Failed to fetch Gluster Volume List
>>
>> thanks
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/AJZNXHOIFHWNDJJ7INI3VNLT46TB3EAW/
>>
>

-- 
Aristotle D. Ahito
--
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/6JHSPVTJ7YDWQF4PZMSRPBCD6HH4AGDG/


[ovirt-users] Re: Cannot connect Glusterfs storage to Ovirt

2020-12-15 Thread Aries Ahito
ok i will try that. ive been using ovirt since 3.4 and we are using san
storage, and we have hosted engine with nfs. this is my first time using
gluster.

On Wed, 16 Dec 2020, 12:42 Parth Dhanjal,  wrote:

> Hey!
>
> Storage connection: 10.33.50.33/VOL1
> Do check if this mount point is correct. You can look for mount points
> through your server terminal
> Mount Option:backup-volfile-servers=<>
> In case you don't have a 3rd host, I'll recommend adding one to the
> cluster. Having a replica 2 volume can cause a split-brain issue is gluster(
> https://docs.gluster.org/en/latest/Troubleshooting/resolving-splitbrain/)
>
>
>
> On Wed, Dec 16, 2020 at 9:44 AM Aries Ahito 
> wrote:
>
>> nope i didnt since i dont know what parameters i will input.. could you
>> help me
>>
>> so i have this gluster with replica 2 configuration
>>
>> 10.33.50.33:/VOL1VOL1
>> 10.33.50.34:/VOL1/VOL1
>>
>> thanks
>>
>> On Wed, Dec 16, 2020 at 12:09 PM Parth Dhanjal  wrote:
>>
>>> Hey!
>>>
>>> Did you input a mount point?
>>> It seems from the error message that either the mount point was missing
>>> or was wrong.
>>>
>>>
>>>
>>> On Wed, Dec 16, 2020 at 6:07 AM Ariez Ahito 
>>> wrote:
>>>
>>>> HI guys, i have installed ovirt 4.4 hosted engine and a separate
>>>> glusterfs storage.
>>>> now during hosted engine deployment when i try do choose
>>>> STORAGE TYPE: gluster
>>>> Storage connection: 10.33.50.33/VOL1
>>>> Mount Option:
>>>>
>>>> when i try to connect
>>>>
>>>> this gives me an error:
>>>> [ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault
>>>> detail is "[Problem while trying to mount target]". HTTP response code is
>>>> 400.
>>>> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg":
>>>> "Fault reason is \"Operation Failed\". Fault detail is \"[Problem while
>>>> trying to mount target]\". HTTP response code is 400."}
>>>> ___
>>>> Users mailing list -- users@ovirt.org
>>>> To unsubscribe send an email to users-le...@ovirt.org
>>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>>> oVirt Code of Conduct:
>>>> https://www.ovirt.org/community/about/community-guidelines/
>>>> List Archives:
>>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/KLPN6P4FMY6LJAD4ETRYLV5PCA7BAV6J/
>>>>
>>>
>>
>> --
>> Aristotle D. Ahito
>> --
>>
>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/5Q3G7YUDY2CM7C7WP3OR42WEZBGVZPD2/


[ovirt-users] Re: Cannot connect Glusterfs storage to Ovirt

2020-12-15 Thread Aries Ahito
nope i didnt since i dont know what parameters i will input.. could you
help me

so i have this gluster with replica 2 configuration

10.33.50.33:/VOL1VOL1
10.33.50.34:/VOL1/VOL1

thanks

On Wed, Dec 16, 2020 at 12:09 PM Parth Dhanjal  wrote:

> Hey!
>
> Did you input a mount point?
> It seems from the error message that either the mount point was missing or
> was wrong.
>
>
>
> On Wed, Dec 16, 2020 at 6:07 AM Ariez Ahito 
> wrote:
>
>> HI guys, i have installed ovirt 4.4 hosted engine and a separate
>> glusterfs storage.
>> now during hosted engine deployment when i try do choose
>> STORAGE TYPE: gluster
>> Storage connection: 10.33.50.33/VOL1
>> Mount Option:
>>
>> when i try to connect
>>
>> this gives me an error:
>> [ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault
>> detail is "[Problem while trying to mount target]". HTTP response code is
>> 400.
>> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault
>> reason is \"Operation Failed\". Fault detail is \"[Problem while trying to
>> mount target]\". HTTP response code is 400."}
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/KLPN6P4FMY6LJAD4ETRYLV5PCA7BAV6J/
>>
>

-- 
Aristotle D. Ahito
--
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/NXZVRJ4ANI6S5D5A7IT6G4LSV5WE3VQF/