[sisuite-users] RE : beta7 bug fixed = beta8 WAS: systemimager 4.3.0-0.7 available for testing
hi David,
Thanks a lot for your report.
Thanks also for the patch. It is not yet integrated because I want to have a
deterministic way of managing firmwares. I don't want to end in a situation
when errors occure because guy A had installed a package and guy B didn't.
I think that the best way for the moment is to add command line switch to
include system installed firmwares . By this way, the user will known that the
problem can come from a missing firmware.
For the L switch, I understand that it is needed for the firmware sync, but
this triggers some problems elsewhere were files a copied twice instead of
having a link and a file.
using L switch is a quick hack but the image gets even bigger (already very
big).
I'm aware of both issues, and I'll find a solution.
The freeze problem is more problematic. Did you try without using LVM? If it
works, then it may be a bad lvm tools build (using system libs instead of
initrd built libs. I tryed to fix most of them, but lvm may be one of them.
Best regards,
PS: Right now, I'm working on debian systemimager oscar-packager. I'll be back
soon.
Olivier.
--
Olivier LAHAYE
CEA DRT/LIST/DCSI/DIR
De : david.livingst...@cn.ca [david.livingst...@cn.ca]
Date d'envoi : mercredi 17 avril 2013 23:31
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] beta7 bug fixed = beta8 WAS: systemimager
4.3.0-0.7 available for testing
Olivier,
Finally had a chance to test from a client running beta8 to a server running
beta8. Both client and server are running rhel 6.4 x86_64.
- I prepared the images as both uyok and without and both worked. No problem
with the getimage from the server.
- I then attempted to load the client with the image I had created. I attempted
this with both the standard kernel and the uyok.
Both worked up to the point in the script when lvcreate was executed. At this
point the load/system would hang(reset required).
See the log below. To restore I loaded from a server running a slightly older
version( systemimager-server-4.3.0-0.2.el6.noarch)
which did not have this problem.
Also note for reasons I have stated in the past I also modified
UseYourOwnKernel.pm as follows :
[root@wild1 130408]# diff
/usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm UseYourOwnKernel.pm
152c152
$cmd = qq(rsync -a --exclude=build --exclude=source ) .
---
$cmd = qq(rsync -aL --exclude=build --exclude=source ) .
159c159
$cmd = qq(rsync -aR $module $staging_dir);
---
$cmd = qq(rsync -aLR $module $staging_dir);
222a223,233
#
# Copy /lib/firmware file to initrd
#
#
if (-d /lib/firmware) {
# copy firmware tree to new initrd.
$cmd = qq(rsync -aLR /lib/firmware $staging_dir);
!system( $cmd ) or die( Couldn't $cmd. );
}
Log of failed boot :
parted -s -- /dev/sda set 2 lvm on
logger: logger: parted /dev/sda set 2 lvm on
New partition table for /dev/sda:
parted -s -- /dev/sda print
Model: HP LOGICAL VOLUME (scsi)
Disk /dev/sda: 300GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End SizeType File system Flags
1 512B1000MB 1000MB primary boot
2 1000MB 300GB 299GB primary lvm
Load software RAID modules.
Load device mapper driver (for LVM).
Initializing partition /dev/sda2 for use by LVM.
pvcreate -M2 -ff -y /dev/sda2 || shellout
WARNING: Forcing physical volume creation on /dev/sda2 of volume group rootvg
Physical volume /dev/sda2 successfully created
lvremove -f /dev/rootvg /dev/null 21 vgremove rootvg /dev/null 21
vgcreate -M2 -l 0 -p 0 -s 32768K rootvg /dev/sda2 || shellout
Volume group rootvg successfully created
lvcreate -L16777216K -n LogVol01 rootvg || shellout
David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Walker Operations East Building
Edmonton, AB, T5E 0B9
Ph : 780 472-3959 Fax : 780 472-3046
Email: david.livingst...@cn.ca
- Forwarded by David Livingstone/LIVING03/CNR/CA on 2013/04/17 15:14 -
From: david.livingst...@cn.ca
To: sisuite-users@lists.sourceforge.net
Date: 2013/04/10 15:56
Subject:Re: [sisuite-users] beta7 bug fixed = beta8 WAS: systemimager
4.3.0-0.7 available for testing
Olivier,
Thanks. That does it. I still need to test loading the image. I will let you
know.
David
David K Livingstone
CN Signals and Communications
From: LAHAYE Olivier olivier.lah...@cea.fr
To: sisuite-users@lists.sourceforge.net
sisuite-users@lists.sourceforge.net
Date: 2013/04/08 06:37
Subject:[sisuite-users] beta7 bug fixed = beta8 WAS: systemimager
4.3.0-0.7 available for testing
Hi,
The issue has been fixed.
I wonder how it could work on V0.2. There were 2 bugs:
One
[sisuite-users] RE : beta7 bug fixed = beta8 WAS: systemimager 4.3.0-0.7 available for testing
Cool, Thanks for the report, hopefully, the deployment will succeed. Note, that you must setup network and bootloader using a post install script. I've fixed grub1, but grub2 is not supported and NetworkManger is not supported as well. Regards, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR De : david.livingst...@cn.ca [david.livingst...@cn.ca] Date d'envoi : mercredi 10 avril 2013 23:56 À : sisuite-users@lists.sourceforge.net Objet : Re: [sisuite-users] beta7 bug fixed = beta8 WAS: systemimager 4.3.0-0.7 available for testing Olivier, Thanks. That does it. I still need to test loading the image. I will let you know. David David K Livingstone CN Signals and Communications From: LAHAYE Olivier olivier.lah...@cea.fr To: sisuite-users@lists.sourceforge.net sisuite-users@lists.sourceforge.net Date: 2013/04/08 06:37 Subject:[sisuite-users] beta7 bug fixed = beta8 WAS: systemimager 4.3.0-0.7 available for testing Hi, The issue has been fixed. I wonder how it could work on V0.2. There were 2 bugs: One that I introduced when I wanted to match kernel 3.x kernels with x 2 But there was also a bug in initrd detection. the routine was unable to check for initramfs files. If no initrd file was available, the error should have triggered as well Anyway, It's hopefully fixed and should be available shortly for fedora, rhel-6 and debian-7-x86_64 soon here: http://svn.oscar.openclustergroup.org/repos/unstable/ The source rpm (and tarball) will be available here soon as well: http://svn.oscar.openclustergroup.org/pkgs/downloads/ -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR De : LAHAYE Olivier Date d'envoi : lundi 8 avril 2013 09:24 À : sisuite-users@lists.sourceforge.net Objet : RE : [sisuite-users] systemimager 4.3.0-0.7 available for testing Hi, Thanks a lot for this report, I'll try to understand the issue ASAP. 0.2 has the same code as 0.7 (differences are on the initrd and boot packages which are very different). Regards, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR De : david.livingst...@cn.ca [david.livingst...@cn.ca] Date d'envoi : samedi 6 avril 2013 00:44 À : sisuite-users@lists.sourceforge.net Objet : Re: [sisuite-users] systemimager 4.3.0-0.7 available for testing Olivier, I installed on a rhel 6.4 client and get the below error message when attempting to prepare the client. If I install 4.3.0-0.2 this does not happen. systemimager-common-4.3.0-0.7.el6.noarch systemimager-x86_64initrd_template-4.3.0-0.7.el6.noarch systemimager-client-4.3.0-0.7.el6.noarch - same error on vccs3 using --no-uyok and without - We get : - [root@mtl-vccs03d ~]# si_prepareclient --no-uyok --server 165.115.83.125 ... This client is ready to have its image retrieved. You must now run the si_getimage command on your imageserver. Automatically create configuration file for systemconfigurator: /etc/systemconfig/systemconfig.conf WARNING: unable to auto-detect kernel file! WARNING: coulnd't create file /etc/systemconfig/systemconfig.conf (needed by systemconfigurator) [root@mtl-vccs03d ~]# David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 Email: david.livingst...@cn.ca - Forwarded by David Livingstone/LIVING03/CNR/CA on 2013/04/05 16:40 - From: David Livingstone/LIVING03/CNR/CA To: sisuite-users@lists.sourceforge.net Date: 2013/03/21 11:40 Subject:Re: [sisuite-users] systemimager 4.3.0-0.7 available for testing Olivier, Thanks ! I will download and test on rhel 6.x). BTW I am currently using your previous build(4.3.0-0.2 std kernel only) on rhel 6.x with the restrictions we have corresponded about. David David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 Email: david.livingst...@cn.ca From: LAHAYE Olivier olivier.lah...@cea.fr To: sisuite-users@lists.sourceforge.net sisuite-users@lists.sourceforge.net Date: 2013/03/20 10:17 Subject:[sisuite-users] systemimager 4.3.0-0.7 available for testing Hi, I've uploaded the rpms for systemimager beta version V4.3.0 (beta7) I've built it for fedora-17 and centos-6.3 They are available here: http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/ Note that you can install the oscar-release rpm which will setup the yum.repo.d/oscar.repo. Usage notes: - The pre install script required to modprobe disk controlers is not required anymore. (leave comments in it) - the post install scripts (si_scripts.tar.bz2http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2
