zdog59
Enthusiast
Enthusiast

Guest Operations - Copy file from Guest to vCO - Format Issue

All,

Noticed that when copying log /txt files from the guest back to the vCO server using the Guest Operations, the files lose there formatting. (ie carriage returns/line breaks)  The log files are created on a Win2k8 server (guest) and being copied back to local dir on vCO (Win2k8 server).  When the files are opened on the guest, they have the proper format.  If they are copied via windows they have correct format.   It is when pulling back through vCO and guest ops api the formatting is changed.

Anyone know how to resolve this issue?

Thanks,

Mike

0 Kudos
7 Replies
Burke-
VMware Employee
VMware Employee

This is a known bug that has been fixed in vCenter plug-in version 5.1.1-521 and newer. I'm unsure if this has made it into a released build yet.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vRealize Orchestrator tips and tutorials - @TechnicalValues on Twitter
zdog59
Enthusiast
Enthusiast

Thank you Burke!

I wish I had posted a week earlier and not wasted the 30ish hours researching. lol.

Quick question, is the new vCenter plugin 5.1.1-521 available and backwards compatible?

0 Kudos
iiliev
VMware Employee
VMware Employee

I think the latest released vCO 5.1.x build includes VC plug-in 5.1.1-509. Not 100% sure; have to double check.

Burke, do you remember the bug number (to check when/where it was fixed)? I think build 5.1.1-521 was about a different issue.

0 Kudos
Burke-
VMware Employee
VMware Employee

Yes, bug id is: 1007880

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vRealize Orchestrator tips and tutorials - @TechnicalValues on Twitter
0 Kudos
iiliev
VMware Employee
VMware Employee

OK, mystery solved...

The bug 1007880 has been fixed on Mar 27th. VC plug-in build 5.1.1-521 is dated May 16th, so it includes not only this particular bugfix, but also other fixes after the latest release. Several older builds before 521 also include the bugfix. Unfortunately, the latest released build VC plug-in 509 has been compiled before Mar 27th and does not include the fix.

Mike, there are several options for you to get a fixed VC plug-in:

  1. Wait for official 5.1U2 release
  2. We can produce a custom patch of VC plug-in that will include only this bug fix applied on top of the released build you currently have. BTW, which version are you using - 5.1GA, 5.1U1, or something else?
  3. We can send you one of the latest, not yet released builds of VC plug-in, which will include not only this bugfix but also all changes committed after the latest release. A bit riskier that option 2.

If you choose option 2 or 3, could you open a support request so we can track it?

zdog59
Enthusiast
Enthusiast

Thank you,

I think the best option for us will be to go with a custom patch.  I will call in the requests this afternoon.

Thanks for your help, this was reeking havoc with our current process.

Mike

0 Kudos
zdog59
Enthusiast
Enthusiast

Version is VC Plugin : 5.1.0.466

Version vCO: 5.1.0 Build 2725

0 Kudos