Project

General

Profile

Bug #31384

hammer os list fails with default organization set

Added by yifat makias over 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:
In Kanboard:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1649011

Description of problem:
When a default organization is set `hammer os list` returns "Association not found for organization. Removing the organization default results in the OS list returning.

Version-Release number of selected component (if applicable): 6.4.0-15

How reproducible:
Always

Steps to Reproduce:
1. Execute `hammer defaults add --param-name organization_id --param-value 1
2. Execute `hammer os list`

Actual results:
Command returns with "Association not found for organization"

Expected results:
List of operating systems:
ID,TITLE,RELEASE NAME,FAMILY
1,RedHat 7.4,,Redhat

Additional info:
The expected result is returned if the default organization id is removed; however, this results in a change in behavior from 6.2.15, the previous release we used. Alternatively, if there is an argument to pass to hammer to either specify an organization-id of null or to ignore defaults.yml, it would allow us to avoid significantly rewriting our deployment automation.


Related issues

Related to Foreman - Bug #32695: API has inconsistent behavior with taxable parametersClosed

Associated revisions

Revision 28331a3d (diff)
Added by Yifat Makias about 2 years ago

Fixes #31384 - fix hammer list failure when defaults are set (#551)

History

#1 Updated by yifat makias over 2 years ago

  • Assignee set to yifat makias
  • Status changed from New to Assigned
  • Category deleted (19)

#2 Updated by The Foreman Bot over 2 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/8155 added

#3 Updated by yifat makias over 2 years ago

  • Status changed from Ready For Testing to Assigned
  • Project changed from Foreman to Hammer CLI
  • Pull request deleted (https://github.com/theforeman/foreman/pull/8155)

#4 Updated by The Foreman Bot over 2 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/hammer-cli-foreman/pull/551 added

#5 Updated by The Foreman Bot about 2 years ago

  • Fixed in Releases hammer-cli-foreman-2.4.0 added

#6 Updated by Anonymous about 2 years ago

  • Status changed from Ready For Testing to Closed

#7 Updated by Oleh Fedorenko almost 2 years ago

  • Related to Bug #32695: API has inconsistent behavior with taxable parameters added

Also available in: Atom PDF