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

Changing ASCENDER_HOSTNAME and re-running setup.sh does not update properly #29

Open
anderbubble opened this issue Oct 1, 2023 · 2 comments
Assignees
Labels
needs triage Need to determine the issue

Comments

@anderbubble
Copy link
Contributor

anderbubble commented Oct 1, 2023

I ran setup.sh without changing ASCENDER_HOSTNAME away from its initial example.com. This completed successfully, but did not allow me to access the system.

After that I changed it to the correct value and re-ran setup.sh. Now the playbook ends in an error.

fatal: [localhost]: FAILED! => {"attempts": 200, "changed": false, "content": "", "elapsed": 0, "msg": "Status code was -1 and not [200]: Request failed: <urlopen error [Errno 111] Connection refused>", "redirected": false, "status": -1, "url": "http://ascender1.local:80/api/v2/ping/"}

PLAY RECAP ********************************************************************************************************************************************************************************************************************************
ascender_host              : ok=13   changed=1    unreachable=0    failed=0    skipped=3    rescued=0    ignored=0   
localhost                  : ok=18   changed=5    unreachable=0    failed=1    skipped=1    rescued=0    ignored=0

It should be possible to update ASCENDER_HOSTNAME without re-installing from scratch, but how to do so is not clear.

@anderbubble
Copy link
Contributor Author

@cigamit cigamit added the needs triage Need to determine the issue label Oct 17, 2023
@adamhgriffith-uofu
Copy link
Contributor

adamhgriffith-uofu commented Oct 17, 2023

Seconding. Just had to move my test instance to a different hostname.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage Need to determine the issue
Development

No branches or pull requests

4 participants