-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stop referencing machine-os-content
#457
Comments
The fix for this is included in openshift/installer#6443, particularly openshift/installer@55bbb10 |
@cgwalters not sure you're aware, we just got this from our latest OKD/SCOS CI release try:
|
Ah, that's openshift/driver-toolkit#102 |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
AIUI current OKD is using
machine-os-content
as a way to find "the default OS image" - it's making it be a new format image.I guess actually we could just do that for OCP/RHCOS too, i.e. do a hard cutover and just ship
rhel-coreos-8
as a retagging. I'm not opposed to that. But it feels better to make a "clean cut" and have a new image in the new format, and crucially define a better way to find "the default OS image". Which could just be another new tag...likedefault-operating-system
or something.Anyways the bootstrap phase currently does
and this will eventually break if we do openshift/machine-config-operator#3364
The text was updated successfully, but these errors were encountered: