you will need to file a websites bug to get the links to atomic removed. http://koji.fedoraproject.org/koji/taskinfo?taskID=7978937 is the failed task, I am not really sure why it failed to compose. but as it failed and is not a release blocking thing it missed the boat.

Dennis, can we get Kushal access to run (scratch, but whatever it takes) image builds so he can test these in koji? We're getting problems that aren't happening with local imagefactory.

We'd like to have a dev environment to test this for F22 and on, but obviously that's not something we have now.

Replying to [comment:2 mattdm]:

Dennis, can we get Kushal access to run (scratch, but whatever it takes) image builds so he can test these in koji? We're getting problems that aren't happening with local imagefactory.

It would need koji admin privileges as previously discussed.

Is he running the local imagefactory builds in mock? Or just from the command line? In mock he should be able to recreate the problem. The commands we run are basically the bellow, the full script is in the rel-eng git repo.

log "starting atomic tree creation"
git clone https://git.fedorahosted.org/git/fedora-atomic.git $ATOMIC
pushd $ATOMIC
sed -i -e 's|mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-21&arch=$basearch|baseurl=http://kojipkgs.fedoraproject.org/mash/branched/$basearch/os/|g' fedora*repo
$MOCK -r $MOCKCONFIG --uniqueext=$DATE --init
$MOCK -r $MOCKCONFIG --uniqueext=$DATE --install rpm-ostree
$MOCK -r $MOCKCONFIG --uniqueext=$DATE --shell "if [ ! -d $ATOMICDEST ]; then ostree init --repo=$ATOMICDEST ;fi"
$MOCK -r $MOCKCONFIG --uniqueext=$DATE --shell "rpm-ostree compose tree --repo=$ATOMICDEST $ATOMIC/fedora-atomic-docker-host.json"
popd
log "finished atomic tree creation"

Because trac is so terrible:
https://git.fedorahosted.org/cgit/releng/tree/scripts/buildrawhide