cloud-atomic: Bring sanity to the remote setup

We were doing gyrations here between the "installmedia" remote and the
intended "fedora-atomic" remote.  Thinking about this, it's *far*
simpler if we pretend installmedia is the target remote.

We still need to delete the remote configuration Anaconda added and
re-add it with the real target URL.

Conflicts:
	fedora-cloud-atomic.ks
This commit is contained in:
Colin Walters 2014-11-17 15:55:35 -05:00
parent 5710f9ff65
commit 90e71f7a4b

View File

@ -30,11 +30,14 @@ volgroup atomicos pv.01
logvol / --size=3000 --fstype="xfs" --name=root --vgname=atomicos
# Equivalent of %include fedora-repo.ks
ostreesetup --nogpg --osname=fedora-atomic-host --remote=installmedia --url=http://kojipkgs.fedoraproject.org/mash/atomic/rawhide/ --ref=fedora-atomic/rawhide/x86_64/docker-host
ostreesetup --nogpg --osname=fedora-atomic-host --remote=fedora-atomic --url=http://kojipkgs.fedoraproject.org/mash/atomic/rawhide/ --ref=fedora-atomic/rawhide/x86_64/docker-host
reboot
%post --erroronfail
# See https://github.com/projectatomic/rpm-ostree/issues/42
ostree remote delete fedora-atomic
ostree remote add --set=gpg-verify=false fedora-atomic 'http://dl.fedoraproject.org/pub/fedora/linux/atomic/rawhide/'
# older versions of livecd-tools do not follow "rootpw --lock" line above
# https://bugzilla.redhat.com/show_bug.cgi?id=964299