Bug 1233815
Summary: | Extract running process doesn't work without error message | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Christian Jung <cbolz> |
Component: | Appliance | Assignee: | Nick Carboni <ncarboni> |
Status: | CLOSED ERRATA | QA Contact: | Jeff Teehan <jteehan> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 5.4.0 | CC: | abellott, cbolz, cpelland, dclarizi, gblomqui, jhardy, mkanoor, ncarboni, obarenbo, tfitzger |
Target Milestone: | GA | ||
Target Release: | 5.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 5.5.0.1 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-08 13:14:36 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Christian Jung
2015-06-19 13:55:26 UTC
Greg, not sure if who should get this but I am figuring you know so assigning to you. Thx Christian - Can you supply the query you were testing with? The error reported in the description 0x80041017 is WBEM_E_INVALID_QUERY "Query was not syntactically valid." Also when issuing the wmic command try specifying the namespace: --namespace="root\cimv2" The query should be in quotes as well. Testing this will obviously not fix the issue but will help validate that you can successfully connect and return data from the terminal. I googled and found this example, which seems to work fine: # wmic -U 'ad\<user>%<password>' //<ipaddress> "Select * from Win32_Bios" CLASS: Win32_BIOS BiosCharacteristics|BIOSVersion|BuildNumber|Caption|CodeSet|CurrentLanguage|Description|IdentificationCode|InstallableLanguages|InstallDate|LanguageEdition|ListOfLanguages|Manufacturer|Name|OtherTargetOS|PrimaryBIOS|ReleaseDate|SerialNumber|SMBIOSBIOSVersion|SMBIOSMajorVersion|SMBIOSMinorVersion|SMBIOSPresent|SoftwareElementID|SoftwareElementState|Status|TargetOperatingSystem|Version (3,42,48,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79)|(BOCHS - 1)|(null)|Default System BIOS|(null)|(null)|Default System BIOS|(null)|0|(null)|(null)|NULL|Seabios|Default System BIOS|(null)|True|20070101000000.000000+000|9F393900-350D-11E1-9CF2-C03FD560822E|0.5.1|2|4|True|Default System BIOS|3|OK|0|BOCHS - 1 This was executed on the appliance from which I want to extract the running processes. New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/4ca5443b2a048df4e67efbc54d8816a3ee2861a3 commit 4ca5443b2a048df4e67efbc54d8816a3ee2861a3 Author: Nick Carboni <ncarboni> AuthorDate: Mon Jul 20 11:37:20 2015 -0400 Commit: Nick Carboni <ncarboni> CommitDate: Mon Jul 20 11:37:20 2015 -0400 Use AwesomeSpawn to fork the wmic process with the password as an argument. The wmic process did not seem to be listening on stdin for the password, so we now pass the credentials as command line arguments through AwesomeSpawn. https://bugzilla.redhat.com/show_bug.cgi?id=1233815 gems/pending/util/win32/miq-wmi-linux.rb | 18 +++++------------- 1 file changed, 5 insertions(+), 13 deletions(-) Detected commit referencing this ticket while ticket status is POST. Detected commit referencing this ticket while ticket status is POST. Added upstream kickstart package line after building the el7 rpm. New commit detected on ManageIQ/manageiq-appliance-build/master: https://github.com/ManageIQ/manageiq-appliance-build/commit/6fff7bb97b9349f3f645e4d4b8cc2760fa06e477 commit 6fff7bb97b9349f3f645e4d4b8cc2760fa06e477 Author: Nick Carboni <ncarboni> AuthorDate: Mon Jul 20 16:57:47 2015 -0400 Commit: Nick Carboni <ncarboni> CommitDate: Thu Aug 27 10:51:32 2015 -0400 Install wmi on appliance build. The wmic tool is needed to get running processes from windows machines. https://bugzilla.redhat.com/show_bug.cgi?id=1233815 kickstarts/base.ks.erb | 2 ++ 1 file changed, 2 insertions(+) New commit detected on ManageIQ/manageiq-appliance-build/master: https://github.com/ManageIQ/manageiq-appliance-build/commit/52bf1333deb360fd402d790adec1b5d8152d1f95 commit 52bf1333deb360fd402d790adec1b5d8152d1f95 Author: Nick Carboni <ncarboni> AuthorDate: Thu Aug 27 10:54:09 2015 -0400 Commit: Nick Carboni <ncarboni> CommitDate: Thu Aug 27 10:54:09 2015 -0400 Add wmi to packages section of kickstart https://bugzilla.redhat.com/show_bug.cgi?id=1233815 kickstarts/base.ks.erb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) The is verified IF: The Windows VM firewall is either disabled or the appropriate ports are open. The account used is "Administrator". All of these settings have been checked: https://social.technet.microsoft.com/Forums/windowsserver/en-US/4f33837b-1cb1-4648-85b1-3ba87cbfe93e/wmi-remote-access-denied?forum=winserverManagement You will get the following output: [root@10-16-6-43 ~]# wmic -U 'Administrator' //10.16.7.124 "Select * from Win32_Bios" Password for [WORKGROUP\Administrator]: CLASS: Win32_BIOS BiosCharacteristics|BIOSVersion|BuildNumber|Caption|CodeSet|CurrentLanguage|Description|IdentificationCode|InstallableLanguages|InstallDate|LanguageEdition|ListOfLanguages|Manufacturer|Name|OtherTargetOS|PrimaryBIOS|ReleaseDate|SerialNumber|SMBIOSBIOSVersion|SMBIOSMajorVersion|SMBIOSMinorVersion|SMBIOSPresent|SoftwareElementID|SoftwareElementState|Status|TargetOperatingSystem|Version (4,7,9,11,12,14,15,16,17,19,22,23,24,25,26,27,28,29,30,34,36,37,40)|(VRTUAL - 5001223,BIOS Date: 05/23/12 17:15:53 Ver: 09.00.06,BIOS Date: 05/23/12 17:15:53 Ver: 09.00.06)|(null)|BIOS Date: 05/23/12 17:15:53 Ver: 09.00.06|(null)|enUS|BIOS Date: 05/23/12 17:15:53 Ver: 09.00.06|(null)|1|(null)|(null)|(enUS)|American Megatrends Inc.|BIOS Date: 05/23/12 17:15:53 Ver: 09.00.06|(null)|True|20120523000000.000000+000|3121-6152-0103-6474-5905-8349-90|090006 |2|3|True|BIOS Date: 05/23/12 17:15:53 Ver: 09.00.06|3|OK|0|VRTUAL - 5001223 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:2551 |