-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Get first server that listens on http port for default_server roulette" has no attribute 'name' #86
Comments
Can you try and run the |
yeah I already did. Same result. It just finished to execute this command though:
It finished successfully but at a first glance there isn't everything (no vhost for instance). I'm looking at it now. Now I'm executing the entire playbook to see what happens |
I'm looking at this portion of the playbook
I doubt that the flattened list is empty therefore, out of the top of my head, it might happen that there is no "name" key in the list Now I'm investigating about the structure that those list are supposed to have and which one can be actually empty |
Nothing, same issue even after running the entire playbook I tried putting in my nginx.yaml
which should populate
therefore there should be at least one item.name populated I don't get it |
What happens if you remove any custom configuration in the inventory and go with the DebOps defaults? I know that you want to configure it - just check how the defaults behave, then you can add your configuration bit by bit to see where the error is. You might also need to remove the |
that's a valuable piece of information. Yes I am proceeding step by step in order to understand where is the issue. The biggest pain is due to the fact that running the playbook is SO slow. (I don't know if it's due to my slow internet connection) |
Since the issue is definitely located in
The 'debops.ferm' role is particularly slow, sorry about that. You could also add tags to all of the tasks that affect the selection of the default server, add |
I ran it with Exactly the same behavior. I'm going to run it with nginx.yaml
|
which gives (.fact was removed) TASK [debops.nginx : Create global webroot directories if allowed] ************************** fatal: [dctl]: FAILED! => { The error appears to have been in '/home/damko/.local/share/debops/debops-playbooks/roles/debops.nginx/tasks/nginx_servers.yml': line 3, column 3, but may The offending line appears to be:
|
Umm.. I guess the issue is lack of documentation for the The
Because you used a string instead of a YAML dictionary, the above error showed up. If you change your entry to be similar to the one I wrote above, role should behave correctly. The The If you disable the above variable, the role will not manage So, unless you know what you want to do, you shouldn't disable |
Thank you SO much for this explanation! No I see the root of the mistake. Most likely one of the variables in my owncloud.yaml should also be a dictionary but it's not. This would explain the original error.
and this clearly belong to nginx.yaml. Shouldn't this be automatically created by the owncloud role starting from the owncloud__fqdn variable? Maybe I screwed up some variables and that's why it didn't happen? note: If I had to wish for an improvement in the debops doc it would be to see more "kick start" yaml examples. |
Yes, owncloud role has nginx config included in defaults/main.yml.
Heading to bed, good luck and see you tommorow! :-)
15.12.2017 00:42 "Damiano Venturin" <notifications@github.com> napisał(a):
… Thank you SO much for this explanation! No I see the root of the mistake.
Most likely one of the variables in my owncloud.yaml should also be a
dictionary but it's not. This would explain the original error.
I guess the issue is lack of documentation for the debops.nginx role
No. Debops is awesome. Period. Here there are few things:
1.
Most important, it's me not being prepared enough
2.
I didn't plan to configure the nginx role and I just wanted to run the
nextcloud role (as I did in the past) I was focuse on nextcloud
configuration and not on nginx. Mistake by mistake I found myself in the
nginx jungle. You probably know how it works
3.
I understand your YAML dictionary (I didn't re-run it yet)
nginx__servers:
- name: 'domain.com'
enabled: True
and this clearly belong to nginx.yaml. Shouldn't this be automatically
created by the owncloud role starting from the owncloud__fqdn variable?
Maybe I screwed up some variables and that's why it didn't happen?
note: If I had to wish for an improvement in the debops doc it would be to
see more "kick start" yaml examples.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#86 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA_t9slt_CaE3NMRlUieiZrYWfiz6lY-ks5tAbJNgaJpZM4RCcsI>
.
|
I'm reporting this in case someone else needs it. I deleted /etc/ansible/facts.d/owncloud.fact and /etc/ansible/nginx.fact. Then I ran
These are my .yaml files in the inventory dir: nginx.yaml
owncloud.yaml
As @drybjed said the nginx.yaml shouldn't be necessary but it works in my scenario. |
I'm running the latest debops and ansible 2.4.2.0
I'm trying to install owncloud package with nextcloud variant on a vanilla VPS debian stretch fully updated
This is my owncloud.yaml
When I run
I get:
I'm looking into this and I will report what I find. Meanwhile any help is appreciated.
The text was updated successfully, but these errors were encountered: