Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-15777

Editing virt-who configuration fails with error undefined method `update_attributes' for #<ForemanVirtWhoConfigure::Config:0x00007fd5d25bfb58> Did you mean? update_attribute audited_attributes

XMLWordPrintable

    • False
    • Important
    • Sprint 112, Sprint 113
    • None
    • None
    • None
    • None
    • Yes

      Description of problem:

      Existing virt-who configuration cannot be edited and while trying to save it after making changes fail with following error.

      Oops, we're sorry but something went wrong undefined method `update_attributes' for #<ForemanVirtWhoConfigure::Config:0x00007fd5d0c37d98> Did you mean? update_attribute audited_attributes

      Version-Release number of selected component (if applicable): satellite-cli-6.13.0-4.el8sat.noarch

      How reproducible: Always

      Steps to Reproduce:

      1. Navigate to Satellite WebUI -> Infrastructure -> Virt-who configurations -> Create config.

      2. Select 'Hypervisor Type' as 'VMware vSphere / vCenter (esx). Fill all the other basic details and save it.

      3. Navigate to Satellite WebUI -> Infrastructure -> Virt-who configurations -> Click on existing configuration name -> Edit.

      4. Make any changes, for example: select 'Whitelist' in 'Filtering', and add following text in 'Filter hosts' field: *.example.com. Click on 'Submit'.

      Actual results:

      The changes cannot be submitted and below error is displayed on screen.

      Oops, we're sorry but something went wrong undefined method `update_attributes' for #<ForemanVirtWhoConfigure::Config:0x000055bcb06cf0a8> Did you mean? update_attribute audited_attributes

      Expected results:

      The changes should get submitted successfully

              rhn-engineering-lfu Lucy Fu
              jira-bugzilla-migration RH Bugzilla Integration
              yanping liu yanping liu
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: