releng

#7891 FBR: Fix f29 ostree refs since new-updates-sync overwrote them
Closed: It's all good Opened by dustymabe.

Closed: It's all good
Reopen Issue

Now that f29 is out new-udates-sync will no longer sync them from
the compose repo and they will be:

  • atomic host - controlled by the two week releases process
  • silverblue - aliased to the updates ref

To fixup the refs we need to first set the Atomic Host refs to
the appropriate f29 commits from the release we ran today and
for silverblue we need to create the alias.

run the following commands on composer.phx2.fedoraproject.org:

# cd /mnt/koji/atomic/repo/
# 
# sudo ostree --repo=./ refs --delete fedora/29/x86_64/atomic-host
# sudo ostree --repo=./ refs --create=fedora/29/x86_64/atomic-host fedora/29/x86_64/updates/atomic-host
#
# sudo ostree --repo=./ refs --delete fedora/29/aarch64/atomic-host
# sudo ostree --repo=./ refs --create=fedora/29/aarch64/atomic-host fedora/29/aarch64/updates/atomic-host
#
# sudo ostree --repo=./ refs --delete fedora/29/ppc64le/atomic-host
# sudo ostree --repo=./ refs --create=fedora/29/ppc64le/atomic-host fedora/29/ppc64le/updates/atomic-host
#
#
# sudo ostree --repo=./ refs --delete fedora/29/x86_64/silverblue
# sudo ostree --repo=./ refs --alias --create=fedora/29/x86_64/silverblue fedora/29/x86_64/updates/silverblue
# 
# sudo ostree summary -u

cc @sinnykumari

+1

 
$ sudo ostree --repo=./ refs --delete fedora/29/x86_64/silverblue
$ sudo ostree --repo=./ refs --alias --create=fedora/29/x86_64/silverblue fedora/29/x86_64/updates/silverblue
error: Listing refs: openat(fedora/29/x86_64/silverblue): No such file or directory
sudo ostree --repo=./ refs --alias --create=fedora/29/x86_64/silverblue fedora/29/x86_64/updates/silverblue
error: Listing refs: openat(fedora/29/x86_64/silverblue): No such file or directory

ok thanks mohan. this problem is because the updates ref actually doesn't exist for silverblue yet because we haven't run any updates composes yet. The updates ref for atomic-host does exist because we started the twoweek process early. We can fix this by creating the updates ref (based on the commit in the release day silverblue images) in the compose repo and then letting new-updates-sync create the updates ref in the prod repo.

Let's first delete the alias we just created.

# cd /mnt/koji/atomic/repo/
# rm refs/heads/fedora/29/x86_64/silverblue

Then let's create the update ref and alias in the compose repo

# cd /mnt/koji/compose/atomic/repo/
# sudo ostree --repo=./ refs --create=fedora/29/x86_64/updates/silverblue f17b670fa8cf69144be5ae0c968dc2ee7eb6999a5f7a54f1ee71eec7783e434a
# 
# sudo ostree --repo=./ refs --delete fedora/29/x86_64/silverblue
# sudo ostree --repo=./ refs --alias --create=fedora/29/x86_64/silverblue fedora/29/x86_64/updates/silverblue

Wait for new-updates-sync to run. Then create the alias in the prod repo

# cd /mnt/koji/atomic/repo/
# sudo ostree --repo=./ refs --alias --create=fedora/29/x86_64/silverblue fedora/29/x86_64/updates/silverblue
# sudo ostree --repo=./ summary -u
Edited by dustymabe

Yup, that makes sense to me.

Let's first delete the alias we just created.

cd /mnt/koji/atomic/repo/

rm refs/heads/fedora/29/x86_64/silverblue

Then let's create the update ref and alias in the compose repo

cd /mnt/koji/compose/atomic/repo/

sudo ostree --repo=./ refs --create=fedora/29/x86_64/updates/silverblue f17b670fa8cf69144be5ae0c968dc2ee7eb6999a5f7a54f1ee71eec7783e434a

sudo ostree --repo=./ refs --delete fedora/29/x86_64/silverblue

sudo ostree --repo=./ refs --alias --create=fedora/29/x86_64/silverblue fedora/29/x86_64/updates/silverblue

Done. and waiting on the remaining

Wait for new-updates-sync to run. Then create the alias in the prod repo

cd /mnt/koji/atomic/repo/

sudo ostree --repo=./ refs --alias --create=fedora/29/x86_64/silverblue fedora/29/x86_64/updates/silverblue

sudo ostree --repo=./ summary -u

Done. and waiting on the remaining

looks like it's synced. on the stage composer I ran:

[dustymabe@composer repo][STG]$ pwd
/mnt/fedora_koji_prod/koji/atomic/repo
[dustymabe@composer repo][STG]$ ostree show fedora/29/x86_64/updates/silverblue 
commit f17b670fa8cf69144be5ae0c968dc2ee7eb6999a5f7a54f1ee71eec7783e434a
ContentChecksum:  a07a2981b5b7f527c8823d3e6e0f19530c3d1f775d3da2ef2e19433304a8c6a8
Date:  2018-10-24 23:20:30 +0000
Version: 29.1.2
(no subject)
Found 1 signature:
  Signature made Wed 24 Oct 2018 11:20:40 PM UTC using RSA key ID A20AA56B429476B4
  Can't check signature: public key not found

ok mohan ran the final commands and all looks good now I believe!

closing this out.

Metadata Update from @dustymabe:
- Issue close_status updated to: It's all good
- Issue status updated to: Closed (was: Open)

Thanks @dustymabe and @mohanboddu !
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.