Bug 1386524 - undefined method `openscap_proxy_id_changed?'
Summary: undefined method `openscap_proxy_id_changed?'
Keywords:
Status: CLOSED DUPLICATE of bug 1363806
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SCAP Plugin
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-19 08:00 UTC by Stephen Wadeley
Modified: 2016-10-19 11:44 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-19 11:44:34 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Stephen Wadeley 2016-10-19 08:00:11 UTC 
Description of problem:

Customer portal member states the entered:

satellite-installer --scenario satellite --upgrade

and saw:

undefined method `openscap_proxy_id_changed?' for #<Host::Managed:0x0000000a99e3a0>/opt/rh/rh-ror41/root/usr/share/gems/gems/activemodel-4.1.5/lib/active_model/attribute_methods.rb:435:in `method_missing'


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

To be confirmed, but should be 6.1.10 when the command was entered if the procedure was followed correctly.


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

reporter applied: http://projects.theforeman.org/projects/foreman_openscap/repository/revisions/a2a74842a14295e03c365205df17a5ea61e28356/diff/

  differences manually and re-run the installer again.

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-6-upgrading-satellite-server-and-capsule-server#comment-1110061
Comment 2 Marek Hulan 2016-10-19 11:44:34 UTC 
Thanks for the report Stephen. I believe this is already tracked as bz 1363806, please continue with eventual further questions there.

*** This bug has been marked as a duplicate of bug 1363806 ***
Note You need to log in before you can comment on or make changes to this bug.