Skip to content

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

@anderbubble

Description

@anderbubble

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.

Metadata

Metadata

Assignees

Labels

needs triageNeed to determine the issue

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions