Hi there I ve run the deployment of a new version of fleet e

Question

Hi there I ve run the deployment of a new version of fleet everything went smoothly however the tools is not allowing the login in the logs I see `authentication error find host timestamp 2022 03 29T17 04 30Z missing destination name public ip in fleet Host` I ve remotely connected to the DB but all the information is still there any thoughts on this

Kathy Satterlee · Answer

Hi < JojoD> Just to make sure we re on the same page was this an upgrade to an existing Fleet instance or a fresh install

JojoD · Answer

it was an existing instance

Kathy Satterlee · Answer

Gotcha And did you run `fleet prepare db` before serving the updated version

JojoD · Answer

yep migrations were completed

JojoD · Answer

I run it twice the second time it returned the message that there was nothing to do because the migration was complete

Kathy Satterlee · Answer

Thanks for the additional context I ll do a bit of research and get back to you shortly

JojoD · Answer

thank you < Kathy Satterlee>

Kathy Satterlee · Answer

Might be relevant how are you logging in Through the UI or using `fleetctl`

JojoD · Answer

through the UI

Kathy Satterlee · Answer

Are you seeing errors when you actually log in or just through the logs

JojoD · Answer

just through logs in the UI it shows Authentication failed

Kathy Satterlee · Answer

Thanks again I m sure I ll have more questions

JojoD · Answer

no worries

JojoD · Answer

thanks for the support ok hand

zwass · Answer

It sounds like you might be running a different version of Fleet when running the migrations vs when running the server

JojoD · Answer

oh I think I used different fleet installations for making the migration

JojoD · Answer

no actually I ve used the same docker image thinking face

Kathy Satterlee · Answer

Can you double check the Fleet version with `fleetctl version`

zwass · Answer

^ That will be the `fleetctl` version Maybe double check what you get from the ` version` API endpoint on Fleet

Kathy Satterlee · Answer

Thanks < zwass>

JojoD · Answer

can that be checked using the cli

Kathy Satterlee · Answer

Did you upgrade `fleetctl` to the newest version along with Fleet

Kathy Satterlee · Answer

And you can hit the ` version` endpoint through the REST API without Auth ```<https fleet example com version>```

JojoD · Answer

thank you so the `fleetctl` shows `fleetctl version 4 8 0` and the other shows `version 4 10 0 `

zwass · Answer

4 10 is not right It sounds like you ve run migrations for 4 12 but your server is running 4 10

JojoD · Answer

how can I know what version the migration was run for also the last version I ve uploaded to the server was the 4 10 0 thinking face

zwass · Answer

What command are you using to run the migration Can you replace the `prepare db` part with `version full`

JojoD · Answer

this is how I run it

JojoD · Answer

like running `fleet version full`

Kathy Satterlee · Answer

What do you get if you run ` usr bin fleet version full` from the same location

JojoD · Answer

so it seems it does has the `4 12 0` open mouth

Kathy Satterlee · Answer

There s the culprit

JojoD · Answer

gosh so recaping fleet and fleetctl should both be in the same version to run successfully

Kathy Satterlee · Answer

Ideally but the real culprit here is that the version of Fleet that s served and the version that was used for database migrations don t match up

JojoD · Answer

is there a way to know what version will run the migration

Kathy Satterlee · Answer

You can double check the version of Fleet installed with the ` usr bin fleet version full` command before running the migrations

JojoD · Answer

got it

JojoD · Answer

thanks a lot for the help < Kathy Satterlee> and < zwass>

Kathy Satterlee · Answer

Do you still have the terminal window where you ran `fleet serve` after the upgrade open

JojoD · Answer

not really I ve used the cli of the docker image used to deploy the new version is not exactly the same server

JojoD · Answer

hello again sweat smile I ve deployed the new version but the behavior remains any additional ideas thinking face

zwass · Answer

Can you check the ` version` endpoint again

zwass · Answer

It sounds like you still aren t running 4 12 on your server

JojoD · Answer

yup first thing I did the version now looks up to date

zwass · Answer

What do you mean at the top when you say the tools is not allowing the login

JojoD · Answer

when headed to the UI we get this message when trying to access with email + pass

JojoD · Answer

additionally we have SSO enabled if we try this option it returns 404

JojoD · Answer

one of my team members asures that the error should be in the DB but I see all the data there so I doubt the DB it s the problem

zwass · Answer

What do you see in the Fleet server logs just after attempting this

JojoD · Answer

in the logs it actually seems to be receiving data from the endpoints

JojoD · Answer

gosh the problem ended up being the IdP callback URL I ve updated this URL to update it from ` api v1 kolide sso callback` to ` api v1 fleet sso callback` everything is working now raised hands

JojoD · Answer

again thanks < zwass> and < Kathy Satterlee> for all the help handshake

Kathy Satterlee · Answer

That s awesome Way to stick with it < JojoD> slightly smiling face