Greg Perry

Just ran into the same error and the same fix worked for me. Thanks for posting the work around @SuperQ !

Could we please get an explanation for the `200` ? Using 200 in my dashboard results in CPU ready percentages over 100% so i'm guessing it shouldn't be left as...

I am now successfully installing this module using my fixes. I am pointing at my forked branch to install (not sure if it's a requirement in the `imports` or not...

FWIW I use MAAS to deploy ESXi 7.0 without issues. Does your ESXi system being deployed have connectivity on the network? Might also want to ensure it has valid DNS...

I had hoped it was that simple but maybe not.... I'm not sure if there's a way to verify a pool was `init`ed already or not so I just re-ran...

- NVMEoF ``` 2024-02-25 14:37:18] INFO grpc.py:75: NVMeoF gateway Git repository: https://github.com/ceph/ceph-nvmeof [2024-02-25 14:37:18] INFO grpc.py:78: NVMeoF gateway Git branch: tags/1.0.0 [2024-02-25 14:37:18] INFO grpc.py:81: NVMeoF gateway Git commit: d08860d3a1db890b2c3ec9c8da631f1ded3b61b6...

Sure thing. For now I am very early on in testing and am following the steps as they are listed in the README. FWIW I haven't seen any `cephadm` deployment...

@caroav @gbregman I want to confirm you're not waiting from more info from me on this issue?

@caroav That was the first thing recommended for me to do and the output is above. My second post in this thread. https://github.com/ceph/ceph-nvmeof/issues/460#issuecomment-1962963421

To sanity check I created a new pool `nvmeoftest`, init'd it, then created a new RBD `disk01` on the new test pool then tried creating the name space with this...