Bug 1811025

Summary: Some unwanted warning messages dumps(Option --environment-id is deprecated. Use --lifecycle-environment-id instead) while restoring customer database
Product: Red Hat Satellite Reporter: Devendra Singh <desingh>
Component: Satellite CloneAssignee: Chris Roberts <chrobert>
Status: CLOSED ERRATA QA Contact: Vladimír Sedmík <vsedmik>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: chrobert, ehelms, jomitsch
Target Milestone: 6.8.0Keywords: EasyFix, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: satellite-clone-1.5.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 12:38:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Devendra Singh 2020-03-06 13:01:07 UTC
Description of problem: Some unwanted warning messages dumps(Option --environment-id is deprecated. Use --lifecycle-environment-id instead) while restoring customer database


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


How reproducible:
always

Steps to Reproduce:
1. Use a specific customer database to perform satellite clone operation.
2. Satellite-clone started successfully.
3. During Lifecycle environment cleanup we get some unknown option error. 

Actual results:
Warning: Option --environment-id is deprecated. Use --lifecycle-environment-id instead messages dumps in satellite clone while dissociating life cycle environment. 

Expected results:
These warning messages should not come.

Additional info:

There is no impact of satellite restore or upgrade

Comment 9 errata-xmlrpc 2020-10-27 12:38:21 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Satellite 6.8 Satellite Maintenance Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4365