Cannot download PAN-OS version due to bissexstile year. Value error: day is out of range for month

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Cannot download PAN-OS version due to bissexstile year. Value error: day is out of range for month

L4 Transporter

Hi All,

 

today one of our customer has tried to download and install PAN-OS version 6.1.10.

Customer has currently installed version 6.1.4.

This error appears:

 

screenshot.77.jpg

 

Error transcript:

-------------------------------------------------------------------------------------------------

Successfully downloaded

Preloading into software manager

Traceback (most recent call last):

File "/usr/local/bin/swm", line 10, in ?

swmmain.main(sys.argv[1:])

File "/usr/share/pan-swm/swmmain.py", line 94, in main

UI.runCommand(H)

File "/usr/share/pan-swm/swmcli.py", line 172, in runCommand

cmd(self.extcmds)

File "/usr/share/pan-swm/swmcli.py", line 317, in do_load

swm.swmRepository(self).load(args, not self.options['nocrypt'])

File "/usr/lib/python2.4/site-packages/swm/repo.py", line 321, in load

self.ensure_freespace(image_file)

File "/usr/lib/python2.4/site-packages/swm/repo.py", line 270, in ensure_freespace

for img in self.redundant_bases():

File "/usr/lib/python2.4/site-packages/swm/repo.py", line 190, in redundant_bases

images = self.imglist()

File "/usr/lib/python2.4/site-packages/swm/repo.py", line 136, in imglist

addimg(dir)

File "/usr/lib/python2.4/site-packages/swm/repo.py", line 114, in addimg

img = swm.imgDescriptor(dir)

File "/usr/lib/python2.4/site-packages/swm/image.py", line 46, in __init__

self.release_info['installed'] = datetime.datetime(*ct[0:6])

ValueError: day is out of range for month

Failed to load into software manager. Please retry.

Post processing failed. Please retry.

-------------------------------------------------------------------------------------------------

 

Same error via CLI.

Seems it's a bug from every version.

We have tried to download on our side and we have currently installed the latest PAN-OS version 7.0.5-h2.

 

Do you think guys this a problem related to bissexstile year?

Best Regards

Luca

2 accepted solutions

Accepted Solutions

Hi Guys,

 

Looks like an issue with the current date, 29th February. Try changing the time to the 1st March or 28th Feb and give it a go, it will resolve the issue.

 

regards,

Ben

View solution in original post

Support now confirms that this is a software bug and PA are working on a fix to be relased in a future version. The bug affects both PA firewalls and Panorama.

 

View solution in original post

8 REPLIES 8

L2 Linker

We have the same problem. Both PA-5050 and Panorama. Old software versions are also gone, or rather not listed as downloaded. I have opened a case with support.

Hi Guys,

 

Looks like an issue with the current date, 29th February. Try changing the time to the 1st March or 28th Feb and give it a go, it will resolve the issue.

 

regards,

Ben

Support now confirms that this is a software bug and PA are working on a fix to be relased in a future version. The bug affects both PA firewalls and Panorama.

 

L4 Transporter

Hi All,

 

Thanks a lot both for your quick response @LCMember1959 , @bmorris1 .

I hope this bug will fixed in the next release,

 

Best Regards

Luca

Y2K was a miss but not Y229.  Glad it will be fixed for the next Leap Year.

@TheRealDiz I'm thinking that Palo will be able to get this fixed in a 4 year window that exists before this can be seen again.

L7 Applicator

Palo Alto Networks is aware of this issue, please see the note at the top of this screen, or this link:

https://live.paloaltonetworks.com/t5/General-Topics/Palo-Alto-Networks-recommends-deferring-upgrades...

 

At this time, the issue seems to be exclusively affecting devices that currently have the date 02/29 as the device datestamp and this issue will resolve as the date changes on the affected device. This has been tested by manually changing the date on our lab devices.

 

However, changing the date manually and removing NTP sync will affect the chronological order of logs and we will lose continuity in viewing the logs for the entirety of the period that the device displays a different time.

 

The other way to avoid running into the aforementioned issues is to wait until the date stamp changes to 03/01 until a content or a software upgrade is attempted.

LIVEcommunity team member
Stay Secure,
Joe
Don't forget to Like items if a post is helpful to you!

Yeap,

 

Sure! I'm agree with you! 🙂

  • 2 accepted solutions
  • 5452 Views
  • 8 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!