- Users - oVirt List Archives

extract nested attribute from a href link with ansible ovirt_vm_facts
by Nathanaël Blanchet 27 Nov '18

27 Nov '18

Hello I'd like to extract all vms which have the lease optionnal attribute and display the name of the storage domain of that lease. I managed to get that dict: "lease": { "storage_domain": { "href": "/ovirt-engine/api/storagedomains/0dc2941a-bdc2-4ce4-8ad7-43fa9c944f88", "id": "0dc2941a-bdc2-4ce4-8ad7-43fa9c944f88" } but how can I get the name of the storage instead of its id? thank you for your help -- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 1

selfhost
by mustafa.taha.mu95＠gmail.com 27 Nov '18

27 Nov '18

Hi , can we build ovirt-selfhost inside ovirt-selfhost ? can anybody answer this question ,please

3 2

Re: Recover accidentally deleted gluster node having bricks ( Engine, Data and Vmstore)
by Kaustav Majumder 27 Nov '18

27 Nov '18

On Tue, Nov 27, 2018 at 4:05 PM Abhishek Sahni <abhishek(a)iiserb.ac.in> wrote: > That is amazing, resetting bricks resolved the issue. > > Thanks much Sahina and Kaustav. > > However, Do we have manual steps to recover those bricks. > https://gluster.readthedocs.io/en/latest/release-notes/3.9.0/ > > On Tue, Nov 27, 2018 at 3:57 PM Abhishek Sahni <abhishek(a)iiserb.ac.in> > wrote: > >> I just enabled it on default cluster and now the volumes are visible. It >> seems like gluster service was disabled by default on cluster. >> >> On Tue, Nov 27, 2018 at 3:51 PM Sahina Bose <sabose(a)redhat.com> wrote: >> >>> >>> >>> On Tue, Nov 27, 2018 at 3:45 PM Kaustav Majumder <kmajumde(a)redhat.com> >>> wrote: >>> >>>> I am not sure why ovirt is not showing any volume. >>>> Sahina, is this a bug? >>>> >>> >>> Check if gluster service is enabled on the cluster. >>> The volumes are managed only if this is true >>> >>> >>>> On Tue, Nov 27, 2018 at 3:10 PM Abhishek Sahni < >>>> abhishek.sahni1991(a)gmail.com> wrote: >>>> >>>>> Hello Kaustav, >>>>> >>>>> That's weird, I never saw any volumes under the storage tab since >>>>> installation. I am using HC setup deployed using cockpit console. >>>>> >>>>> https://imgur.com/a/nH9rzK8 >>>>> >>>>> Did I miss something? >>>>> >>>>> >>>>> On Tue, Nov 27, 2018 at 2:50 PM Kaustav Majumder <kmajumde(a)redhat.com> >>>>> wrote: >>>>> >>>>>> Click on volume for which you want to reset the brick-> under bricks >>>>>> tab select the brick you wan to reset -> once you do you will see the >>>>>> 'Reset Brick' option is active. >>>>>> Attached is a screenshot -> https://i.imgur.com/QUMSrzt.png >>>>>> >>>>>> On Tue, Nov 27, 2018 at 2:43 PM Abhishek Sahni < >>>>>> abhishek.sahni1991(a)gmail.com> wrote: >>>>>> >>>>>>> Thanks Sahina for your response, I am not able to find it on UI, >>>>>>> please help me to navigate? and yes I am using oVirt 4.2.6.4-1. >>>>>>> >>>>>>> On Tue, Nov 27, 2018 at 12:55 PM Sahina Bose <sabose(a)redhat.com> >>>>>>> wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Tue, Nov 20, 2018 at 5:56 PM Abhishek Sahni < >>>>>>>> abhishek.sahni1991(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> Hello Team, >>>>>>>>> >>>>>>>>> We are running a setup of 3-way replica HC gluster setup >>>>>>>>> configured during the initial deployment from the cockpit console using >>>>>>>>> ansible. >>>>>>>>> >>>>>>>>> NODE1 >>>>>>>>> - /dev/sda (OS) >>>>>>>>> - /dev/sdb ( Gluster Bricks ) >>>>>>>>> * /gluster_bricks/engine/engine/ >>>>>>>>> * /gluster_bricks/data/data/ >>>>>>>>> * /gluster_bricks/vmstore/vmstore/ >>>>>>>>> >>>>>>>>> NODE2 and NODE3 with a similar setup. >>>>>>>>> >>>>>>>>> There is a mishap that /dev/sdb on NODE2 totally got crashed and >>>>>>>>> now there is nothing inside. However, I have created similar directories >>>>>>>>> after mounting it back i.e., >>>>>>>>> >>>>>>>>> * /gluster_bricks/engine/engine/ >>>>>>>>> * /gluster_bricks/data/data/ >>>>>>>>> * /gluster_bricks/vmstore/vmstore/ >>>>>>>>> but it is not yet recovered. >>>>>>>>> >>>>>>>>> ===================================================== >>>>>>>>> [root@node2 ~]# gluster volume status >>>>>>>>> Status of volume: data >>>>>>>>> Gluster process TCP Port RDMA Port >>>>>>>>> Online Pid >>>>>>>>> >>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>> Brick *.*.*.1:/gluster_bricks/data/data 49152 0 Y >>>>>>>>> 11111 >>>>>>>>> Brick *.*.*.2:/gluster_bricks/data/data N/A N/A N >>>>>>>>> N/A >>>>>>>>> Brick *.*.*.3:/gluster_bricks/data/data 49152 0 Y >>>>>>>>> 4303 >>>>>>>>> Self-heal Daemon on localhost N/A N/A >>>>>>>>> Y 23976 >>>>>>>>> Self-heal Daemon on *.*.*.1 N/A N/A Y >>>>>>>>> 27838 >>>>>>>>> Self-heal Daemon on *.*.*.3 N/A N/A Y >>>>>>>>> 27424 >>>>>>>>> >>>>>>>>> Task Status of Volume data >>>>>>>>> >>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>> There are no active volume tasks >>>>>>>>> >>>>>>>>> Status of volume: engine >>>>>>>>> Gluster process TCP Port RDMA Port >>>>>>>>> Online Pid >>>>>>>>> >>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>> Brick *.*.*.1:/gluster_bricks/engine/eng >>>>>>>>> ine 49153 0 >>>>>>>>> Y 11117 >>>>>>>>> Brick *.*.*.2:/gluster_bricks/engine/eng >>>>>>>>> ine N/A N/A >>>>>>>>> N N/A >>>>>>>>> Brick *.*.*.3:/gluster_bricks/engine/eng >>>>>>>>> ine 49153 0 >>>>>>>>> Y 4314 >>>>>>>>> Self-heal Daemon on localhost N/A N/A >>>>>>>>> Y 23976 >>>>>>>>> Self-heal Daemon on *.*.*.3 N/A N/A Y >>>>>>>>> 27424 >>>>>>>>> Self-heal Daemon on *.*.*.1 N/A N/A Y >>>>>>>>> 27838 >>>>>>>>> >>>>>>>>> Task Status of Volume engine >>>>>>>>> >>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>> There are no active volume tasks >>>>>>>>> >>>>>>>>> Status of volume: vmstore >>>>>>>>> Gluster process TCP Port RDMA Port >>>>>>>>> Online Pid >>>>>>>>> >>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>> Brick *.*.*.1:/gluster_bricks/vmstore/vm >>>>>>>>> store 49154 0 >>>>>>>>> Y 21603 >>>>>>>>> Brick *.*.*.2:/gluster_bricks/vmstore/vm >>>>>>>>> store N/A N/A >>>>>>>>> N N/A >>>>>>>>> Brick *.*.*.3:/gluster_bricks/vmstore/vm >>>>>>>>> store 49154 0 >>>>>>>>> Y 26845 >>>>>>>>> Self-heal Daemon on localhost N/A N/A >>>>>>>>> Y 23976 >>>>>>>>> Self-heal Daemon on *.*.*.3 N/A N/A Y >>>>>>>>> 27424 >>>>>>>>> Self-heal Daemon on *.*.*.1 N/A N/A Y >>>>>>>>> 27838 >>>>>>>>> >>>>>>>>> Task Status of Volume vmstore >>>>>>>>> >>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>> There are no active volume tasks >>>>>>>>> ============================================================= >>>>>>>>> >>>>>>>>> >>>>>>>>> Can someone please suggest the steps to recover the setup? >>>>>>>>> >>>>>>>>> I have tried the below workaround but it doesn't help. >>>>>>>>> >>>>>>>>> >>>>>>>>> https://lists.gluster.org/pipermail/gluster-users/2013-November/015079.html >>>>>>>>> >>>>>>>> >>>>>>>> You can reset the brick - if you're on oVirt 4.2.x, there's a UI >>>>>>>> option in the bricks subtab to do this. >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> ABHISHEK SAHNI >>>>>>>>> Mob : +91-990-701-5143 >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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/WFYUBA4DPHOSA… >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> ABHISHEK SAHNI >>>>>>> Mob : +91-990-701-5143 >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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/GEZZIGBWA6HQ5… >>>>>>> >>>>>> >>>>>> >>>>>> Thanks, >>>>>> Kaustav >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> ABHISHEK SAHNI >>>>> Mob : +91-990-701-5143 >>>>> >>>>> >>>>> >>>> >>>> -- >>>> >>>> KAUSTAV MAJUMDER >>>> >>>> ASSOCIATE SOFTWARE ENGINEER >>>> >>>> Red Hat India PVT LTD. <https://www.redhat.com/> >>>> >>>> kmajumder(a)redhat.com M: 08981884037 IM: IRC: kmajumder >>>> <https://red.ht/sig> >>>> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >>>> @redhatway <https://twitter.com/redhatway> @redhatinc >>>> <https://instagram.com/redhatinc> @redhatsnaps >>>> <https://snapchat.com/add/redhatsnaps> >>>> >>> >> >> -- >> Thanks, >> >> Abhishek Sahni >> Computer Centre >> IISER Bhopal >> > > > -- > Thanks, > > Abhishek Sahni > Computer Centre > IISER Bhopal > Thanks, Kaustav

