[yast-devel] Add-on installation on SLES12 SP2
Hi,
OES is an add-on installation on SLES and OES configuration happens in second stage of installation.
On SLES12, I added the OES modules under stage continue,mode installation. So once SLES configuration is done (after finish module) server boots and OES configuration starts, after executing inst_oes_postconfig module, server again reboots.
I just wanted to validate that, is the right approach to follow or do I need to anything differently or do I need to call any other modules after OES configuration is done.
<workflow>
<defaults>
<archs>all</archs>
Hi Suresh, Dne 2.8.2016 v 12:00 Suresh K Hosamani napsal(a):
Hi,
OES is an add-on installation on SLES and OES configuration happens in second stage of installation.
On SLES12, I added the OES modules under stage continue,mode installation. So once SLES configuration is done (after finish module) server boots and OES configuration starts, after executing inst_oes_postconfig module, server again reboots.
In other words, the "inst_oes_congratulate" step is skipped? Then check what the "inst_oes_postconfig" client returns (see the y2log). Maybe it aborts the workflow... Or another idea, the "inst_oes_congratulate" step starts but immediately returns due to some bug. Again, check the y2log.
I just wanted to validate that, is the right approach to follow or do I need to anything differently or do I need to call any other modules after OES configuration is done.
The XML definition looks OK to me and should work. You do not need to call any other YaST modules if you do not need them. Just keep in mind that in SLE12 we dropped the second stage completely in a standard installation and it is used only in AutoYaST mode when needed. (The installation system does not include all YaST modules, some AutoYaST modules need to be started from the installed system later.) That means the second stage might be potentially a bit buggy as we do not use it anymore. We might not notice the regressions easily... HTH Ladislav -- Ladislav Slezák YaST Developer lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Hi Ladislav, Sorry instead of inst_oes_congratulate, I had written as inst_oes_postconfig. Is it ok to introduce second stage for OES configuration ? or do the OES configuration in first stage itself ? Regards, Suresh
Ladislav Slezak
8/4/16 7:02 PM >>> Hi Suresh,
Dne 2.8.2016 v 12:00 Suresh K Hosamani napsal(a):
Hi,
OES is an add-on installation on SLES and OES configuration happens in second stage of installation.
On SLES12, I added the OES modules under stage continue,mode installation. So once SLES configuration is done (after finish module) server boots and OES configuration starts, after executing inst_oes_postconfig module, server again reboots.
In other words, the "inst_oes_congratulate" step is skipped? Then check what the "inst_oes_postconfig" client returns (see the y2log). Maybe it aborts the workflow... Or another idea, the "inst_oes_congratulate" step starts but immediately returns due to some bug. Again, check the y2log.
I just wanted to validate that, is the right approach to follow or do I need to anything differently or do I need to call any other modules after OES configuration is done.
The XML definition looks OK to me and should work. You do not need to call any other YaST modules if you do not need them. Just keep in mind that in SLE12 we dropped the second stage completely in a standard installation and it is used only in AutoYaST mode when needed. (The installation system does not include all YaST modules, some AutoYaST modules need to be started from the installed system later.) That means the second stage might be potentially a bit buggy as we do not use it anymore. We might not notice the regressions easily... HTH Ladislav -- Ladislav Slezák YaST Developer lslezak@suse.com SUSE
Hi Suresh, Dne 5.8.2016 v 07:22 Suresh K Hosamani napsal(a):
Is it ok to introduce second stage for OES configuration ? or do the OES configuration in first stage itself ?
If you really need the second stage then it is OK to add it and use it. But if you could configure OES from the first stage then it should be preferred. The advantages of the first stage config are: - the configuration is done in a single run, that's convenient for users and compatible with plain SLES - you do not need to boot the installed system, this makes preparing disk images easier - allows smaller system footprint, it allows installing a minimal system even without YaST included Disadvantages: - the inst-sys (or the y2update.tgz in your case) needs to contain all needed configuration tools and scripts, if you need to run some big programs to configure OES the inst-sys might become too big and might not work with minimal hardware (512MB RAM for SLES, I do not know the OES minimal requirements) - be careful when running external tools or writing to files, the target system is mounted at /mnt not at / (if you use YaST SCR it works transparently) - a bit more difficult development and debugging [1], developing and testing in inst-sys is more complex, a virtual machine helps a lot So in my opinion if you do not need to run big tools or something very tricky I'd prefer the first stage configuration. Ladislav [1] But now we have a debugger in SP2, see http://yastgithubio.readthedocs.io/en/latest/debugging/ -- Ladislav Slezák YaST Developer lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Hi,
I was trying to add few debug statement using Report.Error statement in proposal_store.rb, it fails with below error
yast/wfm.rb:222 Client call failed with 'uninitialized constant Installation::ProposalStore::YaST' and backtrace ["/usr/share/YaST2/lib/installation/proposal_store.rb:46:in `initialize'", "/usr/share/YaST2/lib/installation/proposal_runner.rb:84:in `new'", "/usr/share/YaST2/lib/installation/proposal_runner.rb:84:in `run'", "/usr/share/YaST2/lib/installation/proposal_runner.rb:38:in `run'", "/usr/share/YaST2/clients/inst_proposal.rb:24:in `
On Monday, August 8, 2016 6:16:12 AM WEST Suresh K Hosamani wrote:
Hi,
Hi Suresh,
I was trying to add few debug statement using Report.Error statement in proposal_store.rb, it fails with below error
yast/wfm.rb:222 Client call failed with 'uninitialized constant Installation::ProposalStore::YaST' and backtrace ["/usr/share/YaST2/lib/installation/proposal_store.rb:46:in `initialize'", "/usr/share/YaST2/lib/installation/proposal_runner.rb:84:in `new'", "/usr/share/YaST2/lib/installation/proposal_runner.rb:84:in `run'", "/usr/share/YaST2/lib/installation/proposal_runner.rb:38:in `run'", "/usr/share/YaST2/clients/inst_proposal.rb:24:in `
'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:209:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:209:in `run_client'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:185:in `call_builtin'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:185:in `call_builtin_wrapper'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:178:in `CallFunction'", "/usr/share/YaST2/modules/ProductControl.rb:1360:in `RunFrom'", "/usr/share/YaST2/modules/ProductControl.rb:1547:in `Run'", "/usr/share/YaST2/modules/OesAddOnProduct.rb:1144:in `DoInstall_WithControlFile'", "/usr/share/YaST2/modules/OesAddOnProduct.rb:1346:in `DoInstall'", "/usr/share/YaST2/clients/oes-install.rb:48:in `main'", "/usr/share/YaST2/clients/oes-install.rb:83:in ` '", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:209:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:209:in `run_client'"] code is def initialize(proposal_mode) Yast.import "Mode" Yast.import "ProductControl" Yast.import "Stage" Yast.import "Report" textdomain "installation"
@proposal_mode = proposal_mode YaST::Report.Error("yes")
You should change YaST::Report for Yast::Report.
end Any thing missing ?
I hope it helps. Regards, Imo -- Imobach González Sosa YaST team at SUSE LINUX GmbH
participants (3)
-
Imobach González Sosa
-
Ladislav Slezak
-
Suresh K Hosamani