<?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>bwitkowski Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>bwitkowski Tracker</description>
    <pubDate>Wed, 15 Nov 2023 09:58:56 GMT</pubDate>
    <dc:date>2023-11-15T09:58:56Z</dc:date>
    <item>
      <title>Re: Lifecycle Operations Health Information not available</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Lifecycle-Operations-Health-Information-not-available/m-p/2991420#M294</link>
      <description>&lt;P&gt;How would you recommend we consolidate our different deployed environements to a single environment.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Oct 2023 15:04:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Lifecycle-Operations-Health-Information-not-available/m-p/2991420#M294</guid>
      <dc:creator>bwitkowski</dc:creator>
      <dc:date>2023-10-17T15:04:41Z</dc:date>
    </item>
    <item>
      <title>Re: Lifecycle Operations Health Information not available</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Lifecycle-Operations-Health-Information-not-available/m-p/2991240#M289</link>
      <description>&lt;P&gt;I have already done all of this. It still shows information not available&lt;/P&gt;</description>
      <pubDate>Mon, 16 Oct 2023 14:33:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Lifecycle-Operations-Health-Information-not-available/m-p/2991240#M289</guid>
      <dc:creator>bwitkowski</dc:creator>
      <dc:date>2023-10-16T14:33:08Z</dc:date>
    </item>
    <item>
      <title>Lifecycle Operations Health Information not available</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Lifecycle-Operations-Health-Information-not-available/m-p/2990869#M286</link>
      <description>&lt;P&gt;&lt;SPAN&gt;After installing and adding environments in Lifecycle Operations in accordance with the documentation from the official VMware site VMware Aria Automation, and Aria Operations for Logs all show up with a yellow question mark under health, with the message "Information not available"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Each are in their own separate environment,&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am curious as to how to try to resolve this issue&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1) vmware identity manager 3.3.6&lt;BR /&gt;2) vmware aria automation 8.10.1 (prod)&lt;BR /&gt;3) aria operations for logs 8.10.2 (prod)&lt;BR /&gt;4) aria operations 8.12.0 (prod)&lt;BR /&gt;5) vmware aria automation 8.10.1 (test)&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 12 Oct 2023 22:02:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Lifecycle-Operations-Health-Information-not-available/m-p/2990869#M286</guid>
      <dc:creator>bwitkowski</dc:creator>
      <dc:date>2023-10-12T22:02:43Z</dc:date>
    </item>
  </channel>
</rss>

