|
Bugzilla – Full Text Bug Listing |
| Summary: | autoyast-initscripts execute with stage2 disabled | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Karl Vanden Bogaert <karl.vandenbogaert> |
| Component: | AutoYaST | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED NORESPONSE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | igonzalezsosa, kanderssen, karl.vandenbogaert |
| Version: | Leap 15.5 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Karl Vanden Bogaert
2023-07-18 07:09:19 UTC
There is the second stage of the installation, and there is the optional firstboot workflow. Are you sure you saw the second stage, not firstboot? no I'm indeed talking about second stage, not "first boot" :-) If you set the second stage to false in your control file, the autoyast-initscripts.service don't care and starts at 1st boot. Then you are stuck. Why are you stuck when no custom sripts need to be executed is probably the real question... :-) Imo, please have a look at this. It looks like a bug and would be nice to have logs from an installation where it happens as it is documented by: https://en.opensuse.org/openSUSE:Report_a_YaST_bug Could you attach them? Still waiting for feedback; see comment #4. I've created a very minimal AY profile with second_stage=false and it worked in Leap 15.5 for me. So, the isssue might be caused by something specific in your profile. However, we cannot proceed without yast logs (see comment#4). Your AY profile would be also nice (don't forget to shadow sensitive info if you have any in the profile). If you don't provide the info, we will have to close the bug. No feedback. Closing. |