Hi,
I'm happy to report that this issue has indeed been corrected (in the august or september version of DSU, I can't remember precisely).
Thanks for the work. Bye. Le 10/05/2017 10:45, [email protected] a écrit :
HiThanks for providing the snippet from inv.xml which was causing the issue.We are looking in to the issue and shall update soon. Regards, Sashi [email protected] -----Original Message-----From: linux-poweredge-bounces-Lists On Behalf Of linux-poweredge-request-ListsSent: Friday, May 5, 2017 10:30 PM To: linux-poweredge-Lists <[email protected]> Subject: Linux-PowerEdge Digest, Vol 156, Issue 2 Send Linux-PowerEdge mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.us.dell.com/mailman/listinfo/linux-poweredge or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Linux-PowerEdge digest..." Today's Topics: 1. Re: Problem with DSU on RHEL 6.8 (Guillaume Courtois) ---------------------------------------------------------------------- Message: 1 Date: Fri, 05 May 2017 14:27:06 +0200 From: Guillaume Courtois <[email protected]> Subject: Re: [Linux-PowerEdge] Problem with DSU on RHEL 6.8 To: [email protected] Cc: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" Hi, Sorry for not giving you news before, but I've tried to ask for permission to send you the inventory files from my company, and was not able to get it. Anyway, I've been digging in the meantime, and it seems that the problem is indeed in the content of the inv.xml file, as testing dsu --input-inventory-file= with a inv.xml file from another server works well. And so I was able to isolate the lines that cause the problem : <Device componentID="101434" display="13G SEP Firmware" enum="Bay ID =0"><Application componentType="FRMW" version="2.23" display="13G SEP Firmware, BayID: 0"/></Device> <Device componentID="101434" display="13G SEP Firmware" enum="Bay ID =2"><Application componentType="FRMW" version="2.23" display="13G SEP Firmware, BayID: 2"/></Device> What is pretty strange is that removing either one or the other (or both) of the lines removes the problem. Also, adding these two lines to a inv.xml file on a server where everything was correctly working before makes the dsu command fail too. I'm currently updating the local repository as I've seen there are new dell-system-update and dsucatalog packages, but I've already installed them locally and it does not seem to correct the problem. Versions on the server where I added the lines (redhat 6.5) : invcol_RPTVF_LN64_17.03.200.987_A00-17.03.00.987-RPTVF.x86_64 dell-system-update-1.4.0-17.02.00.x86_64 dsucatalog-17.03.00-R83X8.noarch Versions on the server where I'm doing my tests, which have always failed before removing the lines (redhat 6.8) : dsucatalog-17.04.00-HF1W6.noarch dell-system-update-1.4.1-17.04.00.x86_64 invcol_RPTVF_LN64_17.03.200.987_A00-17.03.00.987-RPTVF.x86_64 Bye. Le 26/04/2017 09:14, [email protected] a ?crit?:Dell - Internal Use - Confidential Hi, What is the dsu version used? Try running below commands and send us the output: dsu --output-inventory-xml="/root/dsu_inv.xml" dsu --input-inventory-file="/root/dsu_inv.xml" Please attach dsu_inv.xml to analyze this. Thanks, Venu -----Original Message----- From: linux-poweredge-bounces-Lists On Behalf Of Guillaume Courtois Sent: Tuesday, April 25, 2017 4:19 PM To: linux-poweredge-Lists <[email protected]> Subject: [Linux-PowerEdge] Problem with DSU on RHEL 6.8 Hi guys, I'm trying to have DSU working of some Dell Poweredge r730xd servers, but despite trying all manipulations I could find here and there, I stll get the infamous "Could not parse the inventory" message. FYI, I have made a mirror of the Dell repository, and packages are installed from there. Whenever I run dsu -i, the trace of the process tells me that it opens and reads the first block of the inv.xml file, then immediately after that it fails with the error message. The content of the file seems ok to me : <?xml version="1.0" encoding="UTF-16"?> <SVMInventory lang="en" schemaVersion="1.0" invcolVersion="17.03.200 (BLD_987)" invcolBuild="987" timeStamp="2017-04-25T12:39:10"> <OperatingSystem osCode="LIN" osVendor="Redhat" osArch="x64" majorVersion="redhat-release-server-6Server" minorVersion="2.6.32-642.el6.x86_64"/> <System systemID="0627"/><Device componentID="2331" display="OpenManage Server Administrator"> etc ... I have tried removing the binary file, running it on a command line to feed the resulting file to dsu, removing and reinstalling all packages, ... Nothing works and I'm running out of ideas. If you have any new idea on that problem I'm willing to test it ! Thanks and bye.-------------- next part -------------- A non-text attachment was scrubbed... Name: 0x6C853BC3.asc Type: application/pgp-keys Size: 1656 bytes Desc: not available Url : http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20170505/47b7c970/attachment-0001.bin ------------------------------ _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge End of Linux-PowerEdge Digest, Vol 156, Issue 2 *********************************************** _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge
0x6C853BC3.asc
Description: application/pgp-keys
_______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge
