Project

General

Profile

Actions

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
Category:
TFTP
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

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 open2 closed)

Related to Foreman - Feature #19389: Change TFTP filename pattern to include unique installation media IDClosedShimon ShteinActions
Related to Foreman - Feature #26709: Rethink TFTP naming conventions for PXE filesNewActions
Related to Foreman - Bug #25733: Media provider unique ID does not work for Debian-based distrosClosedLukas ZapletalActions
Actions #1

Updated by Daniel Kraemer almost 5 years ago

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

Updated by Daniel Kraemer almost 5 years ago

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

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 #4

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 #5

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 #6

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 #7

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 #8

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 #9

Updated by Lukas Zapletal almost 5 years ago

WORKAROUND: Delete those PXE files and smart proxy will redownload them. PR in a minute.

Actions #10

Updated by The Foreman Bot almost 5 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Lukas Zapletal
  • Pull request https://github.com/theforeman/foreman/pull/7432 added
Actions #11

Updated by Daniel Kraemer almost 5 years ago

Lukas Zapletal wrote:

If we calculate the hash from the URL + minor/major version of the OS that would do it when new version is released.

I guess this should fix it.

Lukas Zapletal wrote:

WORKAROUND: Delete those PXE files and smart proxy will redownload them. PR in a minute.

Yep, we've done that, worked

Actions #12

Updated by Tomer Brisker almost 5 years ago

  • Related to Bug #25733: Media provider unique ID does not work for Debian-based distros added
Actions #13

Updated by The Foreman Bot almost 5 years ago

  • Fixed in Releases 2.0.0 added
Actions #14

Updated by Lukas Zapletal almost 5 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF