Skip to content

Conversation

@stbenjam
Copy link
Member

Instead of hardcoding the RHCOS version in dev-scripts, by re-ordering
some things like extracting/building the installer first, we can use the
rhcos.json from the installer to find out which RHCOS version we should
be using.

@stbenjam stbenjam added the CI check this PR with CI label Aug 28, 2019
@stbenjam
Copy link
Member Author

This could be an alternative to #766

@metal3ci
Copy link

Build FAILURE, see build http://10.8.144.11:8080/job/dev-tools/1109/

@stbenjam stbenjam force-pushed the rhcos-from-installer branch from f9f3ce4 to 0df6722 Compare August 28, 2019 20:12
@metal3ci
Copy link

Build SUCCESS, see build http://10.8.144.11:8080/job/dev-tools/1110/

@stbenjam stbenjam force-pushed the rhcos-from-installer branch from 0df6722 to 2975c76 Compare August 28, 2019 23:29
@stbenjam stbenjam changed the title [WIP] Always use RHCOS version from installer Always use RHCOS version from installer Aug 28, 2019
@stbenjam stbenjam removed the CI check this PR with CI label Aug 28, 2019
@hardys
Copy link

hardys commented Aug 29, 2019

cc @rlopez133 we discussed this approach for install-scripts

@hardys
Copy link

hardys commented Aug 29, 2019

looks good, we can see the CI pass used the right image:

Aug 28 20:27:23 |  ++ RHCOS_IMAGE_FILENAME=rhcos-42.80.20190827.1-openstack.qcow2
Aug 28 20:27:23 |  ++ export RHCOS_INSTALLER_IMAGE_URL=https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.2/42.80.20190827.1/rhcos-42.80.20190827.1-openstack.qcow2

However I think there's a rebase mistake which accidentally reverts #776 ?

Copy link

@hardys hardys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other than now needing a rebase, and possible optimization of not downloading rhcos.json in the source case (not blocking on that though) lgtm, thanks!

@stbenjam stbenjam force-pushed the rhcos-from-installer branch from 2975c76 to ceb9867 Compare August 29, 2019 11:40
@stbenjam stbenjam added the CI check this PR with CI label Aug 29, 2019
Instead of hardcoding the RHCOS version in dev-scripts, by re-ordering
some things like extracting/building the installer first, we can use the
rhcos.json from the installer to find out which RHCOS version we should
be using.
@stbenjam stbenjam force-pushed the rhcos-from-installer branch from ceb9867 to 33667e6 Compare August 29, 2019 11:42
@metal3ci
Copy link

Build SUCCESS, see build http://10.8.144.11:8080/job/dev-tools/1112/

@stbenjam
Copy link
Member Author

Ready for another look, CI passed and I fixed it so it reads rhcos.json from the git repo if we're doing a source install.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI check this PR with CI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants