Bug 1525428 - setup sm channels with one shot
Summary: setup sm channels with one shot
Keywords:
Status: CLOSED DUPLICATE of bug 1525163
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-fast-forward-upgrade
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Sandro Bonazzola
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-13 10:23 UTC by Jiri Belka
Modified: 2017-12-13 10:54 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-13 10:54:48 UTC
oVirt Team: Integration
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1366900 0 urgent CLOSED [RFE] - Support direct to version upgrade of the manager 2021-02-22 00:41:40 UTC

Internal Links: 1366900

Description Jiri Belka 2017-12-13 10:23:09 UTC
Description of problem:

SM is super slow tool, and this wrapper is adding additional delay while executing for each repo to add individual SM commands:

...
[ INFO  ] Executing: env LC_ALL=C subscription-manager repos --enable rhel-7-server-rhv-4.1-rpms
Repository 'rhel-7-server-rhv-4.1-rpms' is enabled for this system.
[ INFO  ] Enabling repository: rhel-7-server-rhv-4-tools-rpms
[ INFO  ] Executing: env LC_ALL=C subscription-manager repos --enable rhel-7-server-rhv-4-tools-rpms
...

Version-Release number of selected component (if applicable):
ovirt-engine-hyper-upgrade-1.0.0-3.el7ev.noarch.rpm

How reproducible:
100%

Steps to Reproduce:
1. run the command
2.
3.

Actual results:
it makes executing SM for enabling each repo individually

Expected results:
it should enable repos in one shot as SM is super slow

Additional info:

Comment 1 Sandro Bonazzola 2017-12-13 10:54:48 UTC
Looks like a duplicate of bug #1525163

*** This bug has been marked as a duplicate of bug 1525163 ***


Note You need to log in before you can comment on or make changes to this bug.