|
Bugzilla – Full Text Bug Listing |
| Summary: | JeOS OpenStack image fails to start - systemd-firstboot seems to be executed instead of cloud-init | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Paul Gonin <paul.gonin> |
| Component: | Basesystem | Assignee: | Guilherme Moro <gmoro> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P3 - Medium | CC: | fbui, lnussel |
| Version: | Leap 42.3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Paul Gonin
2017-06-26 09:46:32 UTC
I've no idea how this is supposed to work with openstack but the fact that systemd-firstboot is started instead of cloud-init doesn't mean that systemd-firstboot has an issue. Chenzi what's your rational here ? I agree, I don't think it is a systemd issue rather an issue with the kiwi definition afaik the JeOS team intentionally uses systemd-firstboot. The use of cloud-init would require the presence of a cloud.cfg file and the service activation as part of the image description. But this is in the hands of the JeOS team @Anja could you have a look on the openstack description and check why things are configured as they are. For openstack use cloud-init makes a lot sense, otherwise one would need to implement their own way of accessing the cloud provider services supported by cloud-init on LSE JeOS images for OpenStack cloud-init is used instead of systemd-firstboot (because there is usually no console access to cloud servers) This is a known bug that is fixed in the SLE version of the system, the merge of the internal version of the kiwi templates to leap is coming soon, will fix a lot of problems. Thanks for the report. I merged the templates from SLE again. should be fixed, please verify. |