<?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 Palo Alto Networks recommends deferring upgrades until March 1 in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-networks-recommends-deferring-upgrades-until-march-1/m-p/73831#M41548</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Due to an unforeseen issue with an upgrade script, Palo Alto Networks recommends deferring upgrades until March 1. This impacts all versions of PAN-OS. We apologize for the inconvenience.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;Corrective action is being taken to prevent similar issues from occurring in the future.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 29 Feb 2016 18:35:54 GMT</pubDate>
    <dc:creator>Retired Member</dc:creator>
    <dc:date>2016-02-29T18:35:54Z</dc:date>
    <item>
      <title>Palo Alto Networks recommends deferring upgrades until March 1</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-networks-recommends-deferring-upgrades-until-march-1/m-p/73831#M41548</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Due to an unforeseen issue with an upgrade script, Palo Alto Networks recommends deferring upgrades until March 1. This impacts all versions of PAN-OS. We apologize for the inconvenience.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;Corrective action is being taken to prevent similar issues from occurring in the future.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Feb 2016 18:35:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-networks-recommends-deferring-upgrades-until-march-1/m-p/73831#M41548</guid>
      <dc:creator>Retired Member</dc:creator>
      <dc:date>2016-02-29T18:35:54Z</dc:date>
    </item>
    <item>
      <title>Re: Palo Alto Networks recommends deferring upgrades until March 1</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-networks-recommends-deferring-upgrades-until-march-1/m-p/73840#M41551</link>
      <description>&lt;P&gt;I suspect that is due to Feb 29th leap year? &amp;nbsp;My downloads fail with:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;ValueError: day is out of range for month&lt;/LI&gt;
&lt;LI&gt;Failed to load into software manager. Please retry.&lt;/LI&gt;
&lt;LI&gt;Post processing failed. Please retry.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Feb 2016 20:54:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-networks-recommends-deferring-upgrades-until-march-1/m-p/73840#M41551</guid>
      <dc:creator>cenders</dc:creator>
      <dc:date>2016-02-29T20:54:42Z</dc:date>
    </item>
    <item>
      <title>Re: Palo Alto Networks recommends deferring upgrades until March 1</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-networks-recommends-deferring-upgrades-until-march-1/m-p/73885#M41559</link>
      <description>&lt;P&gt;Just to confirm that suspicion - the updates to my test firewall and Panorama went through fine today whereas I was seeing this issue yesterday.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Mar 2016 09:58:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-networks-recommends-deferring-upgrades-until-march-1/m-p/73885#M41559</guid>
      <dc:creator>MikeMeredith</dc:creator>
      <dc:date>2016-03-01T09:58:26Z</dc:date>
    </item>
    <item>
      <title>Re: Palo Alto Networks recommends deferring upgrades until March 1</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-networks-recommends-deferring-upgrades-until-march-1/m-p/73904#M41567</link>
      <description>&lt;P&gt;I found this issue with support. The Issue was introduced when moving form 6.X to 7.0.3 or above. The issue doesnt exist if you do the two steup upgrade and go to 7.0.1 and then upgrade to 7.0.3 or higher. This fix is cinluded in 7.0.6 I am told&lt;/P&gt;</description>
      <pubDate>Tue, 01 Mar 2016 15:09:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-networks-recommends-deferring-upgrades-until-march-1/m-p/73904#M41567</guid>
      <dc:creator>apritchard</dc:creator>
      <dc:date>2016-03-01T15:09:00Z</dc:date>
    </item>
  </channel>
</rss>

