[ovirt-users] Re: Hosted engine not starting after 4.3 Upgrade - cannot find OVF_STORE
Thank you!
The ownership of the volume file had changed to root:root. I changed it back
to vdsm:kvm and the hosted engine started.
For anyone else who runs in to this, the file was in:
/rhev/data-center/mnt/glusterSD/ovirtnode-02:_vmstore/79376c46-b80c-4c44-bbb1-80c0714a4b52/images/48ee766b-185d-4928-a046-b048d65af2a6
The errors in vdsm.log that pointed to this:
2019-03-06 08:16:24,470-0500 INFO (jsonrpc/4) [vdsm.api] START
getVolumeInfo(sdUUID=u'79376c46-b80c-4c44-bbb1-80c0714a4b52',
spUUID=u'----',
imgUUID=u'48ee766b-185d-4928-a046-b048d65af2a6',
volUUID=u'687e9c0d-e988-4f76-89ff-931685acdf76', options=None) from=::1,37228,
task_id=8170eec2-b3f7-488c-adda-3f1d9b1d0c57 (api:48)
2019-03-06 08:16:24,472-0500 INFO (jsonrpc/4) [vdsm.api] FINISH getVolumeInfo
error=Volume does not exist: (u'687e9c0d-e988-4f76-89ff-931685acdf76',)
from=::1,37228, task_id=8170eec2-b3f7-488c-adda-3f1d9b1d0c57 (api:52)
2019-03-06 08:16:24,472-0500 INFO (jsonrpc/4) [storage.TaskManager.Task]
(Task='8170eec2-b3f7-488c-adda-3f1d9b1d0c57') aborting: Task is aborted:
"Volume does not exist: (u'687e9c0d-e988-4f76-89ff-931685acdf76',)" - code 201
(task:1181)
2019-03-06 08:16:24,472-0500 INFO (jsonrpc/4) [storage.Dispatcher] FINISH
getVolumeInfo error=Volume does not exist:
(u'687e9c0d-e988-4f76-89ff-931685acdf76',) (dispatcher:81)
From: Jayme
Sent: March 6, 2019 6:51 AM
To: Shawn Southern
Cc: users@ovirt.org
Subject: Re: [ovirt-users] Hosted engine not starting after 4.3 Upgrade -
cannot find OVF_STORE
It sure if this is the same bug I hit but check ownership of the cam images.
There’s a bug in 4.3 upgrade that changes ownership to root and causes vms to
not start until you change back to vdsm
On Wed, Mar 6, 2019 at 4:57 AM Shawn Southern
mailto:shawn.south...@entegrus.com>> wrote:
After running 'hosted-engine --vm-start', the status of the hosted engine VM is:
conf_on_shared_storage : True
Status up-to-date : True
Hostname : ovirtnode-01
Host ID: 3
Engine status : {"reason": "bad vm status", "health":
"bad", "vm": "down_unexpected", "detail": "Down"}
Score : 0
stopped: False
Local maintenance : False
crc32 : 7e3db850
local_conf_timestamp : 3509
Host timestamp : 3508
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=3508 (Tue Mar 5 16:03:30 2019)
host-id=3
score=0
vm_conf_refresh_time=3509 (Tue Mar 5 16:03:31 2019)
conf_on_shared_storage=True
maintenance=False
state=EngineUnexpectedlyDown
stopped=False
timeout=Wed Dec 31 20:05:37 1969
The /var/log/libvirt/qemu/HostedEngine.log has no entries since the hosted
engine VM was rebooted.
/var/log/ovirt-hosted-engine-ha/agent.log:
MainThread::ERROR::2019-03-05
16:07:31,916::config_ovf::42::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store)
Failed scanning for OVF_STORE due to Command Volume.getInfo with args
{'storagepoolID': '----', 'storagedomainID':
'79376c46-b80c-4c44-bbb1-80c0714a4b52', 'volumeID':
u'687e9c0d-e988-4f76-89ff-931685acdf76', 'imageID':
u'48ee766b-185d-4928-a046-b048d65af2a6'} failed:
(code=201, message=Volume does not exist:
(u'687e9c0d-e988-4f76-89ff-931685acdf76',))
MainThread::ERROR::2019-03-05
16:07:31,916::config_ovf::84::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store)
Unable to identify the OVF_STORE volume, falling back to initial vm.conf.
Please ensure you already added your first data domain for regular VMs
MainThread::INFO::2019-03-05
16:07:31,971::hosted_engine::493::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop)
Current state EngineUnexpectedlyDown (score: 0)
MainThread::ERROR::2019-03-05
16:07:42,304::config_ovf::42::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store)
Failed scanning for OVF_STORE due to Command Volume.getInfo with args
{'storagepoolID': '----', 'storagedomainID':
'79376c46-b80c-4c44-bbb1-80c0714a4b52', 'volumeID':
u'687e9c0d-e988-4f76-89ff-931685acdf76', 'imageID':
u'48ee766b-185d-4928-a046-b048d65af2a6'} failed:
(code=201, message=Volume does not exist:
(u'687e9c0d-e988-4f76-89ff-931685acdf76',))
MainThread::ERROR::2019-03-05
16:07:42,305::config_ovf::84::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store)
Unable to identify the OVF_STORE volume, falling back to initial vm.conf.
Ple
[ovirt-users] Hosted engine not starting after 4.3 Upgrade - cannot find OVF_STORE
After running 'hosted-engine --vm-start', the status of the hosted engine VM is:
conf_on_shared_storage : True
Status up-to-date : True
Hostname : ovirtnode-01
Host ID: 3
Engine status : {"reason": "bad vm status", "health":
"bad", "vm": "down_unexpected", "detail": "Down"}
Score : 0
stopped: False
Local maintenance : False
crc32 : 7e3db850
local_conf_timestamp : 3509
Host timestamp : 3508
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=3508 (Tue Mar 5 16:03:30 2019)
host-id=3
score=0
vm_conf_refresh_time=3509 (Tue Mar 5 16:03:31 2019)
conf_on_shared_storage=True
maintenance=False
state=EngineUnexpectedlyDown
stopped=False
timeout=Wed Dec 31 20:05:37 1969
The /var/log/libvirt/qemu/HostedEngine.log has no entries since the hosted
engine VM was rebooted.
/var/log/ovirt-hosted-engine-ha/agent.log:
MainThread::ERROR::2019-03-05
16:07:31,916::config_ovf::42::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store)
Failed scanning for OVF_STORE due to Command Volume.getInfo with args
{'storagepoolID': '----', 'storagedomainID':
'79376c46-b80c-4c44-bbb1-80c0714a4b52', 'volumeID':
u'687e9c0d-e988-4f76-89ff-931685acdf76', 'imageID':
u'48ee766b-185d-4928-a046-b048d65af2a6'} failed:
(code=201, message=Volume does not exist:
(u'687e9c0d-e988-4f76-89ff-931685acdf76',))
MainThread::ERROR::2019-03-05
16:07:31,916::config_ovf::84::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store)
Unable to identify the OVF_STORE volume, falling back to initial vm.conf.
Please ensure you already added your first data domain for regular VMs
MainThread::INFO::2019-03-05
16:07:31,971::hosted_engine::493::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop)
Current state EngineUnexpectedlyDown (score: 0)
MainThread::ERROR::2019-03-05
16:07:42,304::config_ovf::42::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store)
Failed scanning for OVF_STORE due to Command Volume.getInfo with args
{'storagepoolID': '----', 'storagedomainID':
'79376c46-b80c-4c44-bbb1-80c0714a4b52', 'volumeID':
u'687e9c0d-e988-4f76-89ff-931685acdf76', 'imageID':
u'48ee766b-185d-4928-a046-b048d65af2a6'} failed:
(code=201, message=Volume does not exist:
(u'687e9c0d-e988-4f76-89ff-931685acdf76',))
MainThread::ERROR::2019-03-05
16:07:42,305::config_ovf::84::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store)
Unable to identify the OVF_STORE volume, falling back to initial vm.conf.
Please ensure you already added your first data domain for regular VMs
MainThread::INFO::2019-03-05
16:07:42,365::hosted_engine::493::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop)
Current state EngineUnexpectedlyDown (score: 0)
MainThread::ERROR::2019-03-05
16:07:51,791::config_ovf::42::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store)
Failed scanning for OVF_STORE due to Command Volume.getInfo with args
{'storagepoolID': '----', 'storagedomainID':
'79376c46-b80c-4c44-bbb1-80c0714a4b52', 'volumeID':
u'687e9c0d-e988-4f76-89ff-931685acdf76', 'imageID':
u'48ee766b-185d-4928-a046-b048d65af2a6'} failed:
(code=201, message=Volume does not exist:
(u'687e9c0d-e988-4f76-89ff-931685acdf76',))
MainThread::ERROR::2019-03-05
16:07:51,792::config_ovf::84::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store)
Unable to identify the OVF_STORE volume, falling back to initial vm.conf.
Please ensure you already added your first data domain for regular VMs
MainThread::INFO::2019-03-05
16:07:51,850::hosted_engine::493::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop)
Current state EngineUnexpectedlyDown (score: 0)
MainThread::INFO::2019-03-05
16:08:01,868::states::684::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume)
Engine down, local host does not have best score
MainThread::ERROR::2019-03-05
16:08:02,196::config_ovf::42::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store)
Failed scanning for OVF_STORE due to Command Volume.getInfo with args
{'storagepoolID': '----', 'storagedomainID':
'79376c46-b80c-4c44-bbb1-80c0714a4b52', 'volumeID':
u'687e9c0d-e988-4f76-89ff-931685acdf76', 'imageID':
[ovirt-users] move 'ovirtmgmt' bridge to a bonded NIC team
We've recently added additional NICs to our oVirt nodes, and want to move the ovirtmgmt interface to one of the bonded interfaces, away from the single ethernet port currently used. This is to provide redundant connectivity to the nodes. I've not had any luck finding documentation on how to do this. If we change it manually by editing files in /etc/sysconfig/network-scripts, VDSM simply changes everything back. I'm just looking to be pointed in the right direction here. Thanks! ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/SIWBA35BTSOZFTHZR4Z3HCCEWYXXLL44/
[ovirt-users] Re: The user admin@internal is not authorized to perform login
Thanks! That fixed it (I just added the Admin user back to SuperUser group via the web interface with an LDAP account that had SuperUser). From: Ravi Shankar Nori Sent: November 26, 2018 12:14 PM To: Greg Sheremeta Cc: Shawn Southern ; users@oVirt.org Subject: Re: [ovirt-users] The user admin@internal is not authorized to perform login Looks like the permissions for admin@internal were removed by another admin user You can try the following 1. Get the admin user external id select external_id from users where name = 'admin' and domain = 'internal-authz' 2. Add permissions for admin user select attach_user_to_role( 'admin', 'internal-authz', '*', 'b71c937c-441b-42cc-bf21-33fa2d9704ce', <=== the external id from above 'SuperUser' ) Let us know if it helps On Sat, Nov 24, 2018 at 9:22 AM Greg Sheremeta mailto:gsher...@redhat.com>> wrote: Perhaps Ravi can assist with this. -- Forwarded message ----- From: Shawn Southern mailto:shawn.south...@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@ovirt.org<mailto:users@ovirt.org> mailto:users@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. 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@ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-le...@ovirt.org<mailto:users-le...@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/OQNDRRXT3EZGGKGMBDIRZRLJYC2546N4/ -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gsher...@redhat.com<mailto:gsher...@redhat.com>IRC: gshereme [Image removed by sender.]<https://red.ht/sig> ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/LZ3UXATM5HY66G6ZWIROJNO2IWUSJWKD/
[ovirt-users] The user admin@internal is not authorized to perform login
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. 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@ovirt.org To unsubscribe send an email to users-le...@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/OQNDRRXT3EZGGKGMBDIRZRLJYC2546N4/
[ovirt-users] Re: Custom Intel AMT fencing question
Thank you! For reference, all I had to do was, on the oVirt hosted engine, run: # yum install -y fence-agents-amt-ws # engine-config -s CustomVdsFenceType="amt_ws" # engine-config -s CustomVdsFenceOptionMapping="amt_ws:port=ipport" # engine-config -s CustomFencePowerWaitParam="amt_ws=power_wait" original message From: Eli Mesika <emes...@redhat.com> Sent: May 16, 2018 4:25 AM To: Shawn Southern <shawn.south...@entegrus.com> Cc: Martin Perina <mper...@redhat.com>; users <users@ovirt.org> Subject: Re: [ovirt-users] Custom Intel AMT fencing question On Tue, May 15, 2018 at 6:50 PM, Shawn Southern <mailto:shawn.south...@entegrus.com> wrote: Thanks for this! I’ve got fence_amt_ws working fine, however the document you linked mentions creating a script, and I’m not sure how I’m to pass the various parameters (host to fence, etc.) to this script. From the doc, I'm looking at: It's not creating , rather using the engine-config tool to set a custom fence agent engine-config -s CustomVdsFenceType="amt" engine-config -s CustomVdsFenceOptionMapping="amt:port=ipport" engine-config -s CustomFencePowerWaitParam="amt=power_wait" Will this pass a parameter called ipport that has the IP address or hostname of the host to fence to my script (which in this case is /usr/sbin/fence_amt)? Should work after restarting the agent , if not , please attach the engine.log - original message ----- From: Martin Perina <mailto:mper...@redhat.com> Sent: May 15, 2018 4:20 AM To: Shawn Southern <mailto:shawn.south...@entegrus.com>; Eli Mesika <mailto:emes...@redhat.com> Cc: users <mailto:users@ovirt.org> Subject: Re: [ovirt-users] Custom Intel AMT fencing question On Mon, May 14, 2018 at 8:13 PM, Shawn Southern <mailto:mailto:shawn.south...@entegrus.com> wrote: I'm now using Intel AMT and the wsmancli package to reboot/power off/power on my entry level systems... but now I want oVirt to use this for fencing. I created 3 xml files: powercycle.xml (uses PowerState 10), poweron.xml (uses PowerState 2) and poweroff.xml (uses PowerState 8). Here is the poweroff.xml file: http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService;> 8 http://schemas.xmlsoap.org/ws/2004/08/addressing; xmlns:wsman="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd;> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ComputerSystem CIM_ComputerSystem ManagedSystem I can then reboot or power on/off the server with: wsman invoke -a RequestPowerStateChange http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService -h [AMT IP] -P 16992 -u admin -p [amt password] -J /fencing/poweron.xml (or poweroff.xml, etc). My question is, how do I move from this to using this for fencing in oVirt? At the moment oVirt doesn't officially support AMT as fence agent. But I've just looked that on CentOS 7 we already have fence-agents-amt-ws package, so please try to install fence-agents-amt-ws package and test if it's working for your server. If above agent is working fine, then please take a look Custom Fencing oVirt feature [1], which should allow you to use fence_agent_amt_ws agent in oVirt. Am I right Eli? Regards Martin [1] https://www.ovirt.org/develop/developer-guide/engine/custom-fencing/ Thanks! ___ Users mailing list -- mailto:mailto:users@ovirt.org To unsubscribe send an email to mailto:mailto:users-le...@ovirt.org -- Martin Perina Associate Manager, Software Engineering Red Hat Czech s.r.o. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org
[ovirt-users] Re: Custom Intel AMT fencing question
Thanks for this! I’ve got fence_amt_ws working fine, however the document you linked mentions creating a script, and I’m not sure how I’m to pass the various parameters (host to fence, etc.) to this script. From the doc, I'm looking at: engine-config -s CustomVdsFenceType="amt" engine-config -s CustomVdsFenceOptionMapping="amt:port=ipport" engine-config -s CustomFencePowerWaitParam="amt=power_wait" Will this pass a parameter called ipport that has the IP address or hostname of the host to fence to my script (which in this case is /usr/sbin/fence_amt)? - original message - From: Martin Perina <mper...@redhat.com> Sent: May 15, 2018 4:20 AM To: Shawn Southern <shawn.south...@entegrus.com>; Eli Mesika <emes...@redhat.com> Cc: users <users@ovirt.org> Subject: Re: [ovirt-users] Custom Intel AMT fencing question On Mon, May 14, 2018 at 8:13 PM, Shawn Southern <mailto:shawn.south...@entegrus.com> wrote: I'm now using Intel AMT and the wsmancli package to reboot/power off/power on my entry level systems... but now I want oVirt to use this for fencing. I created 3 xml files: powercycle.xml (uses PowerState 10), poweron.xml (uses PowerState 2) and poweroff.xml (uses PowerState 8). Here is the poweroff.xml file: http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService;> 8 http://schemas.xmlsoap.org/ws/2004/08/addressing; xmlns:wsman="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd;> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ComputerSystem CIM_ComputerSystem ManagedSystem I can then reboot or power on/off the server with: wsman invoke -a RequestPowerStateChange http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService -h [AMT IP] -P 16992 -u admin -p [amt password] -J /fencing/poweron.xml (or poweroff.xml, etc). My question is, how do I move from this to using this for fencing in oVirt? At the moment oVirt doesn't officially support AMT as fence agent. But I've just looked that on CentOS 7 we already have fence-agents-amt-ws package, so please try to install fence-agents-amt-ws package and test if it's working for your server. If above agent is working fine, then please take a look Custom Fencing oVirt feature [1], which should allow you to use fence_agent_amt_ws agent in oVirt. Am I right Eli? Regards Martin [1] https://www.ovirt.org/develop/developer-guide/engine/custom-fencing/ Thanks! ___ Users mailing list -- mailto:users@ovirt.org To unsubscribe send an email to mailto:users-le...@ovirt.org -- Martin Perina Associate Manager, Software Engineering Red Hat Czech s.r.o. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org
[ovirt-users] Custom Intel AMT fencing question
I'm now using Intel AMT and the wsmancli package to reboot/power off/power on my entry level systems... but now I want oVirt to use this for fencing. I created 3 xml files: powercycle.xml (uses PowerState 10), poweron.xml (uses PowerState 2) and poweroff.xml (uses PowerState 8). Here is the poweroff.xml file: http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService;> 8 http://schemas.xmlsoap.org/ws/2004/08/addressing; xmlns:wsman="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd;> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ComputerSystem CIM_ComputerSystem ManagedSystem I can then reboot or power on/off the server with: wsman invoke -a RequestPowerStateChange http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService -h [AMT IP] -P 16992 -u admin -p [amt password] -J /fencing/poweron.xml (or poweroff.xml, etc). My question is, how do I move from this to using this for fencing in oVirt? Thanks! ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org
[ovirt-users] Power management / fencing with Intel AMT
Does anyone have power management with Intel's Management Engine / AMT working with oVirt 4.22? I've found that there is a fence_amt agent, but it's not part of RHEL/CentOS 7. I've not had any luck finding details on how to get fence_amt on my oVirt CentOS 7 hosts. I found this article @ RH, but I don't have access to read it. https://access.redhat.com/solutions/913413 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
