Bug 2081309 - s2i-base: tzdata is improperly installed
Summary: s2i-base: tzdata is improperly installed
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: tzdata
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Patsy Griffin
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-03 11:39 UTC by Jarek Prokop
Modified: 2023-07-18 14:29 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-04 19:51:03 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-120872 0 None None None 2022-05-03 11:55:33 UTC

Description Jarek Prokop 2022-05-03 11:39:42 UTC
Description of problem:
`tzdata` package is incorrectly installed. `/usr/share/zoneinfo` is not available even though the package is present on the system.

Version-Release number of selected component (if applicable):
image URL: quay.io/sclorg/s2i-base-c9s:c9s ; image ID: a9514389b4df ; CREATED: 8 hours ago

package: tzdata-2022a-1.el9.noarch

How reproducible:
always

Steps to Reproduce:
1. $ ls /usr/share/zoneinfo

Actual results:
`ls: cannot access '/usr/share/zoneinfo': No such file or directory`

Expected results:
The directory has content in it.

Additional info:
Reinstalling the package fixes the problem.

Full log with comparison: https://gist.github.com/pvalena/6dd18aa6f5476b491ca14e5fb2375934

Comment 1 Jarek Prokop 2022-05-03 11:41:23 UTC
The issue's effect is visible here: https://github.com/sclorg/s2i-ruby-container/pull/377#issuecomment-1091954785

Comment 2 Petr Hracek 2022-05-03 12:05:26 UTC
I guess this is not related to the s2i-base-container component but tzdata. Moving to tzdata.

Comment 3 Pavel Valena 2022-05-04 16:40:48 UTC
Please note that this should not be a packaging issue AFAIK, as a simple package reinstall solves it, as jprokop has pointed out in the PR. 

So maybe the base image simply needs to be rebuilt (some layer)? Or there might be some issue with the installation process - it could even be removed explicitly to save space? 

https://gist.github.com/pvalena/770d114f8467a6b06c13bfa00df04b0e


Note You need to log in before you can comment on or make changes to this bug.