<?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 Re: Panorama 8.0.2 - Buggy??? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/panorama-8-0-2-buggy/m-p/288450#M76840</link>
    <description>I would not run any release that does not end in at ".7" or higher in production. Support told me ".6"</description>
    <pubDate>Sat, 14 Sep 2019 00:36:57 GMT</pubDate>
    <dc:creator>Gregory_Korten</dc:creator>
    <dc:date>2019-09-14T00:36:57Z</dc:date>
    <item>
      <title>Panorama 8.0.2 - Buggy???</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/panorama-8-0-2-buggy/m-p/158062#M51762</link>
      <description>&lt;P&gt;We have multiple models of FW hardware running primarliy 7.1.9 and it seems like since upgrading to Panorama 8.0.2 from Panorama 7.1.9 that it is almost painful to make changes. It seems everytime we push to devices something fails. Today specifically we push some changes and it says "failed" look in the log and it says synchonization failed but then you go to the firewalls and they are pefectly synced and all of the changes are there. From my tracking so far it seems like most of the issues come when pushing template changes along with device group changes it is like crash bang boom &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; We would roll back however we converted to Panorama mode from Legacy (lost nearly 1TB of logs) and have new 220's and 800's that require the 8.X code so with pretty much have to suffer.&lt;/P&gt;&lt;P&gt;We have always had very good luck with Panorama upgrades but so far with 8.X is seems like they could have used more BETA testing or something. Anyone else frustrated?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Oh I almost forgot the whole config locks thing. Not sure if is by design or a bug but if you commit all changes then config locks automatically release like they are supposed to. If you commit only your changes then the lock stays on and you have to manually unlock it after you are done. Not really sure what the thought process is there???&lt;/P&gt;</description>
      <pubDate>Wed, 24 May 2017 13:48:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/panorama-8-0-2-buggy/m-p/158062#M51762</guid>
      <dc:creator>Wald</dc:creator>
      <dc:date>2017-05-24T13:48:21Z</dc:date>
    </item>
    <item>
      <title>Re: Panorama 8.0.2 - Buggy???</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/panorama-8-0-2-buggy/m-p/288450#M76840</link>
      <description>I would not run any release that does not end in at ".7" or higher in production. Support told me ".6"</description>
      <pubDate>Sat, 14 Sep 2019 00:36:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/panorama-8-0-2-buggy/m-p/288450#M76840</guid>
      <dc:creator>Gregory_Korten</dc:creator>
      <dc:date>2019-09-14T00:36:57Z</dc:date>
    </item>
  </channel>
</rss>

