-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Swiftless OpenStack: store bootstrap ignition configs in Glance #2960
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
Conversation
The newest version includes important features, like HTTP headers support, that are required for the successful installation of OpenShift on OpenStack without Swift.
|
openstack tests will fail until we upgrade the rhcos image in the installer |
|
/retest |
2 similar comments
|
/retest |
|
/retest |
|
/test e2e-aws |
|
/retest |
1 similar comment
|
/retest |
|
Looks like the OpenStack job failed to come up? AWS came up fine, so the bump to Ignition spec 2.4 doesn't seem to have caused a problem. Still would be nice to see those green though. /retest |
|
Dropping the Swift from destroy means that if I created a cluster using 4.2 and tried to destroy the closer with this new installer, we leak the Swift objects |
|
That's a good point. I think we have to support swift deletion indefinitely. |
|
Once you address Abhinav's comment, LGTM |
|
Hmm, fresh OpenStack run died the same way? |
|
@wking yeah,to make OpenStack test pass we need to bump Ignition in the pre-release image first: https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/pre-release/ |
|
@abhinavdahiya I didn't drop Swift from the destroy module. I just added a check that if there is no Swift service we are fine with it: https://github.com/openshift/installer/pull/2960/files#diff-3420abf882f61be73bc30ef12460687dR547-R550 I removed Swift code from bootstrap destruction ( So, this patch only affects the bootstrapping process and all other parts stay the same. |
| ) | ||
|
|
||
| // DeleteSwiftContainer deletes a container and all of its objects. | ||
| func DeleteSwiftContainer(name string, cloud string) error { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is strange that you can now safely remove this. What if folks want to delete a cluster created by a previous installer (and so using Swift) which got a Swift bootstrap Ignition store, but then failed to install. Wouldn't that leak the Swift container with destroy cluster not using this function? Of course, the fact that nothing else in pkg/destroy/openstack calls this function means that leak is not new in this PR. But it still seems like a leak to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Never mind, @Fedosin points out that this function was pretty similar to deleteContainers, which is left alone by this PR.
|
/retest |
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sdodson The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test e2e-openstack |
|
openstack tests are green |
|
/hold cancel |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@Fedosin: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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. I understand the commands that are listed here. |
Some openstack environments do not allow users to upload or download image data. This is because the cloud providers prevent them from using illegal images on the openstack or getting proprietary images on a local. This PR is based on the Swift functions removed in PR openshift#2960 and adds the feature to store a ignition file in Swift when an upload in Glance fails, as follows: Glance | Swift | used enable | enable | storage --------+--------+--------- v | v | Glance v | | Glance | v | Swift <- this PR | | none Signed-off-by: ERAMOTO Masaya <[email protected]>
Now we store bootstrap ignition configs in Swift storage, but unfortunately Swift is not available on all OpenStack clouds. It leads to the fact that we can't deploy OpenShift on such swiftless clouds.
This PR allows to store configs in Glance, which is available on 100% of OpenStack clouds.