#9344 Regenerate the ostree commit for F33 Silverblue
Closed: Fixed 4 years ago by tpopela. Opened 4 years ago by tpopela.

Describe what you would like us to do:


According to https://bugzilla.redhat.com/show_bug.cgi?id=1876194#c16:

# ostree pull --commit-metadata-only fedora:fedora/33/x86_64/silverblue

GPG: Verification enabled, found 1 signature:

  Signature made Mon 21 Sep 2020 04:05:40 AM EDT using RSA key ID 6C13026D12C944D0
  Good signature from "Fedora <fedora-32-primary@fedoraproject.org>"
2 metadata, 0 content objects fetched; 56 KiB transferred in 4 seconds; 0 bytes content written                                                                                                                                                                 

# ostree show fedora:fedora/33/x86_64/silverblue | grep Date:

Date:  2020-09-21 08:05:26 +0000

#

The ostree commit needs to be regenerated.
This will fix the rebases from Silverblue 32 to Silverblue 33.

When do you need this to be done by? (YYYY/MM/DD)


Sooner the better..

@mohanboddu promised to look at it today


Metadata Update from @mohanboddu:
- Issue assigned to mohanboddu
- Issue tagged with: medium-gain, medium-trouble, ops

4 years ago

Looks like the composes finished for today and new commits exist:

$ ostree pull --commit-metadata-only --depth=1 onerepo:fedora/33/x86_64/silverblue


GPG: Verification enabled, found 1 signature:

  Signature made Wed 23 Sep 2020 04:04:14 AM EDT using RSA key ID 6C13026D12C944D0
  Good signature from "Fedora <fedora-32-primary@fedoraproject.org>"


GPG: Verification enabled, found 1 signature:

  Signature made Tue 22 Sep 2020 10:55:18 AM EDT using RSA key ID 6C13026D12C944D0
  Good signature from "Fedora <fedora-32-primary@fedoraproject.org>"
$ ostree log onerepo:fedora/33/x86_64/silverblue
commit 6942fe3f6c881635d61bbe3c6235feba3c998099f309b369ea4ddfe67abcc698
Parent:  ab146059541131554d05c5696f5e2e03ac73a3330cb6e8e564c09c102c631488
ContentChecksum:  898b6d339d66f5aef26cc2b902b23adc22d5a9fae1740dd480f3f6b257a9fea4
Date:  2020-09-23 08:04:00 +0000
Version: 33.20200923.n.0
(no subject)

commit ab146059541131554d05c5696f5e2e03ac73a3330cb6e8e564c09c102c631488
Parent:  98cb4e1c6e1786b48d9228bc33f02f330c0e57ac5194f219f3752b2bcd9f7cd2
ContentChecksum:  ab4eb21b6712a51f28450000c678813ad9562801b8d15c0a1a0cd3a9c8902481
Date:  2020-09-22 14:54:59 +0000
Version: 33_Beta.1.3
(no subject)

<< History beyond this commit not fetched >>

@tpopela Seems like everything is fine and @dustymabe verified it for me. Can you check it again?

Yeah. I verified we have new commits in the OSTree history. Not sure if they have the content you're looking for, though. You'll need to check.

@mohanboddu it indeed works now! I was able to successfully rebase to Silverblue 33.

Metadata Update from @tpopela:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Log in to comment on this ticket.

Metadata
Boards 1
ops Status: Done