flatcar
changelog: disable DHCP RapidCommit for CloudSigma OEM
Disable DHCP RapidCommit for CLoudSigma OEM
This is related to the following issue: https://github.com/flatcar/Flatcar/issues/1438
How to use
Build OEM beta image and upload it to CloudSigma. Create a host with said image.
Testing done
I tested this by manually applying the OEM config to the /oem/cloud-config.yml file and rebooting.
Note: This is my idea how to fix this issue, i am unsure if this is the desired solution and if this is the right branch to merge into as it currently only is an issue on beta builds.
Thanks for checking in to this, i will try to build it locally. Have never done it so we will see how it goes :).
So i was finally able to test this.
While it does work, it only works after a reboot since the network configuration is already loaded at that point.
I was not able to figure out how to restart the network service. I tried:
runcmd:
- sudo systemctl restart systemd-networkd
But found out later that runcmd is not supported by the coreos-cloudinit implementation.
Do you have a suggestion on how i could do that?
Regards,
David
By the way, what is the plan of moving the next beta to stable? Since it would break for us at that point :)
Okay, so after a bit of looking around in the coreos-cloud i found out that one can also provide network units to cores.units, this doesn't seem to be documented super well.
I built a custom image based on the latest beta and applied this change. This does now seem to work as intended.
Not sure if i require runtime: True i don't think it matters as it will write the file on every boot anyway?
Regards,
David
@ader1990 Hi :),
Thank You for the initial review! Is there anything else i can provide to help this PR?
This seems to have missed the stable now. I would like to ask again what there is we can provide to integrate this. We currently require an own image which we would like to stop again.
This seems to have missed the stable now. I would like to ask again what there is we can provide to integrate this. We currently require an own image which we would like to stop again.
Hello @daMupfel sorry for the delay on this PR and thanks for pinging us again. It looks good to me:
- Do you want me to build an image for you to test with a built image?
- I think we can backport this to alpha and beta first before stable
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
@tormath1 Hi :), no worries. Just wanted to know where we stand here :).
Thank you very much for looking into this.
I think I adapted the PR as you requested.
Regarding the built. I was able to do so by following the documentation (with the container and then the main build and than the specific built). I can test it again if you want. The last time i applied it on the last beta image (which was promoted to stable).
Regards,
David
@daMupfel I was about to merge this change but I just noticed that there is only one commit that contains the two changes (the actual change and the changelog entry) - you can split this change into two commits, e.g:
- changelog: add entry
- disable DHCP rapidcommit for cloud sigma
or just amend the commit to something like disable DHCP rapidcommit for cloud sigma
cherry-picked to:
- flatcar-4081 (current alpha)
- flatcar-4054 (current beta)
Thanks for your change!
By the way, I noticed there is no documentation for CloudSigma - is there any specific things to know to use Flatcar on this platform?
@tormath1 Thank you very much for taking care of my PR!
We don't have any affiliation other than being customers of CloudSigma. At some point, CloudSigma made an effort to support CoreOS, which is where this comes from. At that time, one could select CoreOS as a base image for new VMs. CoreOS then disappeared at some point from the UI. What we do nowadays is convert the OEM image to a raw image and then upload it as a custom base image to CloudSigma.
Please take this with a grain of salt since I am only an external observer.