Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1324598

Summary: hammer content view promote failed
Product: Red Hat Satellite Reporter: sthirugn <sthirugn>
Component: WebUIAssignee: Zach Huntington-Meath <zhunting>
Status: CLOSED ERRATA QA Contact: Roman Plevka <rplevka>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, jyejare, mmccune, rplevka
Target Milestone: UnspecifiedKeywords: PrioBumpQA, Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/14538
Whiteboard:
Fixed In Version: rubygem-hammer_cli_katello-0.0.22.6-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 09:08:07 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:
Bug Depends On:    
Bug Blocks: 1286523    

Description sthirugn@redhat.com 2016-04-06 18:01:51 UTC
Description of problem:
hammer subscription upload timeouts

Version-Release number of selected component (if applicable):
Satellite 6.2.0-beta-snap2.1

How reproducible:
Always

Steps to Reproduce:
hammer> content-view version promote --content-view='rhel7cv' --organization-id=1 --to-lifecycle-environment='QE' --asyncCould not promote the content view:
  Error: found more than one lifecycle_environment


hammer> content-view version promote --content-view='rhel7cv' --organization-id=1 --to-lifecycle-environment-id=2
Could not promote the content view:
  Error: found more than one lifecycle_environment

hammer> content-view version promote --content-view='rhel7cv' --organization-id=1 --to-lifecycle-environment='QE' --from-lifecycle-environment='Library'
Could not promote the content view:
  Error: found more than one lifecycle_environment


Actual results:
Error as shown above

Expected results:
No error and successful promotion

Additional info:

Comment 2 sthirugn@redhat.com 2016-04-06 18:32:44 UTC
Also in the same box, hammer activation-key create failed:

hammer> activation-key create --name=testak1 --organization-id=3
Could not create the activation key:
  Error: found more than one lifecycle_environment

Note: please make sure to have multiple lifecycle environments

Comment 3 sthirugn@redhat.com 2016-04-06 18:41:27 UTC
For Comment 2, I got the following error in hammer debug mode:

[ERROR 2016-04-06 14:40:00 Exception] Error: found more than one lifecycle_environment
Could not create the activation key:
  Error: found more than one lifecycle_environment
[ERROR 2016-04-06 14:40:00 Exception] 

