-
Bug
-
Resolution: Fixed
-
Medium
-
Discovery 3.1.0, Discovery 3.1.1
-
None
-
2
-
Severity 3 - Minor
-
16
-
Issue Summary
Using Discovery 3.1.x when running Linux_Hostinfo_UUID.pat, UUID does not appear on the Scan results
This is reproducible on Data Center: (yes)
Steps to Reproduce
Unable to reproduce the issue but the steps would be as follows:
- Configure Discovery to scan a Red Hat 7 host
- Scan the Red Hat 7 host
- On the Scan logs, the command returns the right UUID
- XML Scan result is not included
Expected Results
UUID value should be included in the Scan results
Actual Results
There are line break \n in UUID string that is not expected in the pattern. We enabled some debugging as we observe below
7/14/2022 3:14:12 AM : Using pattern: Linux_Hostinfo_UUID_debug_v2-1.pat (v3.4.0)
7/14/2022 3:14:15 AM : Creating a shell stream.
7/14/2022 3:14:17 AM : Terminal raw result:
]0;xxxx@ctest:~[xxxx@ctest ~]$ sudo dmidecode -t system | grep 'UUID'
| col -b
UUID: 20014d56-cd29-ac5f-f7b5-e1d728846d93
]0;xxxx@ctest:~[xxxx@ctest ~]$
7/14/2022 3:14:18 AM : Linux HostInfo UUID Perform action started...
7/14/2022 3:14:18 AM : HostInfo.UUID:
7/14/2022 3:14:18 AM :
7/14/2022 3:14:18 AM : Command:
sudo dmidecode -t system | grep 'UUID'
7/14/2022 3:14:18 AM : Result:
UUID: 20014d56-cd29-ac5f-f7b5-e1d728846d93
7/14/2022 3:14:18 AM : CommandResult:
7/14/2022 3:14:18 AM :
UUID: 20014d56-cd29-ac5f-f7b5-e1d728846d93
7/14/2022 3:14:18 AM : firstline:
7/14/2022 3:14:18 AM :
7/14/2022 3:14:18 AM : HostInfo.UUID:
7/14/2022 3:14:18 AM :
7/14/2022 3:14:18 AM : pattern executed in 5.5098006 seconds
Workaround
Use the Linux_Hostinfo_UUID.pat
attached