I installed Chef Delivery version “0.4.404” from RPM package delivery-0.4.404-1.el7.x86_64.
I cannot list users for my enterprise test. It says The command you entered is not correct, even though I looked up the docs.chef#delivery-ctl
[vagrant@delivery-test ~]$ sudo delivery-ctl list-enterprises
test
[vagrant@delivery-test ~]$ sudo delivery-ctl list-users test
The command you entered is not correct.
But nothing helps. I cannot verify my Chef Delivery server setup either.
[vagrant@delivery-test ~]$ sudo delivery-ctl test
/opt/delivery/embedded/lib/ruby/2.1.0/open-uri.rb:36:in `initialize': No such file or directory @ rb_sysopen - /etc/opscode-delivery/opscode-analytics-running.json (Errno::ENOENT)
from /opt/delivery/embedded/lib/ruby/2.1.0/open-uri.rb:36:in `open'
from /opt/delivery/embedded/lib/ruby/2.1.0/open-uri.rb:36:in `open'
from (eval):40:in `block in load_file'
from /opt/delivery/embedded/lib/ruby/gems/2.1.0/gems/omnibus-ctl-0.3.6/lib/omnibus-ctl.rb:171:in `call'
from /opt/delivery/embedded/lib/ruby/gems/2.1.0/gems/omnibus-ctl-0.3.6/lib/omnibus-ctl.rb:171:in `block in add_command'
from /opt/delivery/embedded/lib/ruby/gems/2.1.0/gems/omnibus-ctl-0.3.6/lib/omnibus-ctl.rb:575:in `run'
from /opt/delivery/embedded/lib/ruby/gems/2.1.0/gems/omnibus-ctl-0.3.6/bin/omnibus-ctl:31:in `<top (required)>'
from /opt/delivery/embedded/bin/omnibus-ctl:23:in `load'
from /opt/delivery/embedded/bin/omnibus-ctl:23:in `<main>
delivery-ctl seems to be unable to list users for me as well, with recent license:
root@delivery-server-test:~# delivery-ctl | grep -A1 list-users
list-users
Lists all users
root@delivery-server-test:~# delivery-ctl list-users test
The command you entered is not correct.
root@delivery-server-test:~# delivery-ctl list-enterprises
test
root@delivery-server-test:~# delivery-ctl list-users test
The command you entered is not correct.
Thank you so much for your feedback!! We really appreciate you are sharing this with us.
I’m afraid you have encountered a bug in the list-users command! But hey, I just fixed it!! Yey! The change is under review and once it gets approve in our Internal Delivery Server we will release it so you can upgrade it and have it working!
I’m glad to hear the good news from you. By the way, I also have another problem that I cannot login into Chef Delivery server, it keeps saying “wrong username or password” even if I delete and create as many user to test the login. And strangely, I don’t see any request to Delivery nginx log when I press the “log in” button. Does it relate to the bug also.
P.S: I turned on “Browser developer tool”, and I don’t see the any response from Chef Delivery server when I press the 'log in" button.
We just merged the code to fix this problem and also to expose better output when you introduce wrong arguments to the CTL commands. Thank you one more time for letting us know about this!
About your problem with the Delivery Server. I think I know what the problem is. But first let me ask you a couple of questions:
What is the FQDN of the Delivery Server that you configured inside the file /etc/delivery/delivery.rb (look for delivery_fqdn)
Are you trying to access the Delivery WebUI from a different IP/DNS than the one you configured on the file above?
Well if you answered yes to the question number two, then the problem is that you have to configure the same IP or DNS that you are tying to access the WebUI (nginx). This is something we will fix in the future but for now, make the FQDN of the Delivery Server match with the one you are trying to use on the browser.
If you change the delivery_fqdn on the file, you need to run: delivery-ctl reconfigure on the server after you are done with the modifications.
Let me know if this fixes your problem!
Salim Afiune