Skip to content
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

Fix nil factory #691

Merged
merged 2 commits into from
Jan 11, 2024
Merged

Fix nil factory #691

merged 2 commits into from
Jan 11, 2024

Conversation

jreidinger
Copy link
Member

Problem

insts-sys does not have sysconfig for bootloader. The code first try to get bootloader name from system and then translate it to object. Sadly that name is not checked if it is defined and it result in unnecessary error in yast logs.

Solution

Check if bootloader name is defined and if not, then just return nil to activate condition at https://github.com/yast/yast-bootloader/blob/master/src/lib/bootloader/bootloader_factory.rb#L42 to use proposed bootloader instead.

Testing

  • Tested manually ( official SP6 medium and yupdate from this branch and then on proposal screen check yast logs that it does not contain /tmp/var/log/YaST2/y2log-2.gz:2023-12-16 06:53:34 <3> install(4251) [Ruby] bootloader/bootloader_factory.rb(bootloader_by_name):84 Factory receive nil name

@jreidinger jreidinger changed the base branch from master to SLE-15-SP6 January 10, 2024 23:25
Copy link
Contributor

@shundhammer shundhammer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jreidinger jreidinger merged commit a964b05 into SLE-15-SP6 Jan 11, 2024
6 checks passed
@jreidinger jreidinger deleted the fix_nil_factory branch January 11, 2024 09:59
@yast-bot
Copy link
Contributor

✔️ Internal Jenkins job #3 successfully finished
✔️ Created IBS submit request #317617

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants