Bug 1217334 - Cannot update lifecycle environment on rhel 66 with GA snap2 installed
Summary: Cannot update lifecycle environment on rhel 66 with GA snap2 installed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.1.0
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: Tazim Kolhar
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-30 07:36 UTC by Tazim Kolhar
Modified: 2017-09-19 17:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 14:00:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
foreman-debug attached (455.73 KB, application/x-xz)
2015-04-30 07:36 UTC, Tazim Kolhar
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 10473 0 None None None 2016-04-22 15:47:39 UTC

Description Tazim Kolhar 2015-04-30 07:36:47 UTC
Created attachment 1020429 [details]
foreman-debug attached

Description of problem:
Cannot update lifecycle environment on rhel 66 with GA snap2 installed

Version-Release number of selected component (if applicable):
 rpm -qa | grep foreman
ruby193-rubygem-foreman_docker-1.2.0.10-1.el6_6sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch
foreman-debug-1.7.2.18-1.el6_6sat.noarch
foreman-vmware-1.7.2.18-1.el6_6sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.6-1.el6_6sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.8-1.el6_6sat.noarch
puppet-foreman_scap_client-0.3.3-8.el6_6sat.noarch
foreman-1.7.2.18-1.el6_6sat.noarch
foreman-libvirt-1.7.2.18-1.el6_6sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.12-1.el6_6sat.noarch
rubygem-hammer_cli_foreman-0.1.4.10-1.el6_6sat.noarch
foreman-postgresql-1.7.2.18-1.el6_6sat.noarch
foreman-selinux-1.7.2.13-1.el6_6sat.noarch
qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-1.0-2.noarch
foreman-compute-1.7.2.18-1.el6_6sat.noarch
foreman-gce-1.7.2.18-1.el6_6sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.12-1.el6_6sat.noarch
foreman-proxy-1.7.2.4-1.el6_6sat.noarch
qe-sat6-rhel66.usersys.redhat.com-foreman-client-1.0-1.noarch
qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-ovirt-1.7.2.18-1.el6_6sat.noarch
ruby193-rubygem-foreman-redhat_access-0.1.0-1.el6_6sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el6_6sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.4-1.el6_6sat.noarch


How reproducible:
everytime

Steps to Reproduce:
1. LANG=en_US.UTF-8 hammer -v -u admin -p changeme --output=csv lifecycle-environment update --id="281" --organization-id="240" --description="ÝÝÒÕÔÐÌûîÃÁíÂÄÒ"
[ERROR 2015-04-30 03:30:38 Exception] Error: At least one of options --prior, --prior-id is required

See: 'hammer lifecycle-environment update --help'
Could not update environment:
  Error: At least one of options --prior, --prior-id is required
  
  See: 'hammer lifecycle-environment update --help'
[ERROR 2015-04-30 03:30:38 Exception] 

Clamp::UsageError (At least one of options --prior, --prior-id is required):
    /usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.4.9/lib/hammer_cli/./apipie/../abstract.rb:37:in `parse'
    /usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/command.rb:66:in `run'
    /usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.4.9/lib/hammer_cli/./apipie/../abstract.rb:23:in `run'
    /usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/subcommand/execution.rb:11:in `execute'
    /usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/command.rb:67:in `run'
    /usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.4.9/lib/hammer_cli/./apipie/../abstract.rb:23:in `run'
    /usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/subcommand/execution.rb:11:in `execute'
    /usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/command.rb:67:in `run'
    /usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.4.9/lib/hammer_cli/./apipie/../abstract.rb:23:in `run'
    /usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/command.rb:125:in `run'
    /usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.4.9/bin/hammer:108
    /usr/bin/hammer:19:in `load'
    /usr/bin/hammer:19



2.
3.

Actual results:
the environment is not updated

Expected results:
the environment is updated

Additional info:
foreman-debug attached

Comment 1 RHEL Program Management 2015-04-30 07:53:18 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Justin Sherrill 2015-05-11 18:34:46 UTC
Created redmine issue http://projects.theforeman.org/issues/10473 from this bug

Comment 4 Bryan Kearney 2015-05-11 22:06:31 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/10473 has been closed
-------------
Justin Sherrill
Applied in changeset commit:hammer-cli-katello|33aea9c57a256301d8bcf65c3a3250622d84afbf.

Comment 7 Tazim Kolhar 2015-05-13 11:33:39 UTC
VERIFIED:

rpm -qa | grep foreman
foreman-postgresql-1.7.2.20-1.el7sat.noarch
foreman-gce-1.7.2.20-1.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.1.0-1.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.11-1.el7sat.noarch
foreman-compute-1.7.2.20-1.el7sat.noarch
ruby193-rubygem-foreman_docker-1.2.0.12-1.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch
foreman-debug-1.7.2.20-1.el7sat.noarch
foreman-selinux-1.7.2.13-1.el7sat.noarch
puppet-foreman_scap_client-0.3.3-8.el7sat.noarch
foreman-1.7.2.20-1.el7sat.noarch
foreman-vmware-1.7.2.20-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.13-1.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch
foreman-proxy-1.7.2.4-1.el7sat.noarch
qe-sat6-rhel71.usersys.redhat.com-foreman-proxy-client-1.0-1.noarch
qe-sat6-rhel71.usersys.redhat.com-foreman-client-1.0-1.noarch
qe-sat6-rhel71.usersys.redhat.com-foreman-proxy-1.0-1.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
rubygem-hammer_cli_foreman_docker-0.0.3.6-1.el7sat.noarch
foreman-libvirt-1.7.2.20-1.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch
foreman-ovirt-1.7.2.20-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.5-1.el7sat.noarch

steps:
#  hammer lifecycle-environment update --name DEV --organization-id 1 --new-name Test
[Foreman] Username: admin
[Foreman] Password for admin: 
Environment updated

]# hammer lifecycle-environment list --name Test --organization-id 1
[Foreman] Username: admin
[Foreman] Password for admin: 
----|------|--------
ID  | NAME | PRIOR  
----|------|--------
450 | Test | Library
----|------|--------

Comment 8 Bryan Kearney 2015-08-11 13:35:13 UTC
This bug is slated to be released with Satellite 6.1.

Comment 9 Bryan Kearney 2015-08-12 14:00:25 UTC
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.


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