http://bugzilla.suse.com/show_bug.cgi?id=1155545 http://bugzilla.suse.com/show_bug.cgi?id=1155545#c23 --- Comment #23 from Fabian Vogt <fvogt@suse.com> --- (In reply to Ancor Gonzalez Sosa from comment #20)

(In reply to Fabian Vogt from comment #19)

...

...

4) But instead of fixing the buggy environment (that was the premise, "difference in environments should be neglegible, anything else is a bug in the environment") we end up with a bunch of bug reports about thing we have to adapt in the YaST side for it to work in this new environment. That was not the deal.

First of all, let me clarify something. I talked about "buggy environment" as a direct application of your own sentence: "anything else is a bug in the environment". As far as I understood that sentence, it means that if something works in the normal official installation but it does not work in the live media, it ought to be considered a bug in the live media itself, not in YaST.

If it's something that can be fixed in the environment, yes. Like /etc/install.inf contents or YaST calling "extend" for feature checks, etc.

...

Please tell me which bugs in the environment you're talking about here, to my knowledge there aren't any open ones.

Let's perform a very quick search to find some bugs about something being broken in the live media, although it works in the normal int-sys (there are many more examples... including several ones that has been fixed in the YaST side):

- bug#1151291

Yup - this was clearly caused by a major difference in the environment and discussed earlier. Arguably YaST should avoid to modify the outside system's /run, that might cause issues in the inst-sys as well.

- bug#1151148

Cannot possibly be fixed in the environment, it only worked at all because the inst-sys doesn't have an rpm database. IMO a YaST bug which the live installer uncovered.

- bug#1089823

I opened this report after debugging the issue and fixing the environment. It's about YaST completely ignoring the failure of snapper during installation, no matter the environment.

- bug#1059298

That bug didn't really have much to do with YaST - it did exactly what it was supposed to. A workaround/fix filtering out the unexpected cmdline entries was added to live-net-installer.

- bug#1155516

That's actually a dup of boo#993885 - long known, not that nice to fix, but harmless.

- bug#1155687

I haven't seen that one yet - seems to be more fallout from the /run bind-mount. Fixed live-net-installer is building currently.

- bug#1157686

That happened in the inst-sys as well - the entire snapshot was broken.

None of those are a problem when the installer runs in the official int-sys, which is the environment for which we develop and test the installer. The problems only arise when executed in that different environment that is the live media. That's why I dared to call them "bugs in the environment" as a direct application of the rule above.

Looking at the kind of bugs listed above, the fixes (excluding the network one, which was a known topic back when the live installer was introduced, but didn't cause any fatal issues except for an empty dialog until recently) are mostly just relatively small. So the main blocker here is that it's simply not tested before the full TW snapshot openQA, leading to the for you more frustrating reports of severe regressions. So having it tested continuously would improve this situation quite a bit for everyone involved here AFAICT. That should be doable. It's on my ToDo list already to test (JeOS, MicroOS, Live)-Images in stagings already for a while.

All those bugs are currently assigned to yast2-maintainers. So you can say they are not bugs in the environment, but things the YaST Team should fix by modifying YaST. But, as said, that was not the deal.

Yes - please CC/Assign me if such bugs end up assigned to you and seem to be caused by the environment. (In reply to Ancor Gonzalez Sosa from comment #21)

(In reply to Ancor Gonzalez Sosa from comment #20)

...

All those bugs are currently assigned to yast2-maintainers. So you can say they are not bugs in the environment, but things the YaST Team should fix by modifying YaST. But, as said, that was not the deal.

Just to clarify my words once more. The YaST Team wants to continue being supportive with the idea of running the net installer on top of live media. It's indeed a neat initiative.

But "being supportive" has meant, so far:

- allocating resources only when other priorities allow it - doing only changes that don't risk the supported scenarios - making no commitment about keeping it working in the future

We simply fear the expectations on us has changed recently (little by little) without we having been part of any conversation about it.

It's easier to explain: Until recently, the live installer worked really well, so that the sudden failures were more noticeable and unexpected :-) -- You are receiving this mail because: You are on the CC list for the bug.