Project

General

Profile

Bug #20749

hammer content-view filter rule create does not properly set the architecture

Added by Brad Buckingham about 4 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Category:
Hammer
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

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

Description of problem:
when creating a filter rule, the architecture information is not passed to katello

setting sev: high as that might have interesting results on the clients

Version-Release number of selected component (if applicable):
tfm-rubygem-hammer_cli_foreman-0.10.2-1.el7sat.noarch
tfm-rubygem-hammer_cli-0.10.2-1.el7sat.noarch
tfm-rubygem-hammer_cli_katello-0.10.0-1.el7sat.noarch

How reproducible:
100%

Steps to Reproduce:
1. create a filter with name=foo, arch=x86_64, version=1234
hammer content-view filter rule create --content-view-filter-id 3 --name foo --arch x86_64 --version 1234

Actual results:
The created rule has no architecture set (according to the WebUI)

Expected results:
The created rule has an architecture set

Additional info:

Associated revisions

Revision a4942f1b (diff)
Added by Brad Buckingham about 4 years ago

fixes #20749 - cv filter rule - fix apidoc for architecture

The apidoc lists 'arch'; however, it needs to be
'architecture' to allow the user to set it via
hammer-cli-katello.

History

#1 Updated by Brad Buckingham about 4 years ago

  • Subject changed from hammer content-view filter rule create does not properly set the architecture to hammer content-view filter rule create does not properly set the architecture
  • Status changed from New to Assigned
  • Target version set to 208

#2 Updated by The Foreman Bot about 4 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/6925 added

#3 Updated by Brad Buckingham about 4 years ago

  • Target version changed from 208 to 213

#4 Updated by Brad Buckingham about 4 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#5 Updated by John Mitsch about 4 years ago

  • Legacy Backlogs Release (now unused) set to 250

Also available in: Atom PDF