Bug 1223391

Summary: [Build 6.39] wicked.service: Found ordering cycle on jeos-firstboot.service/start
Product: [openSUSE] PUBLIC SUSE Linux Enterprise Server 15 SP6 Reporter: Martin Loviska <mloviska>
Component: Minimal-VMAssignee: Fabian Vogt <fvogt>
Status: RESOLVED FIXED QA Contact: Gustavo Yokoyama Ribeiro <gyribeiro>
Severity: Normal    
Priority: P2 - High CC: bbrunner, fvogt, mchang, pdostal, rjschwei, rtsvetkov
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Other   
URL: https://openqa.suse.de/tests/14104996/modules/journal_check/steps/2
Whiteboard:
Found By: openQA Services Priority:
Business Priority: Blocker: Yes
Marketing QA Status: --- IT Deployment: ---
Attachments: journal

Description Martin Loviska 2024-04-25 11:55:40 UTC 
Created attachment 874498 [details]
journal

## Observation

openQA test in scenario sle-15-SP6-JeOS-for-VMware-x86_64-jeos-main-cloud-init@svirt-vmware70 fails in
[journal_check](https://openqa.suse.de/tests/14104996/modules/journal_check/steps/2)

Journal scan reports a following service ordering cycle error messages. The issue occurs on vmware image when the image is configured by cloud-init instead of jeos-firstboot.

Apr 21 13:52:27.905781 localhost systemd[1]: wicked.service: Found ordering cycle on jeos-firstboot.service/start
Apr 21 13:52:27.905786 localhost systemd[1]: wicked.service: Found dependency on cloud-config.target/start
Apr 21 13:52:27.905791 localhost systemd[1]: wicked.service: Found dependency on cloud-init.service/start
Apr 21 13:52:28.229105 localhost systemd[1]: Started Journal Service.
Apr 21 13:52:27.905795 localhost systemd[1]: wicked.service: Found dependency on wicked.service/start
Apr 21 13:52:27.905799 localhost systemd[1]: wicked.service: Job jeos-firstboot.service/start deleted to break ordering cycle starting with wicked.service/start

This report might be a consequence of https://bugzilla.suse.com/show_bug.cgi?id=1221132


## Reproducible

Fails since (at least) Build [4.18](https://openqa.suse.de/tests/13350794)


## Expected result

Last good: (unknown) (or more recent)


## Further details

Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=JeOS-for-VMware&machine=svirt-vmware70&test=jeos-main-cloud-init&version=15-SP6)
Comment 1 Radoslav Tzvetkov 2024-04-26 08:49:08 UTC 
Hi Gustavo, could you please look at what is the impact of this? I've looked at the priority of this as P2. Please correct it if needed. Is this important for the GMC?
Comment 2 Robert Schweikert 2024-04-29 11:59:42 UTC 
The problem can be seen here:

https://github.com/openSUSE/jeos-firstboot/blob/master/files/usr/lib/systemd/system/jeos-firstboot.service

jeos-firstboot wants to start before wicked.service but after cloud-init.target. But cloud-init.service, which is part of cloud-init.target needs to start after wicked.service.

Assigning to Fabian.
Comment 4 Robert Schweikert 2024-04-30 20:12:05 UTC 
https://github.com/openSUSE/jeos-firstboot/pull/123
Comment 5 Radoslav Tzvetkov 2024-05-02 09:46:33 UTC 
Who can make an SR for SP6 here?
Comment 6 Fabian Vogt 2024-05-06 11:40:11 UTC 
(In reply to Radoslav Tzvetkov from comment #5)
> Who can make an SR for SP6 here?

https://build.suse.de/request/show/328921
Comment 7 OBSbugzilla Bot 2024-05-06 12:15:03 UTC 
This is an autogenerated message for OBS integration:
This bug (1223391) was mentioned in
https://build.opensuse.org/request/show/1172157 Factory / jeos-firstboot