HammerCLIForeman::ResolverError (found more than one lifecycle_environment):
    /opt/theforeman/tfm/root/usr/share/gems/gems/hammer_cli_foreman-0.5.1.3/lib/hammer_cli_foreman/id_resolver.rb:209:in `pick_result'
    /opt/theforeman/tfm/root/usr/share/gems/gems/hammer_cli_foreman-0.5.1.3/lib/hammer_cli_foreman/id_resolver.rb:168:in `find_resource'
    /opt/theforeman/tfm/root/usr/share/gems/gems/hammer_cli_foreman-0.5.1.3/lib/hammer_cli_foreman/id_resolver.rb:143:in `get_id'
    /opt/theforeman/tfm/root/usr/share/gems/gems/hammer_cli_foreman-0.5.1.3/lib/hammer_cli_foreman/id_resolver.rb:133:in `block (2 levels) in define_id_finders'
    /opt/theforeman/tfm/root/usr/share/gems/gems/hammer_cli_katello-0.0.22.5/lib/hammer_cli_katello/id_resolver.rb:52:in `environment_id'
    /opt/theforeman/tfm/root/usr/share/gems/gems/hammer_cli_foreman-0.5.1.3/lib/hammer_cli_foreman/commands.rb:153:in `get_resource_id'
    /opt/theforeman/tfm/root/usr/share/gems/gems/hammer_cli_foreman-0.5.1.3/lib/hammer_cli_foreman/commands.rb:222:in `block in customized_options'
    /opt/theforeman/tfm/root/usr/share/gems/gems/hammer_cli_foreman-0.5.1.3/lib/hammer_cli_foreman/commands.rb:219:in `each'
    /opt/theforeman/tfm/root/usr/share/gems/gems/hammer_cli_foreman-0.5.1.3/lib/hammer_cli_foreman/commands.rb:219:in `customized_options'
    /opt/theforeman/tfm/root/usr/share/gems/gems/hammer_cli_foreman-0.5.1.3/lib/hammer_cli_foreman/commands.rb:243:in `request_params'
    /opt/theforeman/tfm/root/usr/share/gems/gems/hammer_cli-0.5.1.4/lib/hammer_cli/apipie/command.rb:43:in `send_request'
    /opt/theforeman/tfm/root/usr/share/gems/gems/hammer_cli_foreman-0.5.1.3/lib/hammer_cli_foreman/commands.rb:189:in `send_request'
    /opt/theforeman/tfm/root/usr/share/gems/gems/hammer_cli-0.5.1.4/lib/hammer_cli/apipie/command.rb:34:in `execute'
    /opt/theforeman/tfm/root/usr/share/gems/gems/clamp-1.0.0/lib/clamp/command.rb:68:in `run'
    /opt/theforeman/tfm/root/usr/share/gems/gems/hammer_cli-0.5.1.4/lib/hammer_cli/abstract.rb:22:in `run'
    /opt/theforeman/tfm/root/usr/share/gems/gems/clamp-1.0.0/lib/clamp/subcommand/execution.rb:11:in `execute'
    /opt/theforeman/tfm/root/usr/share/gems/gems/clamp-1.0.0/lib/clamp/command.rb:68:in `run'
    /opt/theforeman/tfm/root/usr/share/gems/gems/hammer_cli-0.5.1.4/lib/hammer_cli/abstract.rb:22:in `run'
    /opt/theforeman/tfm/root/usr/share/gems/gems/clamp-1.0.0/lib/clamp/subcommand/execution.rb:11:in `execute'
    /opt/theforeman/tfm/root/usr/share/gems/gems/clamp-1.0.0/lib/clamp/command.rb:68:in `run'
    /opt/theforeman/tfm/root/usr/share/gems/gems/hammer_cli-0.5.1.4/lib/hammer_cli/abstract.rb:22:in `run'
    /opt/theforeman/tfm/root/usr/share/gems/gems/clamp-1.0.0/lib/clamp/command.rb:133:in `run'
    /opt/theforeman/tfm/root/usr/share/gems/gems/hammer_cli-0.5.1.4/bin/hammer:125:in `<top (required)>'
    /usr/bin/hammer:23:in `load'
    /usr/bin/hammer:23:in `<main>'

Comment 4 Zach Huntington-Meath 2016-04-07 21:17:16 UTC
Created redmine issue http://projects.theforeman.org/issues/14538 from this bug

Comment 5 Bryan Kearney 2016-04-07 22:13:33 UTC
Upstream bug component is WebUI

Comment 6 Jitendra Yejare 2016-04-12 13:42:11 UTC
I hit the same issue of multiple environments while attempting hammer repository list.

#hammer repository list --organization-id 1
Error: found more than one lifecycle_environment

Comment 8 Roman Plevka 2016-04-18 15:16:53 UTC
VERIFIED
sat 6.2.0 snap 8.2

hammer> content-view version promote --content-view='rhel7cv' --organization-id=1 --to-lifecycle-environment='QE' --async
Content view is being promoted with task 54f9fc4f-48d6-420c-968d-474fe8205bce


hammer> repository list --organization-id 1
---|-----------|--------|- -|-----------------------------------------------
ID | NAME | PRODUCT | CONTENT TYPE | URL   
---|-----------|--------|---|-----------------------------------------------
7  | Satellite 6 Tools        | satellite-beta   | yum | http://<hostname>/pulp/repos/Sat6-CI/QA/Tools_RH...
6  | Satellite 6 Capsule      | satellite-beta   | yum | http://<hostname>/pulp/repos/Sat6-CI/QA/Capsule

Comment 10 errata-xmlrpc 2016-07-27 09:08:07 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, 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-2016:1500