Description of problem: Trying to update host using hammer utility fails on realm. From webui works fine. Version-Release number of selected component (if applicable): rubygem-hammer_cli-0.1.4.13-1.el7sat.noarch How reproducible: Always Steps to Reproduce: 1. Satellite 6.1 with realm configured 2. Try to update host using hammer. # hammer host update --id comp-st-060 --managed yes --hostgroup-id 12 Could not update the host: Failed to create example.com's realm entry: ERF12-5287 [ProxyAPI::ProxyException]: Unable to create realm entry ([RestClient::BadRequest]: 400 Bad Request) for proxy https://satellite.example.com:9090/realm/INT.ACI.ICS.PSU.EDU 3. Language settings on satellite server. # env |grep -i lang LANG=en_US.UTF-8 LANGUAGE= # locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= # runuser - postgres -c "psql -l" List of databases Name | Owner | Encoding | Collate | Ctype | Access privileges ------------+----------+----------+-------------+-------------+------------------------- candlepin | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =T/postgres + | | | | | postgres=CTc/postgres + | | | | | candlepin=CTc/postgres foreman | foreman | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =T/foreman + | | | | | foreman=CTc/foreman gutterball | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =T/postgres + | | | | | postgres=CTc/postgres + | | | | | gutterball=CTc/postgres postgres | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | template0 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres + | | | | | postgres=CTc/postgres template1 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres + | | | | | postgres=CTc/postgres (6 rows) Actual results: host update fails at first attempt Expected results: host should get updated without any error
Connecting redmine issue http://projects.theforeman.org/issues/10581 from this bug
Upstream bug component is Capsule
Created attachment 1188724 [details] /var/log/foreman-proxy/proxy.log
I'm seeing the above attached log from either the UI or CLI. I followed the instructions here for an expired keytab to no avail: http://projects.theforeman.org/projects/foreman/wiki/ERF12-5287
In addition, I noticed the documentation for Foreman 1.12 may be incorrect, or the installer contains a bug: When attempting to install the smart proxy with `foreman-installer --foreman-ipa-authentication=true`, the option I get ``` ERROR: Unrecognised option '--foreman-ipa-authentication' See: 'foreman-installer --help' ```
inecas, this seems like a bug with the smart proxy. If it's not, please reassign me.
Opened a PR upstream to address the encoding issue
Moving to POST since upstream bug http://projects.theforeman.org/issues/10581 has been closed
Build:6.2.2-1.1.el7sat Steps: 1. Configured satellite with REALM 2. Provisioned the host which enrolled into realm 3. Created a host group with non-ascii characters name "žluťoučký" 4. Updated the host group of the host to žluťoučký Host enrolled into realm. [root@kbrhel72mul99k ~]# id admin uid=478000000(admin) gid=478000000(admins) groups=478000000(admins) hammer> hostgroup list ---|---------------|---------------|------------------|-------------|------ ID | NAME | TITLE | OPERATING SYSTEM | ENVIRONMENT | MODEL ---|---------------|---------------|------------------|-------------|------ 1 | rhel7_hstgrp | rhel7_hstgrp | RHEL Server 7.2 | production | 3 | žluťoučký | žluťoučký | RHEL Server 7.2 | production | ---|---------------|---------------|------------------|-------------|------ hammer> host update --id 6 --managed yes --hostgroup-id 3 Host updated Also , the class field in IDM for the host is also updated with new hostgroup name.
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:1885