Description of problem: When deploying an env I'm getting a failure at Validate connections of storages task with Operation Failed. Fault detail is "[Cannot edit Storage Connection. Storage connection 78042880-d660-4f07-a046-9b3fdd7c247e already exists for .]". SDs are added successfully from the previous task and there should be nothing wrong with the storages themselves, the hosts in this env can see all the luns without issues. Version-Release number of selected component (if applicable): ovirt.vm-infra (1.2.3) How reproducible: always Steps to Reproduce: 1. setup an env with iscsi storages 2. 3. Actual results: fails to validate Expected results: validation should pass when all SD are added successfully Additional info: can provide multiple envs where this is happening, either talk to me or pkubica
Blocking new servers installation and thus only couple new envs.
Lowering severity, as we are able to verify this flow on different HW.
Issue is caused by our new storage server in a combination of wrong tries to update storage connection during oVirt Infra role prerequisites: - storage has multiple different (target) iqns on the same IP - role is adding iSCSI storage domains from this storage what happens: - in a playbook there is mentioned only one target iqn for the storage domain, after iscsi discovery there are multiple portals with a different iqn - in a validation step, it tries to update the storage domain connections - it sees that there is a different target iqn and it tries to update the connection but there already exists a connection with this target So it's necessary to check existing connections and don't try to update a connections to a different already existing connection
Role installed from galaxy and it doesn't try to change connection to wrong target verified on ovirt.ovirt:1.4.2
This bugzilla is included in oVirt 4.4.6 release, published on May 4th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.6 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.