Description of problem: When setting up iSCSI on Hosted Engine Deployment, frontend logic doesn't send 'Port' value to the server, causing a python exception. Version-Release number of selected component (if applicable): I don't know how to check cockpit version. I installed the server recently via the ovirt cockpit repo so I assume latest. Maybe this should be made more obvious - I can't figure out how to check. How reproducible: I can't complete an iSCSI install at all, so very. Steps to Reproduce: 1. Create a Hosted Engine Deployment 2. Attempt to deploy via iSCSI 3. No bueno Actual results: No bueno Expected results: iSCSI to work Additional info: I've traced the websocket request as follows: 3:4!294 he_filtered_tokens_vars: ['ADMIN_PASSWORD','APPLIANCE_PASSWORD','ISCSI_PASSWORD','ISCSI_DISCOVER_PASSWORD','ROOTPWD','he_appliance_password','he_admin_password','he_iscsi_password','he_iscsi_discover_password','ansible_ssh_pass'] he_filtered_tokens_re: ['BEGIN PRIVATE KEY(?P<filter>.*)END PRIVATE KEY'] he_iscsi_discover_username: test he_iscsi_portal_addr: 10.0.0.4 he_iscsi_portal_port: he_fqdn: foo.bar.com he_host_name: m1.foo.bar.com Note the port is blank. In ovirt-hosted-engine-setup-ansible-iscsi_discover-20210922205908-bwmaim.log: ERROR ansible failed { "ansible_host": "localhost", "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_result": { "_ansible_no_log": false, "changed": false, "exception": "Traceback (most recent call last):\n File \"/tmp/ansible_ovirt_host_payload_kyy78p57/ansible_ovirt_host_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_host.py\", line 618, in main\nTypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType'\n", Within ovir_host.py, Line 618 is: port=int(iscsi_param.get('port', 3260)), Interestingly, I would assume that line on its own would default to 3260, but apparently it's not, so this may actually be two separate bugs. Browser: Firefox 92 on Ubuntu 20.04 LTS.
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
(In reply to RHEL Program Management from comment #1) > The documentation text flag should only be set after 'doc text' field is > provided. Please provide the documentation text and set the flag to '?' > again. Sorry unsure if that was related to me, if so I don't understand what it means? There should be no change to user documentation as part of this bug if that is what it's referring to.
cockpit-ovirt-dashboard-0.15.1-1.el8.noarch installed as reported by yum
See bug 1964302#c2 *** This bug has been marked as a duplicate of bug 1964302 ***