action #11460

Feature 320494: Disable installation source after installation if we register system

Added by maritawerner about 4 years ago. Updated over 3 years ago.

Status:ResolvedStart date:01/04/2016
Priority:UrgentDue date:
Assignee:michalnowak% Done:

0%

Category:-
Target version:openQA Project - Milestone 3
Difficulty:
Duration:

Description

For details see https://fate.suse.com/320494

First check if the Feature status is "done".

Related issues

Related to openQA Tests - action #11708: Add-on installation: review zypper_lr testcase Resolved 25/04/2016

History

#1 Updated by dgutu about 4 years ago

  • Assignee set to dgutu

#2 Updated by RBrownSUSE almost 4 years ago

  • Target version set to 168

#3 Updated by okurz almost 4 years ago

  • Target version changed from 168 to Milestone 3

#4 Updated by RBrownSUSE over 3 years ago

  • Priority changed from Normal to Urgent

#5 Updated by dgutu over 3 years ago

  • Related to action #11708: Add-on installation: review zypper_lr testcase added

#6 Updated by okurz over 3 years ago

  • Description updated (diff)

feature is done. Remove copy-paste content. Better to refer to fate entry itself which also has a testcase.

#7 Updated by okurz over 3 years ago

  • Status changed from New to In Progress
  • Assignee changed from dgutu to michalnowak

Current state: Feature test: PASSED

@michalnowak: This has been covered by you already in the zypper_lr test but I could not find a scenario on osd where registration to (proxy-)SCC is done during installation and an addon is added using a medium, i.e. "Test case #3: registered system + not registered addon" in https://fate.suse.com/320494
I confirmed it looks correct in a local test I did: http://lord.arch/tests/2667#step/zypper_lr/1 but I am not sure wether this is done on osd or if zypper_lr already checks for this. Can you clarify?

#8 Updated by michalnowak over 3 years ago

  • Status changed from In Progress to Resolved

Closing.

Also available in: Atom PDF