Bug #21178
closed
unable to set non-primary remote execution interface
Added by Ivan Necas about 7 years ago.
Updated over 6 years ago.
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1498028
Description of problem:
In satellite web UI, editing host that has multiple interfaces, when enabling rex on an interface that is not primary, the change is not applied after saving. This happens when adding an interface to an existing host as well as provisioning a host with multiple interfaces.
How reproducible:
always
Steps to Reproduce:
1. Host > Edit > Interfaces > Add interface
2. Check "Remote Execution", confirm you want to change it in the pop-up dialog
3. Click OK and submit
4. Edit the host again to view the interfaces, interface you just created is not set as rex, primary interface has rex enabled
Expected results:
Rex interface can be changed without complications
Additional info:
Noticed when trying to reproduce https://bugzilla.redhat.com/show_bug.cgi?id=1417074
- Status changed from New to Ready For Testing
- Assignee set to Ivan Necas
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/275 added
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/276 added
- Related to Bug #21176: Plugin#parameter_filter doesn't work properly with block argument added
- Related to deleted (Bug #21176: Plugin#parameter_filter doesn't work properly with block argument)
- Blocked by Bug #21176: Plugin#parameter_filter doesn't work properly with block argument added
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Subject changed from unable to set non-primary remote execution interface
to unable to set non-primary remote execution interface
- Pull request deleted (
https://github.com/theforeman/foreman_remote_execution/pull/275)
- Translation missing: en.field_release set to 317
Also available in: Atom
PDF