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

Error getting service provider detail for ResourceModelSource/file #4804

Closed
jrose84 opened this issue May 9, 2019 · 14 comments

Comments

Projects
None yet
2 participants
@jrose84
Copy link

commented May 9, 2019

Describe the bug
After upgrading from 3.0.19 to 3.0.21, I can no longer edit nodes from webUI
Error message when I choose source: Error getting service provider detail for ResourceModelSource/file

My Rundeck detail

  • Rundeck version: [ e.g. 2.11.3] 3.0.21
  • install type: [choose: rpm,deb,war,launcher] rpm
  • OS Name/version: [e.g. ubuntu 16.04] CentOS Linux release 7.6.1810 (Core)
  • DB Type/version: [choose: mysql, postgres, mssql, oracle, ... ] 5.7.22-22-log Percona Server

To Reproduce
Steps to reproduce the behavior:

  1. Go to any project
  2. Click on Project Settings
  3. Click on Edit Nodes
  4. Click on Sources

Expected behavior
The ability to edit my YAML nodes file

Screenshots
If applicable, add screenshots to help explain your problem.
image
image

Desktop (please complete the following information):

  • OS: [e.g. iOS] Windows 10
  • Browser [e.g. chrome, safari] Google Chrome
  • Version [e.g. 22] Version 74.0.3729.131 (Official Build) (64-bit)

Additional context
N/A

@jrose84

This comment has been minimized.

Copy link
Author

commented May 9, 2019

I also tried installing a clean instance in a sanbox environment and noting the issue persists. Not sure how to resolve...

@gschueler gschueler added the bug label May 9, 2019

@gschueler gschueler added this to the 3.0.22 milestone May 9, 2019

@gschueler

This comment has been minimized.

Copy link
Member

commented May 9, 2019

can you paste your project configuration (as it pertains to the resource model configuration?)

@gschueler

This comment has been minimized.

Copy link
Member

commented May 9, 2019

are there any errors in the browser javascript console?

@jrose84

This comment has been minimized.

Copy link
Author

commented May 9, 2019

sure!

#edit below
project.description=Common tasks for Performance Environment
project.disable.executions=false
project.disable.schedule=false
project.jobs.gui.groupExpandLevel=1
project.label=PRF
project.name=PRF
project.nodeCache.delay=30
project.nodeCache.enabled=true
project.nodeCache.firstLoadSynch=true
project.ssh-authentication=privateKey
project.ssh-command-timeout=0
project.ssh-connect-timeout=0
project.ssh-keypath=/home/rundeck/.ssh/id_rsa
resources.source.1.config.file=/var/rundeck/nodes/perf.yml
resources.source.1.config.format=resourceyaml
resources.source.1.config.generateFileAutomatically=true
resources.source.1.config.includeServerNode=false
resources.source.1.config.requireFileExists=true
resources.source.1.config.writeable=true
resources.source.1.type=file
service.FileCopier.default.provider=jsch-scp
service.NodeExecutor.default.provider=jsch-ssh```
@jrose84

This comment has been minimized.

Copy link
Author

commented May 9, 2019

does this help?
image

@gschueler

This comment has been minimized.

Copy link
Member

commented May 9, 2019

hmm, does your rundeck base URL include a /rundeck context path?

@jrose84

This comment has been minimized.

Copy link
Author

commented May 9, 2019

yeah, defined in several places

@gschueler

This comment has been minimized.

Copy link
Member

commented May 9, 2019

ok, i think there is a bug in the javascript which is not using the correct URL path

@jrose84

This comment has been minimized.

Copy link
Author

commented May 9, 2019

how do we fix?

@jrose84

This comment has been minimized.

Copy link
Author

commented May 9, 2019

also, the node files are stored local, so not sure why it's looking via URL

@jrose84

This comment has been minimized.

Copy link
Author

commented May 9, 2019

also, not sure if this helps, but we put rundeck behind apache reverse proxy (hence why the URL is port 80 and not 4440)

@jrose84

This comment has been minimized.

Copy link
Author

commented May 9, 2019

apache config

CustomLog /var/log/httpd/access_log combined
ErrorLog /var/log/httpd/proxy/rundeck/error_log
CustomLog /var/log/httpd/proxy/rundeck/access_log combined
ProxyPass /rundeck http://njrndk01.kligerweiss.net:4440/rundeck
ProxyPassReverse /rundeck http://njrndk01.kligerweiss.net:4440/rundeck
ProxyRequests Off

RedirectMatch ^/$ /rundeck

# Local reverse proxy authorization override
<Proxy http://njrndk01.kligerweiss.net:4440/rundeck*>
        Order deny,allow
        Allow from all
</Proxy>

again, not sure if it helps, but since the issue appears to be with broken URL and 404 errors, figured it couldn't hurt to share

@jrose84

This comment has been minimized.

Copy link
Author

commented May 9, 2019

FYI - removed web context from rundeck config, adjusted apache proxy settings, and this seems to be a valid workaround

@gschueler

This comment has been minimized.

Copy link
Member

commented May 9, 2019

@jrose84 yes, running without web context path will fix it.

I'm fixing the bug for next release.

gschueler added a commit that referenced this issue May 10, 2019

@gschueler gschueler closed this in 10670fb May 10, 2019

gschueler added a commit that referenced this issue May 10, 2019

Merge pull request #4808 from rundeck/issue/4804
Fix #4804 broken node config page with web context path
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.