|
Bugzilla – Full Text Bug Listing |
| Summary: | cloud-init: datasource ConfigDrive fails | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Eugen Block <eugen.block> |
| Component: | Cloud:Tools | Assignee: | SUSE Public Cloud Maintainer <public-cloud-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | eugen.block, rjschwei |
| Version: | Leap 15.1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
cloud-init.log
cloud-init-output.log |
||
|
Description
Eugen Block
2019-10-15 14:50:06 UTC
Created attachment 821580 [details]
cloud-init-output.log
Is this the same image but with 2 different cloud.cfg files? The message is not related to using config drive, the code cannot determine in which configuration the network should be written out. In order to find the proper rendering mechanism (the way the network configuration is written) for the network configuration code searches for specific commands to be available. For openSUSE and SLE, or in general to use the code that writes entries for "sysconfig" cloud-init looks for the 'ifup' and 'ifdown' commands. In this case it appears as if these command are missing from the image being tested. This would trigger the error message shown in the initial comment. It is known that the proper network writing code is selected for images with the 'ifup' and 'ifdown' commands included. This suggests an issue with the image. (In reply to Robert Schweikert from comment #2) > Is this the same image but with 2 different cloud.cfg files? No, these are both log files written by cloud-init during the same boot process of one instance. > The message is not related to using config drive, the code cannot determine > in which configuration the network should be written out. > > In order to find the proper rendering mechanism (the way the network > configuration is written) for the network configuration code searches for > specific commands to be available. For openSUSE and SLE, or in general to > use the code that writes entries for "sysconfig" cloud-init looks for the > 'ifup' and 'ifdown' commands. > > In this case it appears as if these command are missing from the image being > tested. This would trigger the error message shown in the initial comment. > > It is known that the proper network writing code is selected for images with > the 'ifup' and 'ifdown' commands included. > > This suggests an issue with the image. This image contains both commands: leap15-1-cloudinit:~ # which ifup /sbin/ifup leap15-1-cloudinit:~ # which ifdown /sbin/ifdown leap15-1-cloudinit:~ # Running those commands manually after cloud-init has finished (unsuccessfully) did work in a previous version of cloud-init, but it doesn't with Leap 15.1. Can you please try again with the latest build from Cloud:Tools? There is a condition in determining the sysconfig renderer that also required some file we do not have on openSUSE SLE. I added a patch to short circuit this condition. That should fix the issue with the renderer not being found. This is an autogenerated message for OBS integration: This bug (1154092) was mentioned in https://build.opensuse.org/request/show/741941 Factory / cloud-init (In reply to Robert Schweikert from comment #4) > Can you please try again with the latest build from Cloud:Tools? > > There is a condition in determining the sysconfig renderer that also > required some file we do not have on openSUSE SLE. I added a patch to short > circuit this condition. That should fix the issue with the renderer not > being found. That looks good, the instance is configured correctly both via datasources OpenStack and ConfigDrive. Thanks! SUSE-SU-2019:3097-1: An update that solves one vulnerability and has 6 fixes is now available. Category: security (moderate) Bug References: 1099358,1129124,1136440,1142988,1144363,1151488,1154092 CVE References: CVE-2019-0816 Sources used: SUSE Linux Enterprise Module for Public Cloud 15 (src): cloud-init-19.2-5.18.1 SUSE Linux Enterprise Module for Open Buildservice Development Tools 15 (src): cloud-init-19.2-5.18.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. SUSE-SU-2019:3096-1: An update that solves one vulnerability and has 6 fixes is now available. Category: security (moderate) Bug References: 1099358,1129124,1136440,1142988,1144363,1151488,1154092 CVE References: CVE-2019-0816 Sources used: SUSE Linux Enterprise Module for Public Cloud 15-SP1 (src): cloud-init-19.2-8.11.1 SUSE Linux Enterprise Module for Open Buildservice Development Tools 15-SP1 (src): cloud-init-19.2-8.11.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. Fixed openSUSE-SU-2019:2633-1: An update that solves one vulnerability and has 6 fixes is now available. Category: security (moderate) Bug References: 1099358,1129124,1136440,1142988,1144363,1151488,1154092 CVE References: CVE-2019-0816 Sources used: openSUSE Leap 15.1 (src): cloud-init-19.2-lp151.2.9.1 SUSE-SU-2019:3191-1: An update that solves one vulnerability and has 6 fixes is now available. Category: security (moderate) Bug References: 1099358,1129124,1136440,1142988,1144363,1151488,1154092 CVE References: CVE-2019-0816 Sources used: SUSE Linux Enterprise Module for Public Cloud 12 (src): cloud-init-19.2-37.33.1 SUSE CaaS Platform 3.0 (src): cloud-init-19.2-37.33.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. |