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

Cannot add system when starting from scratch #98

Closed
TomSie opened this issue Feb 28, 2020 · 2 comments · Fixed by #107
Closed

Cannot add system when starting from scratch #98

TomSie opened this issue Feb 28, 2020 · 2 comments · Fixed by #107
Assignees

Comments

@TomSie
Copy link
Collaborator

TomSie commented Feb 28, 2020

When starting with a new database and not configuring any hosts, "Add system" fails with an error message:

image

@TomSie TomSie assigned TomSie and jones718 and unassigned TomSie Feb 28, 2020
@maverickwoo
Copy link

I think this issue happened when adding a system before adding a Location. (The locations and systems_location tables are both empty.)

Some more notes:

  1. In a fresh installation, the locations, systems, and systems_location tables are all empty in the database. The runner system CRUD operations on the web interface would want to take these corner cases into account. (It seems the current code is written to assume there is at least one location in the DB and will assign any new hosts to that location.)

  2. Upon auditing the code, there is currently a notion of "host names that start with the string dev-". These seem to be intended for runner systems that were added through the web interface:

    {% if host.isNotPersistentDevSys == True %}
    <td style="text-align: left; width: 20%;"><a href="/systems/view/dev-{{ host.Name }}/{{ group.Name }}">{{

    So it seems the design intends to have two steps when adding a runner:

    1. Add the runner system(s) and assign them a location using the web interface. This would update the DB and would be doable after the bug and Changing location after adding first location does not work #100 are fixed.
    2. Manually modify the Ansible inventory file in the file system so that Ansible also knows about these runner systems in a future restart of the PoleMarch container. In retrospect, I think this is likely what this step really means:
      - change /srv/fluffi/data/dnsmasq/hosts e.g., if you want to give some systems static IP addresses or if you want to move services to different machines

@p4cx
Copy link
Collaborator

p4cx commented Mar 3, 2020

Still not fixed. Work in progress!

@p4cx p4cx linked a pull request Mar 4, 2020 that will close this issue
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

Successfully merging a pull request may close this issue.

4 participants