dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` We enabled mutli-arch in rawhide but there are some errors that are causing it to still fail. From last nights run [here](https://koji.fedoraproject.org/koji/taskinfo?taskID=22000643) is the koji task with subtasks for each arch. ppcle64 and aarch64 fail. Both of them have something like this in their logs:
- aarch64
``` 11:48:22,940 NOTICE python3:libostree HTTP error from remote fedora-atomic for https://kojipkgs.fedoraproject.org/compose/atomic/rawhide/objects/68/ee8ab791293a0d623e2c7b90f3b81b68f03f4188bb802f788d43412123d606.filez: Server returned HTTP 404 ```
- ppc64le
``` 11:52:23,678 NOTICE python3:libostree HTTP error from remote fedora-atomic for https://kojipkgs.fedoraproject.org/compose/atomic/rawhide/objects/ef/4c71090240da389db176f2bcff5ea06501e2451b9f13de924028459fa2afbc.dirtree: Server returned HTTP 404 ```
I can reproduce this problem locally using an ostreesetup line like: ``` ostreesetup --osname="fedora-atomic" --remote="fedora-atomic" --url=https://kojipkgs.fedoraproject.org/compose/atomic/rawhide/ --ref="fedora/rawhide/ppc64le/atomic-host" --nogpg` . ```
It seems like some issue with the repo.
``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/340
dustymabe added a new comment to an issue you are following: `` @walters @jlebon @sinnykumari - FYI ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/340
jlebon added a new comment to an issue you are following: `` To sanity check, those objects are indeed missing from the repo:
``` $ curl -I https://kojipkgs.fedoraproject.org/compose/atomic/rawhide/objects/68/ee8ab79... HTTP/1.1 404 Not Found ...
$ curl -I https://kojipkgs.fedoraproject.org/compose/atomic/rawhide/objects/ef/4c71090... HTTP/1.1 404 Not Found ... ```
Given that it's not `.commit` objects they're clamoring for, my suspicion is that the repo was only partially synced. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/340
dustymabe added a new comment to an issue you are following: ``
Given that it's not .commit objects they're clamoring for, my suspicion is that the repo was only partially synced.
this location: https://kojipkgs.fedoraproject.org/compose/atomic/rawhide/ is the actual location where the `rpm-ostree compose tree` happens. This should not be a syncing issue. One possible issue is that there are 3 `rpm-ostree compose tree` operations happening on this repo simultaneously (one for each architecture). Could that be the problem? ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/340
sinnykumari added a new comment to an issue you are following: `` For my understanding, I want to know how exactly ostreesetup figures out which all files from https://kojipkgs.fedoraproject.org/compose/atomic/rawhide/objects/ it should install on a particular arch (With considering, rpm-ostree compose of all three arches are stored in same directory)? ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/340
sinnykumari added a new comment to an issue you are following: `` Atomic CloudImage from Fedora-Rawhide-20170922.n.0 compose built successfully on multi-arch (x86_64, ppc64le and aarch64). Koji build link - https://koji.fedoraproject.org/koji/taskinfo?taskID=22020024 \o/ ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/340
dustymabe added a new comment to an issue you are following: `` Over the past 4 days we haven't seen this issue again. I'll close this and we'll look out for it happening again. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/340
The status of the issue: `failures pulling objects when building ppc64le/aarch64 ISOS` of project: `atomic-wg` has been updated to: Closed as Invalid by dustymabe.
atomic@lists.fedoraproject.org
-
Dusty Mabe -
Jonathan Lebon
-
Sinny Kumari