Bug 117659 - YaST2 Xen setup fails; can't find matching proposal; needs ProductControl::Init() call
Summary: YaST2 Xen setup fails; can't find matching proposal; needs ProductControl::In...
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: RC 1
Hardware: x86-64 All
: P5 - None : Normal
Target Milestone: ---
Assignee: Ladislav Slezák
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-18 04:39 UTC by Charles Duffy
Modified: 2020-09-17 10:21 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
y2logs, per request. (389.38 KB, application/x-gzip)
2005-09-19 16:36 UTC, Charles Duffy 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Charles Duffy 2005-09-18 04:39:01 UTC 
In YaST2, I select "Virtual Machine Installation (Xen)", YaST briefly flashes to
a different screen and returns. Looking at y2log, I note the following:

[YCP] clients/inst_proposal.ycp:503 getting proposals for stage: "normal" mode:
"normal" proposal type: "vm"
[YCP] ProductControl.ycp:553 Stage: normal Mode: normal
[YCP] ProductControl.ycp:604 Proposal modules: nil
[YCP] clients/inst_proposal.ycp:512 No proposals available
[Interpreter] vm/cmdline.ycp:1159 Called YaST client returned: `abort
[Interpreter] clients/menu.ycp:109 Called YaST client returned: `next

This is interesting, because /usr/share/YaST2/control/control.xml quite
certainly contains a proposal for stage normal, mode normal, type vm. None of
the other control.xml paths listed in ProductControl.ycp:Init exist.

However, it appears that Init isn't even being run: there exists no entry in
y2log listing "Candidates: " or showing "Reading control file", so it appears to
me that Init (and thus presumably the ProductControl constructor) isn't even
getting called.

Indeed, ProductControl::Init() is explicitly called only from clients/update.ycp
and clients/autoinst_test_stage.ycp, and adding a call to
clients/inst_proposal.ycp resolves this issue in practice.
Comment 1 Ladislav Slezák 2005-09-19 15:04:10 UTC 
Please, attach full y2log.

It is strange, I have never seen such behaviour, I can start the module without
problems (RC4).
Comment 2 Charles Duffy 2005-09-19 16:36:40 UTC 
Created attachment 50323 [details]
y2logs, per request.

Issue observed in these logs around 2005-09-17 22:15:23; fixed since.
Comment 3 Charles Duffy 2005-10-01 14:18:16 UTC 
Previous comment provided requested info but did not return status to ASSIGNED.
Comment 4 Ladislav Slezák 2006-01-04 14:29:38 UTC 
10.1 version uses it's own control file, ProductControl is initialized correctly.
Comment 5 Wolfgang Bauer 2020-09-17 10:21:09 UTC 
*** Bug 1176669 has been marked as a duplicate of this bug. ***