When our foreman server was upgraded from 3.9 to 3.10, the upgrade was successful. But, after login, I realized hosts are all gone, except for foreman VM; and computer resource, hostgroup and subnet became empty.
Webhook, ansible, domain are good.
We have followed foreman up grade instruction since 3.3. But never seen setting gone before.
Below is my upgrade command, please help with correct my command or provide with possible alternative solution. Thank you
I’ve moved your post to the “Support” category.
What you describe sounds like your database was reset, which clearly shouldn’t happen during an upgrade. Are you using the DB on the same system or external?
Hi @evgeni , this is a stage environment, and we only have 3 hosts in the stage environment. After stage upgrade verified, we will proceed to production. But after stage upgrade, only f#1 and #2 exist. #345 is gone.
Oh!
But wait, the SQL above shows 345 fine. So it is in the DB.
Is it maybe assigned to an org/location that you don’t see by default when you login?
Can you try selecting “Any Org” and “Any Location” at the top menu to see everything?
Hi @evgeni , yes, you are right. I forgot to adjust location to any location. Sorry, this issue is caused by my overlook. We can close this ticket. Thank you very much.
Hi @evgeni , There is one more issue I found in upgrade.
Our hostgroup of MS_Windows/Systems/SJC1 is connected to the location of Systems/SJC1.
When creating VM, we should see all settings from hostgroup to be added, for example, “Deploy On”. But none of them are brought into the host creation items. I choose any location and organization this time