Project

General

Custom queries

Profile

Actions
Copy link

Bug #30193

closed

installer failed with error "Could not find a suitable provider for foreman_smartproxy" while doing upgrade

Added by Evgeni Golov almost 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Evgeni Golov
Category:
-
Target version:
Foreman - 2.1.0
Difficulty:
Triaged:
No
Bugzilla link:
1846593
Pull request:
https://github.com/theforeman/foreman-installer/pull/527, https://github.com/theforeman/foreman-installer/pull/524, https://github.com/theforeman/foreman-installer/pull/526, https://github.com/theforeman/foreman-installer/pull/528, https://github.com/theforeman/foreman-installer/pull/529, https://github.com/theforeman/foreman-installer/pull/530, https://github.com/theforeman/foreman-installer/pull/531
Fixed in Releases:
Foreman - 2.1.0
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1846593

Description of problem: Satellite-installer failed with error "Could not find a suitable provider for foreman_smartproxy" while doing upgrade from 6.7 to 6.8

Version-Release number of selected component (if applicable):
6.8 Snap4

How reproducible:
always

Steps to Reproduce:
1. Prepared the environment to perform the satellite-upgrade from 6.7 to 6.8
2. Configure all the repository(Enabled the required repository)
3. Execute the pre-check and it has completed successfully.

Actual results:

Satellite-installer failed with Could not find a suitable provider for foreman_smartproxy

Expected results:
Satllite-installer should not be failed.

Additional info:

#1

Updated by Evgeni Golov almost 5 years ago

  • Project changed from Foreman to Installer
  • Subject changed from Satellite-installer failed with error "Could not find a suitable provider for foreman_smartproxy" while doing upgrade from 6.7 to 6.8 to Satellite-installer failed with error "Could not find a suitable provider for foreman_smartproxy" while doing upgrade from 6.7 to 6.8
#2

Updated by The Foreman Bot almost 5 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman-installer/pull/524 added
#3

Updated by The Foreman Bot almost 5 years ago

  • Fixed in Releases 2.2.0 added
#4

Updated by Evgeni Golov almost 5 years ago

  • Status changed from Ready For Testing to Closed
#5

Updated by The Foreman Bot almost 5 years ago

  • Pull request https://github.com/theforeman/foreman-installer/pull/526 added
#6

Updated by The Foreman Bot almost 5 years ago

  • Pull request https://github.com/theforeman/foreman-installer/pull/527 added
#7

Updated by The Foreman Bot almost 5 years ago

  • Pull request https://github.com/theforeman/foreman-installer/pull/528 added
#8

Updated by Tomer Brisker almost 5 years ago

  • Target version set to 2.1.0
#9

Updated by Evgeni Golov almost 5 years ago

  • Fixed in Releases 2.1.0 added
#10

Updated by The Foreman Bot almost 5 years ago

  • Pull request https://github.com/theforeman/foreman-installer/pull/529 added
#11

Updated by Tomer Brisker almost 5 years ago

  • Fixed in Releases deleted (2.2.0)
#12

Updated by Tomer Brisker almost 5 years ago

  • Subject changed from Satellite-installer failed with error "Could not find a suitable provider for foreman_smartproxy" while doing upgrade from 6.7 to 6.8 to installer failed with error "Could not find a suitable provider for foreman_smartproxy" while doing upgrade
#13

Updated by The Foreman Bot almost 5 years ago

  • Pull request https://github.com/theforeman/foreman-installer/pull/530 added
#14

Updated by The Foreman Bot almost 5 years ago

  • Pull request https://github.com/theforeman/foreman-installer/pull/531 added
Actions
Copy link

Also available in: Atom PDF