I had forgotten to run the repo-regen on Koji. That is finishing up now. I will run another test after and report back.
On Wed, Nov 15, 2017 at 2:08 PM, Patrick Creech <[email protected]> wrote: > On Wed, 2017-11-15 at 14:00 -0500, Patrick Creech wrote: > > On Wed, 2017-11-15 at 19:56 +0100, Lukas Zapletal wrote: > > > I do not have access here, can someone take a look? Are repodata > > > present for EPEL7? > > > > If I have the correct path, it does not appear so: > > > > [root@koji repodata]# pwd > > /mnt/koji/external-repos/epel7-x86_64/epel/repodata > > [root@koji repodata]# ls > > [root@koji repodata]# > > > > I might not have, this path DOES have repodata: > > /mnt/koji/external-repos/www/epel7-x86_64/RPMS.epel/repodata > > > > LZ > > > > > > On Wed, Nov 15, 2017 at 6:15 PM, Ewoud Kohl van Wijngaarden > > > <[email protected]> wrote: > > > > I still get errors when building: > > > > > > > > http://koji.katello.org/koji/taskinfo?taskID=52363 > > > > http://koji.katello.org/kojifiles/work/tasks/2363/52363/root.log > > > > > > > > DEBUG util.py:439: Error downloading packages: > > > > DEBUG util.py:439: 1:nodejs-6.10.3-1.el7.x86_64: failed to > retrieve > > > > nodejs-6.10.3-1.el7.x86_64.rpm from build > > > > DEBUG util.py:439: error was [Errno 2] Local file does not exist: > > > > /mnt/koji/external-repos/www/epel7-x86_64/RPMS.epel/nodejs- > 6.10.3-1.el7.x86_64.rpm > > > > DEBUG util.py:439: http-parser-2.7.1-3.el7.x86_64: failed to > retrieve > > > > http-parser-2.7.1-3.el7.x86_64.rpm from build > > > > DEBUG util.py:439: error was [Errno 2] Local file does not exist: > > > > /mnt/koji/external-repos/www/epel7-x86_64/RPMS.epel/http- > parser-2.7.1-3.el7.x86_64.rpm > > > > DEBUG util.py:439: 1:npm-3.10.10-1.6.10.3.1.el7.x86_64: failed to > > > > retrieve npm-3.10.10-1.6.10.3.1.el7.x86_64.rpm from build > > > > DEBUG util.py:439: error was [Errno 2] Local file does not exist: > > > > /mnt/koji/external-repos/www/epel7-x86_64/RPMS.epel/npm-3. > 10.10-1.6.10.3.1.el7.x86_64.rpm > > > > > > > > > > > > On Wed, Nov 15, 2017 at 11:44:24AM -0500, Eric D Helms wrote: > > > > > > > > > > Looks like everything is back up and working as expected. For > packagers, > > > > > keep in mind that this updated some of our external repositories > to their > > > > > latest versions if you see any oddities. This also means that > Fedora 27 is > > > > > available as an external repository for Pulp and Katello clients. > > > > > > > > > > On Wed, Nov 15, 2017 at 9:32 AM, Lukas Zapletal <[email protected]> > wrote: > > > > > > > > > > > Hey, > > > > > > > > > > > > when I initiated mrepo -n (dry run) this morning to see how mrepo > > > > > > works on our koji in order to test if we are able to add Fedora > 27 for > > > > > > Pulp, I learned that this "dry run" is actually a real run and > mrepo > > > > > > initiated full resync of our content without metadata > regeneration. > > > > > > > > > > > > This rendered our external repositories unusable as all metadata > were > > > > > > deleted. All builds will fail today with missing dependencies. > > > > > > > > > > > > The plan: we need to let mrepo finish "dry run" downloading of > Fedora > > > > > > 27 and then we need to reexecute it with proper flags: > > > > > > > > > > > > cat /usr/local/bin/koji-sync-external-repos > > > > > > #!/bin/bash > > > > > > mrepo -qugf > > > > > > koji list-targets --quiet | awk '{print $2}' | sort -u | xargs > -I '{}' > > > > > > koji regen-repo --nowait '{}' > > > > > > > > > > > > Note the -u -g -f flags for mrepo, this will cause all metadata > to be > > > > > > regenerated. Once this command is done, koji will see missing > > > > > > dependencies to appear. > > > > > > > > > > > > The dry run of mrepo is running in screen and it is about to > finish > > > > > > hopefully soon. I will defer this to Eric in case it won't > finish by > > > > > > EMEA EOB. > > > > > > > > > > > > Sorry for inconvenience, but dry run should be dry run, right. > > > > > > > > > > > > -- > > > > > > Later, > > > > > > Lukas @lzap Zapletal > > > > > > > > > > > > -- > > > > > > You received this message because you are subscribed to the > Google Groups > > > > > > "foreman-dev" group. > > > > > > To unsubscribe from this group and stop receiving emails from > it, send an > > > > > > email to [email protected]. > > > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Eric D. Helms > > > > > Red Hat Engineering > > > > > > > > > > -- > > > > > You received this message because you are subscribed to the Google > Groups > > > > > "foreman-dev" group. > > > > > To unsubscribe from this group and stop receiving emails from it, > send an > > > > > email to [email protected]. > > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > Groups > > > > "foreman-dev" group. > > > > To unsubscribe from this group and stop receiving emails from it, > send an > > > > email to [email protected]. > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > > > > > -- > > > Later, > > > Lukas @lzap Zapletal > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Eric D. Helms Red Hat Engineering -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
