Skip to content
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

change default ubuntu image from DO #1213

Merged
merged 1 commit into from
Aug 31, 2023

Conversation

felipe-colussi
Copy link
Contributor

@felipe-colussi felipe-colussi commented Aug 31, 2023

Issue: #1215

Problem

Wile testing the migration of SDK to SDK2 I noticed that the default image for DO is no longer valid.

[tf-do-image.zip](https://github.com/rancher/terraform-provider-rancher2/files/12486407/tf-do-image.zip) Error creating machine: Error in driver during machine creation: POST https://api.digitalocean.com/v2/droplets: 422 You specified an invalid image for Droplet creation.

After checking DO only supports ubuntu 20 and 22.

Solution

Update the DO default image to: ubuntu-22-04-x64

Testing

Engineering Testing

Manual Testing

Using the terraform as it is:
Tried to generate a UBUNTU RKE cluster using the default image. It fails.
Change the image for ubuntu-22-04-x64 , it works.

After the change:
I ran the tf with an empty image. It worked.

TF files:
tf-do-image.zip

Automated Testing

I ran the automated tests.
That said I didn't create one to test the "Default" value provided by TF SDK.

QA Testing Considerations

Regressions Considerations

Copy link
Contributor

@a-blender a-blender left a comment

Choose a reason for hiding this comment

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

@felipe-colussi Prov an RKE cluster on DO didn't give you any ssh/networking issues like you saw before? Not sure if the fix for this is a fix for what you were seeing a few days ago. Otherwise great catch!

@felipe-colussi
Copy link
Contributor Author

felipe-colussi commented Aug 31, 2023

@a-blender

@felipe-colussi Prov an RKE cluster on DO didn't give you any ssh/networking issues like you saw before? Not sure if the fix for this is a fix for what you were seeing a few days ago. Otherwise great catch!

Nop, that was happening on AWS, so I swapped to DO and got this image error :/

@felipe-colussi felipe-colussi merged commit 0f4a482 into rancher:master Aug 31, 2023
@felipe-colussi felipe-colussi deleted the fix_do_image branch August 31, 2023 19:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants