QA » openQA Project » openQA Tests

Talked with Jiri:
Hi,

the default depends on the scenario and possibly also on the product
(e.g. for JeOS you do not want to install soft dependencies, you only
want a minimal system).

With scenario I mean: When you do update, you may intentionally want to
disable recommends - because then even if a recommended package was
explicitly uninstalled before, it would get in because it is recommended
by newer version of some package which gets upgraded.

I would need to search for details, but yes, for some scenarios the
default is changed and that behavior is correct.

Jiri

On 13. 12. 18 9:49, yutao wrote:

Hi Jiri,

Add one information: The 'Install Recommended Packages' doesn't select
by default. Only happened at sled12sp4 migration to sled15sp1.
sled15GA migration to sled15sp1, the 'Install Recommended Packages'
still be selected by default.

On 12/12/2018 06:15 PM, Jiri Srain wrote:

Hi Yutao,

I don't understand where the problem is, even the test case source
describes what it should do:

--- snip ---

     # Given that package is not installed,
     # uncheck Dependencies/Install Recommended Packages,
     # select the package, verify that recommended package is NOT

selected

--- snap ---

So, when you first select yast2-nfs-client, the recommended nfs-client
package gets selected, then you disable selecting recommended packages
and it gets unselected.
Yes, I agree this is correct behave.
Background Info: If 'Install Recommended Packages' is selected, first
select yast2-nfs-client, the recommended nfs-client package gets
selected automatically.
My question is: The 'Install Recommended Packages' would be selected by
default before, but now the 'Install Recommended Packages' doesn't
select by default. Is this change expected? Why change it?
Because all of our openQA cases based on 'Install Recommended Packages'
is selected by default. If 'Install Recommended Packages' doesn't
select by default, we should change our case. If you can confirm this
change is expected, then we will update our case.

Thanks and BRs,
Yutao

That is exactly how it should behave.

Jiri

On 12. 12. 18 10:46, yutao wrote:

Hi Jiri,

I checked the case, if choose 'Install Recommended Packages', then

'nfs-client' should be recommended automatically.Please check the
attachment.
As 'Install Recommended Packages' be selected by default, the
'nfs-client' should be recommended.

My question is: 'Install Recommended Packages' be selected by

default now or not? All of our openqa cases, use 'Install Recommended
Packages' be selected by default scenario.

I checked 'Migration from sled12sp3 to 15sp1', 'nfs-client' can be

recommended.
Related case: https://openqa.suse.de/tests/1772456#step/yast2_i/12

BRs,

On 12/12/2018 05:23 PM, Jiri Srain wrote:

Hi Yutao,

On 12. 12. 18 10:02, yutao wrote:

Hi Jiri,

My description has some problem. My meaning is the 'nfs-client'
doesn't get recommended.
The expected result like the attachment file.
Now it doesn't have 'a+' before 'nfs-client'.
According fate: https://fate.suse.com/318099
It should "get Recommended dependencies of that package"
I don't understand you. There are two types of dependencies:

Hard (usually Requires) means that if you select yast2-nfs-client, it
would select nfs-client (the way it is shown in your screenshot with
that 'a+'

Soft dependencies (Recommends) are different; you can have the solver
configured so that recommended packages are automatically selected, or
so that the Recommends dependencies are ignored (note that with more
recent libzypp, which is on the way to the distro now, there are even
more configuration options).

Since there is only a soft dependency (Recommends), whether the package
gets pre-selected depends on how your solver is configured - based on
that, either selecting or ignoring the dependency is a correct behabior.

Jiri

BRs,

On 12/12/2018 04:50 PM, Jiri Srain wrote:

Hi Yutao,

the behavior is correct. The YaST module only recommends the nfs-client
package, therefore it should or should not be selected based on your
system settings.

When you only install the YaST module and start it, it should ask you to
install additional packages.

This behavior is intentional; you need the YaST module e.g. to crete an
AutoYaST profile, but for that you don't need the underlying service.
This allows to have smaller system installed.

Hope that this information helps,
Jiri

On 12. 12. 18 7:46, yutao wrote:

Hi Jiri,

I have one problem about yast2 to install packages.
My test steps:

1. Install base system SLED12SP4
2. Offline migration with media.
3. Upgrade to sled15sp1: basesytem+WE+Desktop After migration, login sled15sp1 system:
4. zypper -n -i rm yast2-nfs-client nfs-client
5. yast2 sw_single
6. At 'Search Phrase' type string: 'yast2-nfs-client' and selected this package
7. At 'Search Phrase' type string: 'nfs-client' Expected result: 'nfs-client' should be selected as it has dependency with 'yast2-nfs-client' Actually result: 'nfs-client' didn't be selected. Please check the attachment screenshot. Related test case: https://openqa.suse.de/tests/2318980#step/yast2_i/12

Could you please confirm is it a bug about yast?

Thanks and BRs,
Yutao

Verified on o.s.d. https://openqa.suse.de/tests/2340422