Bug #28965: Regression: Since #19389 boot image of debian is not updated and installation is broken - Foreman

Custom queries

3.11.5 release DONE
3.11.5 release TODO
3.12.2 release DONE
3.12.2 release TODO
3.13.0 release DONE
3.13.0 release TODO
All bugs by votes
All issues closed in the last 3 weeks
Easy and Trivial Issues
Easy Issues (only)
Foreman - new open issues in last 10 days
Good first issues - Foreman core
high prio open bugs
Host registration [open]
Mine
My issues closed in the last 3 weeks
old bugs
Open with target version set (aka blockers)
registration
taken-none
Team Atlas untriaged bugs
templates
Trivial Issues
Untriaged and opened in the past two weeks

Actions

Copy link

Bug #28965

closed

Regression: Since #19389 boot image of debian is not updated and installation is broken

Added by Daniel Kraemer almost 5 years ago. Updated almost 5 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Lukas Zapletal

Category:

TFTP

Target version:

Difficulty:

Triaged:

Bugzilla link:

Pull request:

https://github.com/theforeman/foreman/pull/7432

Fixed in Releases:

2.0.0

Found in Releases:

1.22.1

Red Hat JIRA:

Description

Hi,

since the filenames for bootimage/initrd are containing some hash based on the media, foreman will not download new bootimages when debian is releasing a minor version like today (10.2 -> 10.3).
While the repo is updated in background, the packages, which get downloaded during preseed, doesn't match the image anymore and the installtion fails with an error.

Related issues 3 (1 open — 2 closed)

Related to Foreman - Feature #19389: Change TFTP filename pattern to include unique installation media ID	Closed	Shimon Shtein	Actions
Related to Foreman - Feature #26709: Rethink TFTP naming conventions for PXE files	New		Actions
Related to Foreman - Bug #25733: Media provider unique ID does not work for Debian-based distros	Closed	Lukas Zapletal	Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Daniel Kraemer almost 5 years ago

Related to Feature #19389: Change TFTP filename pattern to include unique installation media ID added

Actions

Copy link

Updated by Daniel Kraemer almost 5 years ago

Related to Feature #26709: Rethink TFTP naming conventions for PXE files added

Actions

Copy link

Updated by Daniel Kraemer almost 5 years ago

Status changed from New to Duplicate
Found in Releases 1.22.1 added
Found in Releases deleted (~~1.22.0~~)

Actions

Copy link

Updated by Daniel Kraemer almost 5 years ago

Actually this looks like a duplicate of https://projects.theforeman.org/issues/25733

but #25733 should already be fixed and we still suffer from this bug

Actions

Copy link

Updated by Tomer Brisker almost 5 years ago

Is duplicate of Bug #25733: Media provider unique ID does not work for Debian-based distros added

Actions

Copy link

Updated by Tomer Brisker almost 5 years ago

Is duplicate of deleted (Bug #25733: Media provider unique ID does not work for Debian-based distros)

Actions

Copy link

Updated by Tomer Brisker almost 5 years ago

Status changed from Duplicate to New

changing back to new since this appears to be related but not quite a duplicate

Actions

Copy link

Updated by Lukas Zapletal almost 5 years ago

Hello, I think it's still a bug. Help me to understand the problem. We currently calculate the unique ID from URL, however when Debian releases new version, the installation URL remains the same, therefore smart proxy has no reason to redownload the files (as we currently do not fetch ETAG/Last-Changed HTTP header). If we calculate the hash from the URL + minor/major version of the OS that would do it when new version is released.

Actions

Copy link