dustymabe added a new comment to an issue you are following: `` ok since this problem was introduced in the f28 stream I decided to run an [rpm-ostree bisect]() to see where it first started happening. The results probably won't surprise you:
``` Starting RPM-OSTree Bisect Testing... : Using data file at: /var/lib/rpm-ostree-bisect.json : Did not find device timeout. Test Passes : Removed /etc/systemd/system/multi-user.target.wants/rpm-ostree-bisect.service. : BISECT TEST RESULTS: : Last known good commit: : 5736e83 : 28.20180708.0 : 2018-07-08T20:03:31Z : First known bad commit: : bc3aa17 : 28.20180711.0 : 2018-07-11T18:26:22Z : libostree pull from 'fedora-atomic' for fedora/28/x86_64/atomic-host complete security: GPG: commit http: TLS non-delta: meta: 270 content: 0 transfer: secs: 43 size: 2.7 MB : ostree diff commit old: 5736e832b1fd59208465458265136fbe2aa4ba89517d8bdcc91bc84724f40a8e : ostree diff commit new: bc3aa17a5ad6c04103563bd93c4c668996ef786ec04f989a3209a9887c8e982c : Upgraded: : acl 2.2.52-20.fc28 -> 2.2.53-1.fc28 : attr 2.4.47-23.fc28 -> 2.4.48-1.fc28 : dracut 047-8.git20180305.fc28 -> 048-1.fc28 : dracut-config-generic 047-8.git20180305.fc28 -> 048-1.fc28 : dracut-network 047-8.git20180305.fc28 -> 048-1.fc28 : kernel 4.17.3-200.fc28 -> 4.17.4-200.fc28 : kernel-core 4.17.3-200.fc28 -> 4.17.4-200.fc28 : kernel-modules 4.17.3-200.fc28 -> 4.17.4-200.fc28 : libacl 2.2.52-20.fc28 -> 2.2.53-1.fc28 : libattr 2.4.47-23.fc28 -> 2.4.48-1.fc28 : openldap 2.4.46-1.fc28 -> 2.4.46-2.fc28 : podman 0.6.5-1.git9d97bd6.fc28 -> 0.7.1-1.git802d4f2.fc28 : python3-pytoml 0.1.16-1.fc28 -> 0.1.17-1.fc28 : Removed: : grubby-8.40-11.fc28.x86_64 : Added: : libkcapi-1.1.1-1.fc28.x86_64 : libkcapi-hmaccalc-1.1.1-1.fc28.x86_64 Started RPM-OSTree Bisect Testing.
```
So with everything we've learned so far the problem is in the code in the dracut-network rpm and introduced in dracut `048`. Also the smoking gun seems to be somewhere in the iscsi module because when `iscsi-initiator-utils` isn't installed we don't have the problem. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/513