Bug 1433851

Summary: tps-srmptest rebuild fails on self.assertEqual(loc_time.strftime('%Z%z'), 'NET+0020')
Product: Red Hat Enterprise Linux 7 Reporter: Vaclav Danek <vdanek>
Component: pytzAssignee: Python Maintainers <python-maint>
Status: CLOSED ERRATA QA Contact: Vaclav Danek <vdanek>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: cstratak, pviktori, vdanek
Target Milestone: rcFlags: vdanek: needinfo-
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pytz-2016.10-2.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 20:30:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vaclav Danek 2017-03-20 07:38:40 UTC
Description of problem:
tps-srmptest rebuild fails on self.assertEqual(loc_time.strftime('%Z%z'), 'NET+0020')


Version-Release number of selected component (if applicable):
pytz-2016.10-1.el7.src.rpm

How reproducible:
Start tps-srpmtest for erratum 26511 

Actual results:
Last 20 lines of Build Log:
        # Actually +00:19:32, but Python datetime rounds this
        self.assertEqual(loc_time.strftime('%Z%z'), 'NST+0120')
    
        loc_time = loc_tz.localize(datetime(1940, 5, 10, 0, 0, 0))
>       self.assertEqual(loc_time.strftime('%Z%z'), 'NET+0020')
E       AssertionError: '+0020+0020' != 'NET+0020'

Additional info:
Probably caused due to abbreviations changes in tzdata.

Comment 2 Charalampos Stratakis 2017-03-20 09:05:20 UTC
Yes it seems so, this is a bug as the tests expect obsolete abbrevations from tzdata.

Reported also here: https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1507666.html

Will dig a bit, but it should be safe to just disable the specific test cases.

Comment 6 errata-xmlrpc 2017-08-01 20:30:53 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1915