|
Bugzilla – Full Text Bug Listing |
| Summary: | networking problems using cloud-init in leap 15.1 images | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE.org | Reporter: | Carsten Hoeger <choeger> |
| Component: | 3rd party software | Assignee: | Robert Schweikert <rjschwei> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <bnc-team-screening> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | alynx.zhou, choeger, prometheoid, rjschwei |
| Version: | unspecified | Flags: | rjschwei:
needinfo?
(choeger) |
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
/var/log/cloud-init.log
systemd-analyze plot on leap 15.1 systemd-analyze plot on leap 42.3 |
||
|
Description
Carsten Hoeger
2019-07-26 09:23:04 UTC
Maybe related (I am not a cloud-init expert): systemd-analyze plot shows that wicked.service is started after cloud-config.target in 15.1 while it is started before cloud-config.target in 42.3. Created attachment 811768 [details]
systemd-analyze plot on leap 15.1
Created attachment 811769 [details]
systemd-analyze plot on leap 42.3
Any chance to get this fixed? Recent images still show the same issue. Dealing with the same issue, using Tumbleweed image from https://download.opensuse.org/tumbleweed/appliances/openSUSE-Tumbleweed-JeOS.x86_64-OpenStack-Cloud.qcow2 to spin up a DigitalOcean VM. I've pushed a few wicked/cloud-init units around using guestfish and haven't been able to resolve the problem yet. 2019-07-26 09:16:02,657 - stages.py[ERROR]: Unable to render networking. Network config is likely broken: No available network renderers found. Searched through list: ['eni', 'sysconfig', 'netplan'] Indicates that ifup/ifdown was not found and cloud-init could not determine in which format the network configuration should be written. Since cloud-init cannot write the network configuration networking cannot work if there is no default device configuration, such as ifcfg-eth0 built in. This is independent of the ordering. In 19.2 currently in Cloud:Tools the order of unit files is modified. However this does not fix the issue w.r.t. cloud-init not being able to write the network configuration to begin with. https://github.com/cloud-init/cloud-init/blob/02c8214eac857e29b40ecc65992c1da6983083e1/cloudinit/net/sysconfig.py#L745-L758 These lines contain directories that don't exist in the cloud image - could be the availability check that's failing. Trying to identify whether there are suitable symlinks that could fill the void. Should be fixed with the latest version in CLoud:Tools cloud-init 19.2, can someone please test and confirm? Hello, Robert thank you so much for this - It did not fix the problem, unfortunately. I think I've tracked the issue down. There was a change here -> https://github.com/cloud-init/cloud-init/commit/0948cdfbef2052cdf839f24d6a17d457aa9fd4d3#diff-b3309b48873bd17b3fc8f29bd84c50fa that does not appear to be in the opensuse version. "opensuse-tumbleweed" and "opensuse-leap" (which are returned from the get_linux_distro method) are not in the KNOWN_DISTROS dictionary. Instead the system_info method from that package needs to be used. Thanks so much for all your help, and the excellent work you do maintaining this package for opensuse. (to be clear I think the change you made shortcircuiting with ifup/ifdown was necessary, especially since those hardcoded paths are still in the most recent commit of cloud-init https://github.com/cloud-init/cloud-init/blob/02c8214eac857e29b40ecc65992c1da6983083e1/cloudinit/net/sysconfig.py , it just also needs the changes from that diff) Thanks for spotting this, yes we need another change in the package. The condition is an "and" thus since currently "available_sysconfig() always returns False it wouldn't matter even if the first part of the check is correct, grmbl. This will take me a little bit. OK, the next build in Cloud:Tools should fix the issue. Another quick test? Thanks (In reply to Robert Schweikert from comment #12) > OK, the next build in Cloud:Tools should fix the issue. > > Another quick test? > > Thanks By jove it works! Thanks so much for this, was going to give up but I'm so glad I get to use opensuse for this project now. If anyone else needs to get this working fast, grab the qcow2 cloud image, install libguestfs (command for opensuse host) $ sudo zypper in libguestfs run $ virt-customize -a <path_to_qcow2_file> --run-command 'zypper --non-interactive addrepo -C https://download.opensuse.org/repositories/Cloud:Tools/openSUSE_Tumbleweed/Cloud:Tools.repo' --run-command 'zypper --gpg-auto-import-keys refresh' --install cloud-init-19.2-6.1.x86_64 Thanks again Robert This is an autogenerated message for OBS integration: This bug (1142988) was mentioned in https://build.opensuse.org/request/show/741941 Factory / cloud-init Yes, cloud-init is now working, thanks. Yes, cloud-init is now working, 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. 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. |