-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not run the same thing again in second firstrun wizard #20212
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO that's the wrong approach.
If it's not possible to fix the testing to avoid running the firstboot wizard twice, it should be made much more explicit which "stage" it is running instead of just doing the same things twice.
f73283c
to
a46883a
Compare
Added a setting then. |
Can't we just use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest fixing the schedule so that the module is not executed on the children.
I tried, but seems some key steps are missing to run next modules |
Technically yes - but IMO it makes sense to test jeos-firstboot on the actual target hardware. |
https://progress.opensuse.org/issues/166175
Verification run