Description of problem: Running comman `hammer organization` shows warning of deprecated environments feature Version-Release number of selected component (if applicable): tfm-rubygem-hammer_cli-0.17.1-2.el7sat.noarch How reproducible: always Steps to Reproduce: 1. hammer organization >/dev/null 2. 3. Actual results: Warning: Option --environments is deprecated. Use --puppet-environments instead Warning: Option --environment-ids is deprecated. Use --puppet-environment-ids instead Expected results: no warnings Additional info: # hammer environment >/dev/null environment command is deprecated and will be removed in one of the future versions. Please use puppet-environment command instead.
Created redmine issue https://projects.theforeman.org/issues/27778 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27778 has been resolved.
ON_QA Verified @Satellite 6.7.0 snap 3.0 Steps/Observation: - `hammer organization` does not show warning of deprecated environments feature - warning shows only under help text for options '--environment/--environment-id'. ___________________________________________________________ [root@qe-sat6-feature-rhel7 ~]# hammer organization Usage: hammer organization [OPTIONS] SUBCOMMAND [ARG] ... Parameters: SUBCOMMAND Subcommand [ARG] ... Subcommand arguments Subcommands: add-compute-resource Associate a compute resource add-config-template Associate a configuration template add-domain Associate a domain add-environment Associate a Puppet environment add-hostgroup Associate a hostgroup add-location Associate a location add-medium Associate a medium add-smart-proxy Associate a smart proxy add-subnet Associate a subnet add-user Associate an user create Create organization delete Delete an organization delete-parameter Delete parameter for an organization info Show organization list List all organizations remove-compute-resource Disassociate a compute resource remove-config-template Disassociate a configuration template remove-domain Disassociate a domain remove-environment Disassociate a Puppet environment remove-hostgroup Disassociate a hostgroup remove-location Disassociate a location remove-medium Disassociate a medium remove-smart-proxy Disassociate a smart proxy remove-subnet Disassociate a subnet remove-user Disassociate an user set-parameter Create or update parameter for an organization update Update organization Options: -h, --help Print help [root@qe-sat6-feature-rhel7 ~]# hammer organization >/dev/null [root@qe-sat6-feature-rhel7 ~]# [root@qe-sat6-feature-rhel7 ~]# hammer content-view version update --help Usage: hammer content-view version update [OPTIONS] Options: --content-view CONTENT_VIEW_NAME Content view name to search by --content-view-id CONTENT_VIEW_ID Content view numeric identifier --description DESCRIPTION The description for the content view version --environment ENVIRONMENT_NAME Lifecycle environment name to search by (--environment is deprecated: Use --lifecycle-environment instead) --environment-id ENVIRONMENT_ID (--environment-id is deprecated: Use --lifecycle-environment-id instead) --id ID Content view version identifier --lifecycle-environment LIFECYCLE_ENVIRONMENT_NAME Lifecycle environment name to search by --lifecycle-environment-id LIFECYCLE_ENVIRONMENT_ID --new-version NEW_VERSION --organization ORGANIZATION_NAME Organization name to search by --organization-id ORGANIZATION_ID Organization ID --organization-label ORGANIZATION_LABEL Organization label to search by --version VERSION Content view version number -h, --help Print help [root@qe-sat6-feature-rhel7 ~]# [root@qe-sat6-feature-rhel7 ~]# hammer host update --help|grep 'environment' --environment ENVIRONMENT_NAME Environment name (--environment is deprecated: Use --puppet-environment instead) --environment-id ENVIRONMENT_ID (--environment-id is deprecated: Use --puppet-environment-id instead) ___________________________________________________________
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, 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:1455