Novajoin availability should not impeach deploy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Incomplete
|
Medium
|
Unassigned |
Bug Description
Dear Stackers,
While doing some "lab" tests, I stumbled on a "nice" things:
If novajoin-server isn't reachable for some reason, the current behavior is to just output "unable to find node"-like error, and abort the deploy.
I'm wondering if this is really a good thing and, if so, a meaningful message shouldn't be shown.
For the records, novajoin serves "only" one purpose: provide a gateway/proxy to a freeIPA instance so that nodes get recorded in it, using both novajoin-server and novajoin-notify.
It would be good to get either a more precise error message "novajoin-server isn't reachable, aborting", or maybe a failover "unable to reach novajoin-server, discard all freeIPA things"
Cheers,
C.
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → rocky-1 |
Changed in tripleo: | |
milestone: | rocky-1 → rocky-2 |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
Changed in tripleo: | |
milestone: | rocky-3 → rocky-rc1 |
Changed in tripleo: | |
milestone: | rocky-rc1 → stein-1 |
Changed in tripleo: | |
milestone: | stein-1 → stein-2 |
Changed in tripleo: | |
milestone: | stein-2 → stein-3 |
Changed in tripleo: | |
milestone: | stein-3 → train-1 |
Changed in tripleo: | |
milestone: | train-1 → train-2 |
Changed in tripleo: | |
milestone: | train-2 → train-3 |
Changed in tripleo: | |
milestone: | train-3 → ussuri-1 |
Changed in tripleo: | |
milestone: | ussuri-1 → ussuri-2 |
Changed in tripleo: | |
milestone: | ussuri-2 → ussuri-3 |
Changed in tripleo: | |
milestone: | ussuri-3 → ussuri-rc3 |
Changed in tripleo: | |
status: | Triaged → Incomplete |
Changed in tripleo: | |
milestone: | ussuri-rc3 → victoria-1 |
Changed in tripleo: | |
milestone: | victoria-1 → victoria-3 |