Bug 412449

Summary: Perl Bootloader: Use of uninitialized value in string
Product: [openSUSE] openSUSE 10.3 Reporter: Jorma Hytonen <jorma.hytonen>
Component: YaST2Assignee: Josef Reidinger <jreidinger>
Status: RESOLVED NORESPONSE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P3 - Medium    
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: openSUSE 10.3   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Jorma Hytonen 2008-07-26 06:02:25 UTC
It happens every YaST2 based cron backups.

Before backup starts, root gets email message.
Subject: Cron <root@suse-lnx>  /usr/lib/YaST2/bin/backup_cron "profile=System"
Message: 
Use of uninitialized value in string eq at
	/usr/lib/perl5/vendor_perl/5.8.8/Bootloader/Core/GRUB.pm line 852 (#1)
    (W uninitialized) An undefined value was used as if it were already
    defined.  It was interpreted as a "" or a 0, but maybe it was a mistake.
    To suppress this warning assign a defined value to your variables.

And after backup complete, root gets message:
Subject: YaST Automatic Backup (System)
Mesage:
BACKUP REPORT for Profile System


Summary:
========

Modified Files Found: 48
Total Size: 193.16 kB
Files Not in a Package Found: 14390
Total Size: 648.61 MB
Selected Files to Back Up: 14438


Archive /sdb/backup/system/files.tar created successfully
Autoinstallation profile saved to file /sdb/backup/system/files.xml.

... and so on...
Comment 1 Stephan Kulow 2008-07-26 06:19:04 UTC
how is that major? Maybe I overlook the consequences this has to you, so please explain. Please refer to http://en.opensuse.org/Bugs/Definitions
Comment 2 Jorma Hytonen 2008-07-26 06:40:16 UTC
Ok, I change severity to Normal.
Basically, it slows down backup process several minutes and give extra warnings to check every morning.

All YaST2 profiles:
Cron <root@suse-lnx> /usr/lib/YaST2/bin/backup_cron "profile=Home"
Cron <root@suse-lnx> /usr/lib/YaST2/bin/backup_cron "profile=Srv-www"
Cron <root@suse-lnx>  /usr/lib/YaST2/bin/backup_cron "profile=System"
.. and so on ..
I have five profiles to backup every night.

But in example:
Cron <root@suse-lnx> zypper up -y -t patch  --skip-interactive
Cron <root@suse-lnx> /usr/bin/zrm-pre-scheduler --action backup --backup-set dailyrun --backup-level 0 --interval daily

Those backups give no warnings!
It must be only YaST2 problem?




Comment 3 Cyril Hrubis 2008-07-26 08:56:48 UTC
Please next time remove NEEDINFO status by selecting "This comment/attachment 
provides ..." checkbox after supplying needed information. Reassigning to maintainer.
Comment 4 Josef Reidinger 2008-08-12 06:15:58 UTC
I hope now this problem is fixed, but due to some changes in grub.pm I am not sure, if fix is on this line. Could you please retest it with current perl-Bootloader? thanks
Comment 5 Jorma Hytonen 2008-08-12 09:02:03 UTC
In where I can find this new perl-Bootloader?
I have YaST Automatic Updates on. But "No Updates Available".

Comment 6 Josef Reidinger 2008-08-12 09:37:25 UTC
(In reply to comment #5 from Jorma Hytonen)
> In where I can find this new perl-Bootloader?
> I have YaST Automatic Updates on. But "No Updates Available".
> 

Because new perl-bootloader is not backported to 10.3 you find it in factory.
Comment 7 Josef Reidinger 2008-09-12 12:55:37 UTC
no response for month, if you test new package and it still fail, please reopen
Comment 8 Jorma Hytonen 2008-09-13 09:37:40 UTC
"Because new perl-bootloader is not backported to 10.3 you find it in factory."

--> I can't find any "factory" or "repo" where to update bootloader?



Comment 9 Josef Reidinger 2008-09-16 08:29:26 UTC
factory repository is here: http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/
Comment 10 Josef Reidinger 2008-09-16 10:37:32 UTC
If you try it please, say if it is now fixed. Thanks
Comment 11 Josef Reidinger 2008-10-16 08:31:45 UTC
no response for month