2 2

Remote console access for old Ovirt 3.6 install
by David Gossage 27 Nov '18

27 Nov '18

I have an older 3.6.7 setup I am still using at a location. The hosted-engine is up but not responding {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "up"} I am guessing it got into some paused or halted state after a power outage and storage went offline for a short bit and I may need to manually perform some tasks. When I attempt the suggested method of hosted-engine --set-maintenance --mode=global hosted-engine --console I get an error about Use the password you've set using --add-console-password for logging in ** (remote-viewer:11479): WARNING **: Could not open X display Cannot open display: Run 'remote-viewer --help' to see a full list of available command line options Their are 7 other VM's running I was able to manually continue from vdsClient Is their a way to get remote access to this engine? *David Gossage* *Carousel Checks Inc. | System Administrator* *Office* 708.613.2284

2 2

Recover accidentally deleted gluster node having bricks ( Engine, Data and Vmstore)
by Abhishek Sahni 27 Nov '18

27 Nov '18

Hello Team, We are running a setup of 3-way replica HC gluster setup configured during the initial deployment from the cockpit console using ansible. NODE1 - /dev/sda (OS) - /dev/sdb ( Gluster Bricks ) * /gluster_bricks/engine/engine/ * /gluster_bricks/data/data/ * /gluster_bricks/vmstore/vmstore/ NODE2 and NODE3 with a similar setup. There is a mishap that /dev/sdb on NODE2 totally got crashed and now there is nothing inside. However, I have created similar directories after mounting it back i.e., * /gluster_bricks/engine/engine/ * /gluster_bricks/data/data/ * /gluster_bricks/vmstore/vmstore/ but it is not yet recovered. ===================================================== [root@node2 ~]# gluster volume status Status of volume: data Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick *.*.*.1:/gluster_bricks/data/data 49152 0 Y 11111 Brick *.*.*.2:/gluster_bricks/data/data N/A N/A N N/A Brick *.*.*.3:/gluster_bricks/data/data 49152 0 Y 4303 Self-heal Daemon on localhost N/A N/A Y 23976 Self-heal Daemon on *.*.*.1 N/A N/A Y 27838 Self-heal Daemon on *.*.*.3 N/A N/A Y 27424 Task Status of Volume data ------------------------------------------------------------------------------ There are no active volume tasks Status of volume: engine Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick *.*.*.1:/gluster_bricks/engine/eng ine 49153 0 Y 11117 Brick *.*.*.2:/gluster_bricks/engine/eng ine N/A N/A N N/A Brick *.*.*.3:/gluster_bricks/engine/eng ine 49153 0 Y 4314 Self-heal Daemon on localhost N/A N/A Y 23976 Self-heal Daemon on *.*.*.3 N/A N/A Y 27424 Self-heal Daemon on *.*.*.1 N/A N/A Y 27838 Task Status of Volume engine ------------------------------------------------------------------------------ There are no active volume tasks Status of volume: vmstore Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick *.*.*.1:/gluster_bricks/vmstore/vm store 49154 0 Y 21603 Brick *.*.*.2:/gluster_bricks/vmstore/vm store N/A N/A N N/A Brick *.*.*.3:/gluster_bricks/vmstore/vm store 49154 0 Y 26845 Self-heal Daemon on localhost N/A N/A Y 23976 Self-heal Daemon on *.*.*.3 N/A N/A Y 27424 Self-heal Daemon on *.*.*.1 N/A N/A Y 27838 Task Status of Volume vmstore ------------------------------------------------------------------------------ There are no active volume tasks ============================================================= Can someone please suggest the steps to recover the setup? I have tried the below workaround but it doesn't help. https://lists.gluster.org/pipermail/gluster-users/2013-November/015079.html -- ABHISHEK SAHNI Mob : +91-990-701-5143

