Skip to content
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

No nodes listed, no errors #47

Open
smcavoy-travelbird opened this issue Apr 26, 2016 · 6 comments
Open

No nodes listed, no errors #47

smcavoy-travelbird opened this issue Apr 26, 2016 · 6 comments

Comments

@smcavoy-travelbird
Copy link
Contributor

I have installed 1.5.2 on 2.6.6 and am not seeing any nodes populating.

I tried a false key and received and error. Fixed it, no nodes.
I checked the key is authorised to run describe-instances
And I have seen https between rundeck and a AWS IP that was timed with the reload of the node list.

I do not see any errors related to getting the details from AWS. I see no option to increase the verbosity of logging to determine why this is not working.

The only odd thing in the logs I found is below:

2016-04-26 10:19:31,399 - Evaluating Decision for: res subject action env: authorized: true: GRANTED, reason: GRANTED, evaluations:        ACLRule{'Admin, all access.' context={project='.*'} type='resource' for: { group='admin'} allow=[*]} GRANTED for action read => GRANTED (0ms)
2016-04-26 10:19:31,399 - Evaluating Decision for: res subject action env: authorized: false:      No context matches subject or environment => REJECTED_NO_SUBJECT_OR_ENV_FOUND (0ms)

Has this behaviour been seen before? Is there anyway to further debug this problem?
Thanks,

Sean

@gschueler
Copy link
Member

Sean, the 2.6.6 node source is now asynchronous by default, and ec2 plugin has its own asynchronous behavior, it might be just be delayed in displaying the results. you can also try disabling the asynch nodes feature in the project

@smcavoy-travelbird
Copy link
Contributor Author

When creating a job and selecting a set of nodes to have a step execute on there is an option to refresh the list. I assume this is to query AWS for an updated inventory at that time. Is that not the case?

Are there no options to have more verbose logging?

@smcavoy-travelbird
Copy link
Contributor Author

I found the problem, I did not add an endpoint, I left it blank. Is that expected behaviour?

@gschueler
Copy link
Member

@smcavoy-travelbird what region are you using? leaving it blank uses the default endpoint, which i think is us-east-1

@smcavoy-travelbird
Copy link
Contributor Author

We have nothing in us-east-1, only eu-west-1/eu-central-1
So this explains it. It would be helpful if that was clearer so I created a PR:
#48

@gschueler
Copy link
Member

Perhaps the text for the 'endpoint' input field should also have more information there, and/or have the default be shown explicitly so it's clear what it is

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants