-
Notifications
You must be signed in to change notification settings - Fork 821
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
Openstack Datasource not detected in Oracle cloud #5091
Comments
cc: @cjp256 could you please shed some light on this? |
@palash-delphix Sorry for closing earlier, I accidentally hit the "Close with comment" while in the middle of writing my comment. I'm working on reproducing this, but in the mean time, can you explain what you're trying to achieve with this configuration? Why does |
Also, if you determine that, for some reason your images/platform needs require OpenStack datasource to be used. This could be resolved without any changes to cloud-init or ds-identify given a simple config file change if you have reasons to retain OpenStack datasource instead of Oracle platform. From the looks of the DataSourceOpenStack.ds_detect. If It looks like the following config could be provided in
This will tell the unique DataSourceOpenStack.ds_detect logic to prefer OpenStack datasource detection on any system which exposes chassis asset tag= |
ds-identify would automatically append "None" to the datasource_list if a single entry was provided in /etc/cloud/cloud.cfg[.d]. This wasn't a problem in the past as the python code would detect a single datasource along with None as an indication to automatically use that datasource. Since the python code no longer does that, we should ensure that one specified datasource results in one specified datasource after ds-identify has run. Fixes canonicalGH-5091
@TheRealFalcon and @blackboxsw Thank you for the quick response and fix. Much appreciated. |
This change may require a user to add `None` to the `datasource_list` defined in `/etc/cloud/cloud.cfg[.d]` if they have a customized datasource_list and want the DataSourceNone fallback behavior. ds-identify would automatically append "None" to the datasource_list if a single entry was provided in /etc/cloud/cloud.cfg[.d]. This wasn't a problem in the past as the python code would detect a single datasource along with None as an indication to automatically use that datasource. Since the python code no longer does that, we should ensure that one specified datasource results in one specified datasource after ds-identify has run. Fixes canonicalGH-5091
This change may require a user to add `None` to the `datasource_list` defined in `/etc/cloud/cloud.cfg[.d]` if they have a customized datasource_list and want the DataSourceNone fallback behavior. ds-identify would automatically append "None" to the datasource_list if a single entry was provided in /etc/cloud/cloud.cfg[.d]. This wasn't a problem in the past as the python code would detect a single datasource along with None as an indication to automatically use that datasource. Since the python code no longer does that, we should ensure that one specified datasource results in one specified datasource after ds-identify has run. Fixes GH-5091
This change may require a user to add `None` to the `datasource_list` defined in `/etc/cloud/cloud.cfg[.d]` if they have a customized datasource_list and want the DataSourceNone fallback behavior. ds-identify would automatically append "None" to the datasource_list if a single entry was provided in /etc/cloud/cloud.cfg[.d]. This wasn't a problem in the past as the python code would detect a single datasource along with None as an indication to automatically use that datasource. Since the python code no longer does that, we should ensure that one specified datasource results in one specified datasource after ds-identify has run. Fixes GH-5091
This change may require a user to add `None` to the `datasource_list` defined in `/etc/cloud/cloud.cfg[.d]` if they have a customized datasource_list and want the DataSourceNone fallback behavior. ds-identify would automatically append "None" to the datasource_list if a single entry was provided in /etc/cloud/cloud.cfg[.d]. This wasn't a problem in the past as the python code would detect a single datasource along with None as an indication to automatically use that datasource. Since the python code no longer does that, we should ensure that one specified datasource results in one specified datasource after ds-identify has run. Fixes GH-5091
This change may require a user to add `None` to the `datasource_list` defined in `/etc/cloud/cloud.cfg[.d]` if they have a customized datasource_list and want the DataSourceNone fallback behavior. ds-identify would automatically append "None" to the datasource_list if a single entry was provided in /etc/cloud/cloud.cfg[.d]. This wasn't a problem in the past as the python code would detect a single datasource along with None as an indication to automatically use that datasource. Since the python code no longer does that, we should ensure that one specified datasource results in one specified datasource after ds-identify has run. Fixes GH-5091
Bug report
It looks like recent changes from this PR #4426 have caused an issue in cloud-init where the datasource is not detected causing cloud-init configuration to be ignored.
Here's what we see in the logs:
It looks like the
ds-identify
script creates a list with "None":In our cloud-init configuration, the last file to be read lexicographically contains:
The PR mentions:
How are we supposed to do so? The cfg files we have do not have None in the list to begin with.
Steps to reproduce the problem
This should be reproducible by creating a cfg file like the one above and attempting to run
cloud-init clean
and thencloud-init init
. Unfortunately, I do not have an easy way to spin up a vanilla Ubuntu instance in our OCI account but if the issue is not obvious to the maintainers, I can try to spend some time requesting the required access internally.Environment details
cloud-init logs
The text was updated successfully, but these errors were encountered: