Bug 556110

Custom service show what you have configured in the config file, /etc/webyast/custom_services.yml.

If there is one service, it will show one service.
If there are more, show more of them.


So, the question is, if we should provide example custom_services.yml just like we are doing it now? Or should we provide empty file, and show an info that no service is defined?

Created attachment 328069 [details]
screenshot

We could show something like this.

(In reply to comment #2)

> We could show something like this.

This is quite general message, however, the technical details are described in the README files, so I think they do not belong here...

Solution of comment #2 is fine.

The main bug currently is that 'system services' and 'custom service' both show _all_ services. There is no visible difference.

(Inclusion of system services in RC2 was a bug, this has been fixed meanwhile. So only custom services will be available)

Sorry, but one more needinfo, to make it clear.

(In reply to comment #4)
> Solution of comment #2 is fine.
> 
> The main bug currently is that 'system services' and 'custom service' both show
> _all_ services. There is no visible difference.
>
> (Inclusion of system services in RC2 was a bug, this has been fixed meanwhile.
> So only custom services will be available)

Uh, do I understand it right, that the orginal report is invalid? (The bug _is_ vs. inclusion _was_)

(If it still happens, this is relevant:

What is actually "RC2"? I'm testing Signed_WebYaST_on_SLES11-0.12.0 image and here I only see those 2 preconfigured services.

What URL do you have after clicking Custom Service? Is "custom=1" parameter there?)


I assume that the answer for comment 1 is  that we should _not_ provide any pre-defined services as example: Martin, could you remove that custom_services.xml?

(In reply to comment #5)
> I assume that the answer for comment 1 is  that we should _not_ provide any
> pre-defined services as example: Martin, could you remove that
> custom_services.xml?

Removed from both appliances on iStudio: [Signed_]WebYaST_on_SLES11

(In reply to comment #6)
> (In reply to comment #5)
> > I assume that the answer for comment 1 is  that we should _not_ provide any
> > pre-defined services as example: Martin, could you remove that
> > custom_services.xml?
> 
> Removed from both appliances on iStudio: [Signed_]WebYaST_on_SLES11

Err, why is it  custom_services.XML and not  custom_services.YML ? Or is it a typo ?

In any case, I'd suggest to leave the  custom_services file in but with services commented out. Then its much easier for vendors to understand the file's contents

(In reply to comment #5)
> 
> Uh, do I understand it right, that the orginal report is invalid? (The bug _is_
> vs. inclusion _was_)

Its two bugs

1. system services included in webyast for appliances. This is fixed.
2. system services and custom service showing exactly the same output, namely full list of all services. And, yes, 'custom=1' is shown in the url.

> 
> (If it still happens, this is relevant:
> 
> What is actually "RC2"? I'm testing Signed_WebYaST_on_SLES11-0.12.0 image and
> here I only see those 2 preconfigured services.

It's 'git master' on opensuse 11.2 

> 
> What URL do you have after clicking Custom Service? Is "custom=1" parameter
> there?)

Yes.

(In reply to comment #7)

> > > custom_services.xml?
> > 
> > Removed from both appliances on iStudio: [Signed_]WebYaST_on_SLES11
> 
> Err, why is it  custom_services.XML and not  custom_services.YML ? Or is it a
> typo ?

Typo.

(In reply to comment #8)

> It's 'git master' on opensuse 11.2 

Than I assume it is fixable by using latest yast2 package (from svn).

(In reply to comment #4)
> Solution of comment #2 is fine.

yast2-webclient-services-0.0.12