4 7

Upgrade 4.0 to 4.1: Global Maintenance Mode not recognized
by gregor 27 Nov '18

27 Nov '18

Hello, I upgraded one host from 4.0 to 4.1 without problems. Now I have a problem with another host, in another network, where the Global Maintenance mode is not recognized by engine-setup. Is there a way to force the setup or set the maintenance mode inside the database? One problem can be that an the host was accidentally upgraded to 4.1 before I upgraded the engine. kind regards gregor

3 6

Re: The user admin@internal is not authorized to perform login
by Greg Sheremeta 26 Nov '18

26 Nov '18

Perhaps Ravi can assist with this. ---------- Forwarded message --------- From: Shawn Southern <shawn.southern(a)entegrus.com> Date: Fri, Nov 23, 2018 at 9:52 PM Subject: [ovirt-users] The user admin@internal is not authorized to perform login To: users(a)ovirt.org <users(a)ovirt.org> No one can log in to our oVirt instance today. LDAP users cannot authenticate, and the internal ‘admin’ user gets “The user admin@internal is not authorized to perform login” after being authenticated. From engine.log: 2018-11-23 10:17:12,454-05 INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-24) [] User admin@internal successfully logged in with scopes: ovirt-app-admin ovirt-app-api ovirt-app-portal ovirt-ext=auth:sequence-priority=~ ovirt-ext=revoke:revoke-all ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2018-11-23 10:17:12,576-05 INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-24) [43bd2e4f] Running command: CreateUserSessionCommand internal: false. 2018-11-23 10:17:12,584-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-24) [43bd2e4f] EVENT_ID: USER_VDC_LOGIN_FAILED(114), User admin@internal-authz connecting from '10.11.12.13' failed to log in<UNKNOWN>. 2018-11-23 10:17:12,585-05 ERROR [org.ovirt.engine.core.aaa.servlet.SsoPostLoginServlet] (default task-24) [] The user admin@internal is not authorized to perform login Where do I go from here? _______________________________________________ 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/OQNDRRXT3EZGG… -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig>

