December 2014 - rel-eng - Fedora Mailing-Lists

#4985: Extend test image creation SOP to require notification of delays

by Fedora Release Engineering

#4985: Extend test image creation SOP to require notification of delays ----------------------+----------------------------------------------------- Reporter: adamwill | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | ----------------------+----------------------------------------------------- Working through the F16 QA retrospective here: https://fedoraproject.org/wiki/Fedora_16_QA_Retrospective One of the notes is: "jlaska - Alpha TC1 - Missed the Alpha-TC1 milestone by 1 week, little to no communication regarding status. With only two weeks Alpha ISO test time, losing 50% of time almost certainly results in a slip. See rel-eng ticket#4844 . None of the Alpha rel-eng release tickets have been filed at this time. adamw - perhaps releng image compose SOP should require updating of ticket with progress info, especially when image compose / delivery is delayed?" So: this ticket proposes that the releng 'Composing test images' SOP - https://fedoraproject.org/wiki/Composing_test_images - should be extended to require whoever is creating the images to post a comment on the image request ticket if the compose is delayed, explaining the reasons for the delay (so that any other interested party can attempt to contribute to resolving them) and giving a best estimate of an ETA if possible (so other groups can adjust their scheduling as best they can). Thanks! -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4985> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 1 month

1
4
0 / 0

#5836: Update gitolite to gitolite3

by Fedora Release Engineering

#5836: Update gitolite to gitolite3 ------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: git Keywords: | Blocked By: Blocking: | ------------------+------------------------ The package gitolite3 in EPEL should be used to update gitolite for dist- git. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5836> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 1 month

1
2
0 / 0

#5924: CPUID flags on buildvm-20.phx2.fedoraproject.org

by Fedora Release Engineering

#5924: CPUID flags on buildvm-20.phx2.fedoraproject.org -----------------------------+------------------------ Reporter: jakub | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 21 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ In the gcc-4.9.0-12.fc21 build logs I saw a weird error: /builddir/build/BUILD/gcc-4.9.0-20140619/obj-x86_64-redhat-linux/gcc/xgcc -B/builddir/build/BUILD/gcc-4.9.0-20140619/obj-x86_64-redhat-linux/gcc/ /builddir/build/BUILD/gcc-4.9.0-20140619/gcc/testsuite/gcc.target/i386/pr57275.c -fno-diagnostics-show-caret -fdiagnostics-color=never -O3 -march=native -lm -o ./pr57275.exe /builddir/build/BUILD/gcc-4.9.0-20140619/gcc/testsuite/gcc.target/i386/pr57275.c:1:0: error: CPU you selected does not support x86-64 instruction set and I'd like to debug that, but don't know of a way to force e.g. a scratch rpm build to a particular build host. Would it be possible for some release engineer to run gcc -v -march=native -S -xc /dev/null -o /tmp/foo.s cat /proc/cpuinfo in the F21 mock chroot on that box? Perhaps we are missing something in the -m{arch,tune}=native logic, a CPU which clearly does support x86_64 64-bit ISA should not be determined as one that does not. Thanks. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5924> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 1 month

1
3
0 / 0

#6038: rawhide cloud image nightlies failing with "Could not reach destination to fetch boot media"

by Fedora Release Engineering

#6038: rawhide cloud image nightlies failing with "Could not reach destination to fetch boot media" -----------------------------+------------------------ Reporter: mattdm | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 21 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Rawhide nightly cloud images are failing, and Oz gives the error "Could not reach destination to fetch boot media". See for example: http://koji.fedoraproject.org/koji/taskinfo?taskID=8080223 This is obviously less urgent than all F21-related tasks, but would be nice to have fixed. Thanks! -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6038> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 1 month

1
3
0 / 0

#6056: Branched: no images/ or LiveOS/ directory created due to package conflicts

by Fedora Release Engineering

