Hello,
my attempt to (scratch) build an EPEL 8 package failed with
https://kojipkgs.fedoraproject.org//work/tasks/9259/37759259/root.log
DEBUG util.py:593: Error: Error downloading packages: DEBUG util.py:593: Status code: 404 for https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/... DEBUG util.py:741: Child return code was: 1
I assume it's not something I could affect from my fedpkg side.
Is that a known issue? What is the best way to report it?
On Fri, 20 Sep 2019 at 06:53, Jan Pazdziora jpazdziora@redhat.com wrote:
Hello,
my attempt to (scratch) build an EPEL 8 package failed with
https://kojipkgs.fedoraproject.org//work/tasks/9259/37759259/root.log DEBUG util.py:593: Error: Error downloading packages: DEBUG util.py:593: Status code: 404 for https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-80.11.1.el8_0.x86_64.rpm DEBUG util.py:741: Child return code was: 1
I assume it's not something I could affect from my fedpkg side.
Is that a known issue? What is the best way to report it?
It isn't a known issue.. I would report it as a releng issue so whatever I wrote to try and make this work can be fixed.
Looking at the tree
-rw-r--r--. 1 root sysadmin-main 434036 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-4.18.0-80.11.2.el8_0.x86_64.rpm -rw-r--r--. 1 root sysadmin-main 438636 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-abi-whitelists-4.18.0-80.11.2.el8_0.noarch.rpm -rw-r--r--. 1 root sysadmin-main 24802356 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-core-4.18.0-80.11.2.el8_0.x86_64.rpm -rw-r--r--. 1 root sysadmin-main 5191712 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-cross-headers-4.18.0-80.11.2.el8_0.x86_64.rpm -rw-r--r--. 1 root sysadmin-main 434148 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-debug-4.18.0-80.11.2.el8_0.x86_64.rpm -rw-r--r--. 1 root sysadmin-main 46589036 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-debug-core-4.18.0-80.11.2.el8_0.x86_64.rpm -rw-r--r--. 1 root sysadmin-main 12965136 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-debug-devel-4.18.0-80.11.2.el8_0.x86_64.rpm -rw-r--r--. 1 root sysadmin-main 40150300 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-debug-modules-4.18.0-80.11.2.el8_0.x86_64.rpm -rw-r--r--. 1 root sysadmin-main 1619632 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-debug-modules-extra-4.18.0-80.11.2.el8_0.x86_64.rpm -rw-r--r--. 1 root sysadmin-main 12829460 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-devel-4.18.0-80.11.2.el8_0.x86_64.rpm -rw-r--r--. 1 root sysadmin-main 16031932 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-doc-4.18.0-80.11.2.el8_0.noarch.rpm -rw-r--r--. 1 root sysadmin-main 1650432 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-80.11.2.el8_0.x86_64.rpm -rw-r--r--. 1 root sysadmin-main 20939020 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-modules-4.18.0-80.11.2.el8_0.x86_64.rpm -rw-r--r--. 1 root sysadmin-main 1065180 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-modules-extra-4.18.0-80.11.2.el8_0.x86_64.rpm -rw-r--r--. 1 root sysadmin-main 51548 2019-06-24 23:34 latest/x86_64/RHEL-8-001/non_modular/kernel-rpm-macros-116-1.el8.noarch.rpm -rw-r--r--. 1 root sysadmin-main 587436 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-tools-4.18.0-80.11.2.el8_0.x86_64.rpm -rw-r--r--. 1 root sysadmin-main 443480 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-tools-libs-4.18.0-80.11.2.el8_0.x86_64.rpm -rw-r--r--. 1 root sysadmin-main 436704 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-tools-libs-devel-4.18.0-80.11.2.el8_0.x86_64.rpm
So the .2 kernel is the one which should be used. I don't see a timestamp in the file you provided so I am not sure if this build problem occurred near the 09:25 listed above or not.
On Fri, Sep 20, 2019 at 09:21:21AM -0400, Stephen John Smoogen wrote:
On Fri, 20 Sep 2019 at 06:53, Jan Pazdziora jpazdziora@redhat.com wrote:
my attempt to (scratch) build an EPEL 8 package failed with
https://kojipkgs.fedoraproject.org//work/tasks/9259/37759259/root.log DEBUG util.py:593: Error: Error downloading packages: DEBUG util.py:593: Status code: 404 for https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-80.11.1.el8_0.x86_64.rpm DEBUG util.py:741: Child return code was: 1
I assume it's not something I could affect from my fedpkg side.
Is that a known issue? What is the best way to report it?
It isn't a known issue.. I would report it as a releng issue so whatever I wrote to try and make this work can be fixed.
Looking at the tree
-rw-r--r--. 1 root sysadmin-main 434036 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-4.18.0-80.11.2.el8_0.x86_64.rpm
[...]
latest/x86_64/RHEL-8-001/non_modular/kernel-tools-libs-devel-4.18.0-80.11.2.el8_0.x86_64.rpm
So the .2 kernel is the one which should be used. I don't see a timestamp in the file you provided so I am not sure if this build problem occurred near the 09:25 listed above or not.
Thanks Stephen for looking at it. I don't see the same problem today and I was able to build the package.
On Mon, 23 Sep 2019 at 04:49, Jan Pazdziora jpazdziora@redhat.com wrote:
On Fri, Sep 20, 2019 at 09:21:21AM -0400, Stephen John Smoogen wrote:
On Fri, 20 Sep 2019 at 06:53, Jan Pazdziora jpazdziora@redhat.com wrote:
my attempt to (scratch) build an EPEL 8 package failed with
https://kojipkgs.fedoraproject.org//work/tasks/9259/37759259/root.log DEBUG util.py:593: Error: Error downloading packages: DEBUG util.py:593: Status code: 404 for https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-80.11.1.el8_0.x86_64.rpm DEBUG util.py:741: Child return code was: 1
I assume it's not something I could affect from my fedpkg side.
Is that a known issue? What is the best way to report it?
It isn't a known issue.. I would report it as a releng issue so whatever I wrote to try and make this work can be fixed.
Looking at the tree
-rw-r--r--. 1 root sysadmin-main 434036 2019-09-20 09:25 latest/x86_64/RHEL-8-001/non_modular/kernel-4.18.0-80.11.2.el8_0.x86_64.rpm
[...]
latest/x86_64/RHEL-8-001/non_modular/kernel-tools-libs-devel-4.18.0-80.11.2.el8_0.x86_64.rpm
So the .2 kernel is the one which should be used. I don't see a timestamp in the file you provided so I am not sure if this build problem occurred near the 09:25 listed above or not.
Thanks Stephen for looking at it. I don't see the same problem today and I was able to build the package.
What I think might be happening is that due to the time it takes to download repos from CDN, and then rebuild the repository there is a window where the build can break. In an ideal (aka this wasn't done in spare time and actually had a budget and staff), the script would see if there were builds for EPEL going, tell koji to not let any more on, wait until the last one was cleared, then move the link to the latest repo, then tell koji to rebuild its cache and finally let EPEL builds start again.