3 2

oVirt impersonation and sessions
by Anastasiya Ruzhanskaya 26 Nov '18

26 Nov '18

Hello everyone! I wanted to find out how the impersonation technique used in oVirt works? I know from libvirt developers, that oVirt opens one connection only for multiple clients. How does this work? Also I found out in source code that in ActionParameterBase class the sessionId field is marked transient but, for example, for GWT rpc message, which goes to the server and says what action will be made (shut down, pause vm) this is the only field in all sent information which says what the session is. Where is the session sent instead? There was also a field with session id in https headers, but this was related to cookie so I am not completely sure if this can help to identify the current user.

2 2

How to kill hanged task listed in engine but not in vdsm-client?
by Stefano Stagnaro 26 Nov '18

26 Nov '18

Hello, I'm struggling with an hanged task. I can see it from RestAPI (and UI) as: <job href="/ovirt-engine/api/jobs/9326a95e-4686-4205-bbac-b552beae4d29" id="9326a95e-4686-4205-bbac-b552beae4d29"> <actions> <link href="/ovirt-engine/api/jobs/9326a95e-4686-4205-bbac-b552beae4d29/clear" rel="clear"/> <link href="/ovirt-engine/api/jobs/9326a95e-4686-4205-bbac-b552beae4d29/end" rel="end"/> </actions> <description>Adding Disk</description> <link href="/ovirt-engine/api/jobs/9326a95e-4686-4205-bbac-b552beae4d29/steps" rel="steps"/> <auto_cleared>true</auto_cleared> <external>false</external> <last_updated>2018-11-23T18:40:59.466+01:00</last_updated> <start_time>2018-11-23T18:06:18.512+01:00</start_time> <status>started</status> <owner href="/ovirt-engine/api/users/6f4573b6-0cf1-4cbb-ac03-bf8e126b394c" id="6f4573b6-0cf1-4cbb-ac03-bf8e126b394c"/> </job> The job is hanged since user has killed fallocate process on the host. However, I can't kill task from the hosts itself since vdsm-client returns zero task on any host: # vdsm-client Host getAllTasksInfo {} How can I deal with it? I already tried to restart ovirt-engine.service but task is still there and prevent me to put the involved storage domain into maintenance. I also tried the "clear" method for service "job" via RestAPI but it fails since it's not an external job. Thank you, -- Stefano Stagnaro Prisma Telecom Testing S.r.l. Via Petrocchi, 4 20127 Milano – Italy Tel. 02 26113507 int 339 e-mail: stefanos(a)prismatelecomtesting.com skype: stefano.stagnaro

3 2

AffinityGroup API
by p.staniforth＠leedsbeckett.ac.uk 26 Nov '18

26 Nov '18

Hello, When using the API to update an AffinityGroup there is a AffinityGroupVm and AffinityGroupVms so I can add or remove VMs but there is no AffinityGroupHost or AffinityGroupHosts, therefore I can't add or remove hosts. Thanks, Paul S.

4 6