Hide Forgot
Description of problem: hammer docker registry update lacks options for organization/location association. For other entities such as medium, domain, subnet, compute-resource these options exist. For docker registries the only way is to use UI. Version-Release number of selected component (if applicable): @sat6.2.0-Beta-Snap8 tfm-rubygem-hammer_cli_foreman_docker-0.0.4-1.el7sat.noarch How reproducible: always Steps to Reproduce: 1. # hammer docker registry update -h | grep -e location-ids -e locations -e organization-ids -e organizations Actual results: CLI: unable to associate docker registry with locations and organizations Expected results: CLI: docker registry update subcommand has similar options as other entities have for organization and location association
Missing options: --location-ids LOCATION_IDS REPLACE locations with given ids --locations LOCATION_NAMES Comma separated list of values. --organization-ids ORGANIZATION_IDS REPLACE organizations with given ids. --organizations ORGANIZATION_NAMES Comma separated list of values.
Created redmine issue http://projects.theforeman.org/issues/14703 from this bug
Upstream bug component is Container Management
Moving to POST since upstream bug http://projects.theforeman.org/issues/14703 has been closed ------------- Daniel Lobato Garcia Applied in changeset commit:foreman-docker|c1cbf3bd157d557241a524c39823ed7aff148248.
Verified with 6.2 GA SNAP 13 [vagrant@sat-test-rhel7 ~]$ hammer docker registry update -h | grep -e location-ids -e locations -e organization-ids -e organizations --location-ids LOCATION_IDS REPLACE locations with given ids --locations LOCATION_NAMES Comma separated list of values. --organization-ids ORGANIZATION_IDS REPLACE organizations with given ids. --organizations ORGANIZATION_NAMES Comma separated list of values.
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:1501