<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic ovftool 4.2.0 has a broken --allowAllExtraConfig in Open Virtualization Format Tool Discussions</title>
    <link>https://communities.vmware.com/t5/Open-Virtualization-Format-Tool/ovftool-4-2-0-has-a-broken-allowAllExtraConfig/m-p/1779851#M1017</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;4.2.0 is bundled into the current build of Fusion10:&lt;/P&gt;&lt;P&gt;ovftool --version&lt;/P&gt;&lt;P&gt;VMware ovftool 4.2.0 (build-6230482)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This version has a busted --allowAllExtraConfig flag, so some VMs will not export to OVA, instead you get a slew of errors like this one:&lt;/P&gt;&lt;P&gt; - Line -1: Unsupported value 'disk.EnableUUID' for attribute 'key' on element 'ExtraConfig'.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 18 Nov 2017 07:36:30 GMT</pubDate>
    <dc:creator>lusid2</dc:creator>
    <dc:date>2017-11-18T07:36:30Z</dc:date>
    <item>
      <title>ovftool 4.2.0 has a broken --allowAllExtraConfig</title>
      <link>https://communities.vmware.com/t5/Open-Virtualization-Format-Tool/ovftool-4-2-0-has-a-broken-allowAllExtraConfig/m-p/1779851#M1017</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;4.2.0 is bundled into the current build of Fusion10:&lt;/P&gt;&lt;P&gt;ovftool --version&lt;/P&gt;&lt;P&gt;VMware ovftool 4.2.0 (build-6230482)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This version has a busted --allowAllExtraConfig flag, so some VMs will not export to OVA, instead you get a slew of errors like this one:&lt;/P&gt;&lt;P&gt; - Line -1: Unsupported value 'disk.EnableUUID' for attribute 'key' on element 'ExtraConfig'.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 18 Nov 2017 07:36:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Open-Virtualization-Format-Tool/ovftool-4-2-0-has-a-broken-allowAllExtraConfig/m-p/1779851#M1017</guid>
      <dc:creator>lusid2</dc:creator>
      <dc:date>2017-11-18T07:36:30Z</dc:date>
    </item>
    <item>
      <title>Re: ovftool 4.2.0 has a broken --allowAllExtraConfig</title>
      <link>https://communities.vmware.com/t5/Open-Virtualization-Format-Tool/ovftool-4-2-0-has-a-broken-allowAllExtraConfig/m-p/1779852#M1018</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So it appears this broke a year ago, and I'm just noticing it now because it finally rolled into Fusion/Workstation.&amp;nbsp; Reverting to pre-ovftool 4.x variants of my scripts fixes ovf export, so rather than alias the deprecated --allowAllExtraConfig flag back to the surviving --allowExtraConfig flag, they elected to just break it.&amp;nbsp;&amp;nbsp; So for the next guy to trip over this one; include both flags and it works on 4.1 and 4.2.&amp;nbsp; Each version seems to ignore the flag it considers extraneous.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV class="grammarly-disable-indicator"&gt; &lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 18 Nov 2017 20:27:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Open-Virtualization-Format-Tool/ovftool-4-2-0-has-a-broken-allowAllExtraConfig/m-p/1779852#M1018</guid>
      <dc:creator>lusid2</dc:creator>
      <dc:date>2017-11-18T20:27:20Z</dc:date>
    </item>
    <item>
      <title>Re: ovftool 4.2.0 has a broken --allowAllExtraConfig</title>
      <link>https://communities.vmware.com/t5/Open-Virtualization-Format-Tool/ovftool-4-2-0-has-a-broken-allowAllExtraConfig/m-p/1779853#M1019</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="http://pubs.vmware.com/Release_Notes/en/developer/ovf/65/vmware-ovftool-420-release-notes.html" title="http://pubs.vmware.com/Release_Notes/en/developer/ovf/65/vmware-ovftool-420-release-notes.html"&gt;OVF Tool 4.2.0 Release Notes&lt;/A&gt; says,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;H2 style="font-family: Arial; margin-bottom: 18px; color: #387c2c;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;Known Issues in This Version&lt;/SPAN&gt;&lt;/H2&gt;&lt;BLOCKQUOTE&gt;&lt;P style="color: #000000; font-family: Arial;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;The &lt;TT&gt;ovftool&lt;/TT&gt; option &lt;TT&gt;--allowAllExtraConfig&lt;/TT&gt; is no longer supported. The command-line option &lt;TT&gt;--allowAllExtraConfig&lt;/TT&gt; never worked as designed. As of release 6.5 U1, vSphere no longer supports this option. The workaround is to use &lt;TT&gt;--allowExtraConfig&lt;/TT&gt; instead to import additional configurations.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;...&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 06 Jan 2018 05:52:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Open-Virtualization-Format-Tool/ovftool-4-2-0-has-a-broken-allowAllExtraConfig/m-p/1779853#M1019</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2018-01-06T05:52:14Z</dc:date>
    </item>
  </channel>
</rss>

