https://dominik.wombacher.cc/2022-03-29T00:00:00+02:002022-03-29T00:00:00+02:002022-03-29T00:00:00+02:00Dominik Wombachertag:dominik.wombacher.cc,2022-03-29:/posts/vcloud_usage_meter_45_upgrade_error_908_command_line_option_is_invalid_skipdigest.html

<!-- SPDX-FileCopyrightText: 2023 Dominik Wombacher <dominik@wombacher.cc> --> <!-- --> <!-- SPDX-License-Identifier: CC-BY-SA-4.0 --> <p>Again a interesting bug, this time during the In-Place Upgrade of a VMWare vCloud Usage Meter from Version 4.4 to 4.5, which shouldn't be a big deal based ... <a class="read-more" href="/posts/vcloud_usage_meter_45_upgrade_error_908_command_line_option_is_invalid_skipdigest.html"> [read more]</a></p>

<!-- SPDX-FileCopyrightText: 2023 Dominik Wombacher <dominik@wombacher.cc> --> <!-- --> <!-- SPDX-License-Identifier: CC-BY-SA-4.0 --> <p>Again a interesting bug, this time during the In-Place Upgrade of a VMWare vCloud Usage Meter from Version 4.4 to 4.5, which shouldn't be a big deal based on the <a class="reference external" href="https://docs.vmware.com/en/vCloud-Usage-Meter/4.5/Getting-Started-vCloud-Usage-Meter/GUID-AE5A81E1-097A-4EED-9A8E-8BF7E0B378A4.html">official Upgrade Guide</a> (Archive: <a class="reference external" href="https://web.archive.org/web/20220329202039/https://docs.vmware.com/en/vCloud-Usage-Meter/4.5/Getting-Started-vCloud-Usage-Meter/GUID-AE5A81E1-097A-4EED-9A8E-8BF7E0B378A4.html">[1]</a>, <a class="reference external" href="https://archive.today/2022.03.29-201847/https://docs.vmware.com/en/vCloud-Usage-Meter/4.5/Getting-Started-vCloud-Usage-Meter/GUID-AE5A81E1-097A-4EED-9A8E-8BF7E0B378A4.html">[2]</a>).</p> <p>Running <code>bash /root/upgrade/upgrade-um.sh</code> ended in:</p> <pre class="code text literal-block"> Error(908) : Command line error: option is invalid. No such option: --skipdigest. Please use /usr/bin/tdnf --help Upgrade fail during JRE update. Please, revert to latest snapshot and prior update execute 'tdnf clean cache'.` </pre> <p>I followed all steps exactly as described in the Guide so how is it possible that the Upgrade Script triggers <code>tdnf</code> with unavailable options? Couldn't find anything related / similar in the VMWare KB, GitHub and a good old Google / DuckDuckGo Search.</p> <p>Based on our internal documentation, we installed the Usage Meter a while back in Version 4.1 and upgraded to 4.4 a year ago, probably there was also a 4.2 and / or 4.3 upgrade before.</p> <p>The result of <code>tdnf --version</code> was a quite outdated version <code>tdnf: 1.2.3</code> which seem to be released around mid of 2017, but option <code>--skipdigest</code> was part of a <a class="reference external" href="https://github.com/vmware/tdnf/commit/7f23f9c2f5b5976d2ccd443ddc2b84e00cba81d0">commit</a> (Archive: <a class="reference external" href="https://web.archive.org/web/20220329202918/https://github.com/vmware/tdnf/commit/7f23f9c2f5b5976d2ccd443ddc2b84e00cba81d0">[1]</a>, <a class="reference external" href="https://archive.today/2022.03.29-202915/https://github.com/vmware/tdnf/commit/7f23f9c2f5b5976d2ccd443ddc2b84e00cba81d0">[2]</a>) on April 12 2019.</p> <p>vCloud Usage Meter is running on VMware Photon OS, <em>just</em> another Linux Distribution with yum as package manager and attached online repositories. So let's just try to update <strong>tdnf</strong> manually via <code>yum update tdnf</code>:</p> <pre class="code text literal-block"> Upgrading: rpm-libs x86_64 4.14.3-1.ph3 photon-updates 937.03k 959523 rpm x86_64 4.14.3-1.ph3 photon-updates 356.38k 364930 hawkey x86_64 2017.1-8.ph3 photon-updates 150.05k 153656 tdnf-cli-libs x86_64 3.1.8-1.ph3 photon-updates 70.18k 71864 tdnf x86_64 3.1.8-1.ph3 photon-updates 309.71k 317139 Total installed size: 1.78M 1867112 Is this ok [y/N]: y </pre> <p>Looks good, installation of version <code>tdnf: 3.1.8</code> was successful, a quick test, which ended earlier in the same <em>Error(908)</em> as above, worked this time, so obviously this version is new enough to know the option <code>--skipdigest</code>:</p> <pre class="code text literal-block"> tdnf update --skipdigest vmware-jre </pre> <p>Afterwards I could just follow the Guide from VMWare to perform the In-Place Upgrade to Version 4.5 without any further issues. I assume something went wrong during earlier Upgrades and <code>tdnf</code> was never updated after the initial Installation. Earlier Upgrade Scripts probably didn't used the <code>--skipdigest</code> option, so it was undetected until now.</p> <p>All this would explain why no one else seem to hit that bug, was probably a rare edge case limited to our Environment.</p>