-
Notifications
You must be signed in to change notification settings - Fork 870
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
system_cfg not read on Oracle datasource #3938
Comments
Launchpad user Brett Holman(holmanb) wrote on 2022-02-15T21:54:34.768998+00:00 This bug is believed to be fixed in cloud-init in version 22.1. If this is still a problem for you, please make a comment and set the state back to New Thank you. |
Launchpad user Chad Smith(chad.smith) wrote on 2022-03-11T18:11:25.641679+00:00 This fix in Jammy 22.1-14-g2e17a0d6-0ubuntu1~22.04.1 also had an unintended side-effect where network would not get rendered due and newly launched instnaces on Jammy were unreachable due to This commit is being reverted for this release so it can be refactored to avoid the side-effect. |
Launchpad user James Falcon(falcojr) wrote on 2022-04-27T13:47:44.211326+00:00 Every Oracle instance boots with /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg as it was probably intended to ensure only iSCSI configuration is used. While this seems unnecessary to me, there are currently no plans to change this, so I see no reason to keep this bug open. |
Launchpad user Fabio Augusto Miranda Martins(fabio.martins) wrote on 2022-12-15T23:35:49.825539+00:00 CPC has worked on removing /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg from Oracle images and this is completed started with Images with build >=20221123 I just used our daily images to create 3 custom images with:
And launched J/F/B bare-metal instances and I can validate this doesn't cause any issues and the networking is working well on all 3 releases: https://pastebin.ubuntu.com/p/nX7dM7mQSQ/ I believe next step is to proceed with the change proposed by this LP. As a reminder, as part of a post-install script, we'll need to remove /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg if it exists, so that we don't break network for existing instances when they upgrade cloud-init. Marking back as EDIT: Marking as confirmed, as I can't mark as Triaged |
Launchpad user Chad Smith(chad.smith) wrote on 2023-03-05T05:08:38.373951+00:00 Upstream commit landed for this feature 6b9bf7b expected release cloud-init version 23.2. It'll publish sooner into 23.04 (Lunar) in a 23.1.1-## interim snapshot. |
Launchpad user Chad Smith(chad.smith) wrote on 2023-03-05T05:09:41.194907+00:00 Related changeset in Lunar packaging to remove config artifacts across upgrade path on Oracle: #2046 |
Launchpad user Fabio Augusto Miranda Martins(fabio.martins) wrote on 2023-03-06T12:46:03.771268+00:00 I see per the comments that this is being released to Lunar. Is there a plan to backport it to B / F / J? |
Launchpad user James Falcon(falcojr) wrote on 2023-03-06T16:34:59.958139+00:00 Fabio, this one missed the 23.1 release, which is currently in the process of being SRUed. It will make if to F, J, and K (not B as it will be EOL) once 23.2 lands in about 3 months. |
This bug was originally filed in Launchpad as LP: #1956788
Launchpad details
Launchpad user James Falcon(falcojr) wrote on 2022-01-07T18:20:57.658410+00:00
In 2c52e6e , the order of reading network config was changed for Oracle due to initramfs needing to take lower precedence than the datasource. However, this also bumped system_cfg to a lower precedence than ds, which means that any network configuration specified in /etc/cloud will not be applied.
system_cfg should instead be moved above ds so network configuration in /etc/cloud takes precedence.
The text was updated successfully, but these errors were encountered: