`delivery-ctl` cannot list users nor running test

Hi,

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.

Try to check the Status and Restart all services.

[vagrant@delivery-test ~]$ sudo delivery-ctl status
run: delivery: (pid 22849) 293s; run: log: (pid 15713) 101506s
run: nginx: (pid 22884) 293s; run: log: (pid 15620) 101511s
run: postgresql: (pid 22890) 292s; run: log: (pid 15602) 101512s

[vagrant@delivery-test ~]$ sudo delivery-ctl restart
ok: run: delivery: (pid 23052) 1s
ok: run: nginx: (pid 23087) 0s
ok: run: postgresql: (pid 23093) 0s

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>

Or maybe my trial license is expired. I cannot login either.

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.

For this specific version, setup using https://github.com/chef-cookbooks/delivery-cluster/pull/217 (with the test.json env within that PR)

root@delivery-server-test:~# cat /opt/delivery/version-manifest.txt 
delivery 0.4.437

Component                   Installed Version   Version GUID                                    Overridden From                            
-------------------------------------------------------------------------------------------------------------------------------------------
base-dialyzer-plt           0.0.1               
bundler                     0.4.437             
cacerts                     2016.01.20          md5:36eee0e80373937dd90a9a334ae42817            
chef-gem                    12.5.1              11.12.2                                    
cmake                       3.4.3               md5:4cb3ff35b2472aae70f542116d616e63            
common                      0.0.1               
config_guess                master              git:dafd8e767ec87b90aac62f0fcedd11944c84b50a    
cpanminus                   1.7004              md5:02fe90392f33a12979e188ea110dae67            
curl                        7.47.1              md5:3f9d1be7bf33ca4b8c8602820525302b            
delivery                    0.0.1               
delivery-cookbooks          0.4.437             
delivery-ctl                0.4.437             
delivery-git-hooks          0.4.437             
delivery-schema             0.4.437             
delivery-scripts            0.4.437             
delivery-server             0.4.437             
delivery-vendor-cookbooks   0.4.437             
delivery-web                0.4.437             
elasticsearch               2.3.1               sha1:387c5f045843339d486203b0048ff8911e9c8c54   
erlang                      18.2                md5:b336d2a8ccfbe60266f71d102e99f7ed            R15B03-1                                   
expat                       2.1.0               md5:dd7dab7a5fea97d2a6a43f511449b7cd            
git                         2.8.2               md5:3022d8ebf64b35b9704d5adf54b256f9            
insights                    0.0.1               
insights-batch-jobs         0.4.437             
insights-elasticsearch      0.4.437             
insights-logstash           0.4.437             
insights-scripts            0.4.437             
insights-web                0.4.437             
kibana                      4.3.1               md5:1d65db216ff444d8239772828d783ef9            
libedit                     20130712-3.1        md5:0891336c697362727a1fa7e60c5cb96c            20120601-3.0                               
libffi                      3.2.1               md5:83b89587607e3eb65c70d361f13bab43            
libiconv                    1.14                md5:e34509b1623cec449dfeb73d7ce9c6c6            
libidn                      1.32                md5:4dd8356ba577287ea7076bfa1554b534            
libossp-uuid                1.6.2               md5:5db0d43a9022a6ebbbc25337ae28942f            
libreadline                 6.3                 md5:33c8fb279e981274f485fd91da77e94a            
libtool                     2.4.2               md5:d2f3b7d4627e69e13514a40e72a24d50            2.4                                        
libyaml                     0.1.6               md5:5fe00cda18ca5daeb43762b80c38e06e            
logrotate                   3.8.5               md5:d3c13e2a963a55c584cfaa83e96b173d            
logstash                    2.3.1               sha1:fa0f46fcdb0a89057ca4194caa681e9c6d2b0133   
lsyncd                      2.1.6               md5:e0618ac837a25aa027fa1cbb67815c23            
lua                         5.1.5               md5:2e115fe26e435e33b0d5c022e4490567            
makedepend                  1.0.5               md5:efb2d7c7e22840947863efaedc175747            
ncurses                     5.9                 md5:8cb9c412e5f2d96bc6f459aa8c6282a1            
nginx                       1.8.1               md5:2e91695074dbdfbf1bcec0ada9fda462            
nodejs-binary               5.6.0               md5:17cb2fc57a0cf46bcc021060b25edf48            
omnibus-ctl                 0.3.6               git:c514d1d4ecb24e30fdbd310b2dd038b2192b4fa7    
openssl                     1.0.1t              md5:9837746fcf8a6727d46d22ca35953da1            
pcre                        8.38                md5:8a353fe1450216b6655dfcf3561716d9            
perl                        5.18.1              md5:304cb5bd18e48c44edd6053337d3386d            
perl_pg_driver              3.3.0               md5:547de1382a47d66872912fe64282ff55            
pkg-config-lite             0.28-1              md5:61f05feb6bab0a6bbfab4b6e3b2f44b6            
popt                        1.16                md5:3743beefa3dd6247a73f8f7a32c14c33            
postgresql                  9.3.5               md5:5059857c7d7e6ad83b6d55893a121b59            9.2.10                                     
preparation                 1.0.0               
r-train                     0.11.2              
rabbitmq                    3.6.1               md5:c9da5523b7504fb7932e813ef7856d1f            
rb-readline                 master              git:cf67cd06ae89e8b2710ba930c3015639240ac7b7    
rebar                       2.5.1               git:e9f62c45807ce2db39e0606c4d97cd071416bd64    93621d0d0c98035f79790ffd24beac94581b0758   
relx                        master              git:38bf6186db7518e5b2eae9b51cc1096362697128    
remove-build-deps           0.0.1               
remove-cmake                3.4                 
remove-libidn               1.32                
remove-nodejs               5.6.0               
rsync                       3.1.1               md5:43bd6676f0b404326eee2d63be3cdcfe            
ruby                        2.1.6               md5:6e5564364be085c45576787b48eeb75f            2.1.8                                      
rubygems                    0.4.437             
runit                       2.1.1               md5:8fa53ea8f71d88da9503f62793336bc3            
server-jre                  8u74                md5:2c244c8071b7997219fe664ef1968adf            
sqitch                      0.973               md5:0994e9f906a7a4a2e97049c8dbaef584            
strip-objects               0.0.1               
tools                       0.0.1               
util-macros                 1.18.0              md5:fd0ba21b3179703c071bbb4c3e5fb0f4            
xproto                      7.0.25              md5:a47db46cb117805bd6947aa5928a7436            
zlib                        1.2.8               md5:44d667c142d7cda120332623eab69f40            

Howdy!

I know the help output doesn’t show it, but I think it requires enterprise name as its argument:

delivery-ctl list-users yourenterprise

@marcparadise the enterprise name is test:

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.

Hello Delivery Friend!

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! :sob: But hey, I just fixed it!! Yey! :tada: 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!

Apologize for the inconveniences.
Salim Afiune

Hi @afiune,

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.

Hey @chrisduong !!

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:

  1. What is the FQDN of the Delivery Server that you configured inside the file /etc/delivery/delivery.rb (look for delivery_fqdn)
  2. 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

2 Likes

Hi @afiune,

It is fixed. Thanks a lot.