#6056: Branched: no images/ or LiveOS/ directory created due to package conflicts -----------------------------+------------------------ Reporter: kparal | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 21 Final | Component: mash Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ 20141125 is the last day we have images/, LiveOS/ and similar directories: http://koji.fedoraproject.org/mash/branched-20141125/21/x86_64/os/ After that, only Packages/ and repodata/ are available: http://koji.fedoraproject.org/mash/branched-20141127/21/x86_64/os/ The log says: {{{ yum.verbose.YumBase.INFO_2: Running Transaction Check pylorax.ltmpl.ERROR: template command error in runtime-install.tmpl: pylorax.ltmpl.ERROR: run_pkg_transaction pylorax.ltmpl.ERROR: YumRPMCheckError: [u'ERROR with transaction check vs depsolve:', 'fedora-productimg-cloud conflicts with fedora-productimg- workstation-21-6.fc21.noarch', 'fedora-productimg-server conflicts with fedora-productimg-workstation-21-6.fc21.noarch', 'fedora-productimg-server conflicts with fedora-productimg-cloud-21-6.fc21.noarch', 'fedora- productimg-workstation conflicts with fedora-productimg- cloud-21-6.fc21.noarch', 'fedora-productimg-cloud conflicts with fedora- productimg-server-21-6.fc21.noarch', 'fedora-productimg-workstation conflicts with fedora-productimg-server-21-6.fc21.noarch'] pylorax.ltmpl.DEBUG: Traceback (most recent call last): pylorax.ltmpl.DEBUG: File "/usr/lib/python2.7/site- packages/pylorax/ltmpl.py", line 508, in run_pkg_transaction pylorax.ltmpl.DEBUG: rpmDisplay=LoraxRpmCallback()) pylorax.ltmpl.DEBUG: File "/usr/lib/python2.7/site- packages/yum/__init__.py", line 6469, in processTransaction pylorax.ltmpl.DEBUG: self._doTestTransaction(callback,display=rpmTestDisplay) pylorax.ltmpl.DEBUG: File "/usr/lib/python2.7/site- packages/yum/__init__.py", line 6548, in _doTestTransaction pylorax.ltmpl.DEBUG: raise Errors.YumRPMCheckError,retmsgs pylorax.ltmpl.DEBUG: YumRPMCheckError: [u'ERROR with transaction check vs depsolve:', 'fedora-productimg-cloud conflicts with fedora-productimg- workstation-21-6.fc21.noarch', 'fedora-productimg-server conflicts with fedora-productimg-workstation-21-6.fc21.noarch', 'fedora-productimg-server conflicts with fedora-productimg-cloud-21-6.fc21.noarch', 'fedora- productimg-workstation conflicts with fedora-productimg- cloud-21-6.fc21.noarch', 'fedora-productimg-cloud conflicts with fedora- productimg-server-21-6.fc21.noarch', 'fedora-productimg-workstation conflicts with fedora-productimg-server-21-6.fc21.noarch'] }}} http://koji.fedoraproject.org/mash/branched-20141127/logs/x86_64.log I'm not sure whether this affects our ability to create a full Fedora 21 release compose? -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6056> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 1 month

1
2
0 / 0

#5959: Enable keep-alive connections for koji (primary and secondaries)

by Fedora Release Engineering

#5959: Enable keep-alive connections for koji (primary and secondaries) -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Final | Component: koji Keywords: meeting | Blocked By: Blocking: | -----------------------------+------------------------ Keeping connections alive will speed up koji acces when multiCall() is not used without a significant speed penalty. Therefore it is a good idea to support this. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5959> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 1 month

1
4
0 / 0

Lookaside: Move away from md5

by Mathieu Bridon

We should move to something more secure than md5 for the uploaded sources. This patch series implements the client-side part of this change. We might want to drop the md5 fallback once we have migrated completely, that is when: 1. all archives on the lookaside have been moved to a stronger hash 2. the "sources" file in all git repos has been updated to the same hash https://fedorahosted.org/rel-eng/ticket/5846

9 years, 2 months

5
10
0 / 0

#5846: move away from md5 for look-aside cache

by Fedora Release Engineering

#5846: move away from md5 for look-aside cache ------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: other Keywords: | Blocked By: Blocking: | ------------------+------------------------ The lookaside cache uses md5, but something more secure like sha-256 or sha-512 should be used instead. Maybe it should even be made to allow easy changes in the future. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5846> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 2 months

1
22
0 / 0

#5992: Create new fedora-ca certificates without SHA1

by Fedora Release Engineering

#5992: Create new fedora-ca certificates without SHA1 -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Currently .fedora-server-ca.cert and .fedora-upload-ca.cert use SHA1 for their self-signatures. Since SHA1 support is phased out, it might be a good idea to re-create the signatures. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5992> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 2 months

1
1
0 / 0

#6023: allow Peter Robinson to restart sigul bridges

by Fedora Release Engineering

#6023: allow Peter Robinson to restart sigul bridges -----------------------------+------------------------ Reporter: till | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Final | Component: koji Keywords: meeting | Blocked By: Blocking: | -----------------------------+------------------------ The sigul bridges are very unstable, but currently nobody from Europe can restart it, therefore it might be unusable for a long time until Dennis Gilmore or Kevin Fenzi find the time to restart it. Especially to get the autosigner run smoothly it would be better to have at least one more being able to restart the bridges. Peter Robinson would be a good candidate. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6023> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 2 months

1
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng December 2014