Bugs item #790891, was opened at 2003-08-18 19:39 Message generated for change (Comment added) made by mchasal You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109368&aid=790891&group_id=9368
Category: Installation Group: 2.2.1 >Status: Closed >Resolution: Duplicate >Priority: 5 Submitted By: Benoit des Ligneris (bligneri) >Assigned to: Michael Chase-Salerno (mchasal) Summary: SIS mkautoinstallscript problem Initial Comment: >From [EMAIL PROTECTED] Mon Aug 18 17:51:18 2003 From: Bernard Li <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: [Oscar-users] OSCAR install (static_dhcp) Date: Mon, 18 Aug 2003 14:45:09 -0700 Hi group: I have finally installed OSCAR on our cluster and I would like to share my findings. There is a bug in v2.2.1 where if you choose 'static_dhcp' when you build the clients, the mkautoinstallscript will fail. One solution is to run the mkautoinstallscript with the correct argument 'dhcp' instead of 'static_dhcp' but I found out later that this solution is incomplete, as it does not address running the post_rpm_install script. Therefore, my solution is to choose 'static' instead, build the image and then manually modify the script to make it 'dhcp'. The file to edit is /var/lib/systemimager/scripts/<imagename>.master: You want to remove the line with $GATEWAY and also change 'static' to 'dhcp' and remove the $IP_ADDRESS and the $SUBNET_MASK settings. After that you should be in business. If you recall our problem with ssh - this was because the post_rpm_install script never got run, and this is where it runs the SSH install and keygen and also the propagation of the keys to the clients. Thanks for all your help and I'll continue to try to integrate Oscar to our system! ---------------------------------------------------------------------- >Comment By: Michael Chase-Salerno (mchasal) Date: 2003-08-19 09:27 Message: Logged In: YES user_id=99742 This was fixed a while ago and this bug is a dupe of #717912 https://sourceforge.net/tracker/index.php?func=detail&aid=717912&group_id=9368&atid=109368 Also the release manager is the only person who should set a bug's priority to 9. This indicates that the bug has been accepted during CVS closure. If you think a bug is a showstopper, you should set it to priority 8 (unless you are the RM) so the RM can consider it for approval. ---------------------------------------------------------------------- Comment By: Benoit des Ligneris (bligneri) Date: 2003-08-18 19:40 Message: Logged In: YES user_id=179120 Can someone try to reproduce this bug on 2.3b6 ? If this bug still exists I think this is really a showtopper and either the options should be removed from the wizard or the big fixed... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109368&aid=790891&group_id=9368 ------------------------------------------------------- This SF.net email is sponsored by Dice.com. Did you know that Dice has over 25,000 tech jobs available today? From careers in IT to Engineering to Tech Sales, Dice has tech jobs from the best hiring companies. http://www.dice.com/index.epl?rel_code=104 _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
