-
Greetings team. 2023-10-23 09:56:21 EDT:10.253.203.172(56148):6535f7f3.421fa:root@vmdb_production:[270842]:ERROR: column lans.switch does not exist at character 183 thnks |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 10 replies
-
Hello @cronosy What version of the code are you using? I was not able to find any code on master with |
Beta Was this translation helpful? Give feedback.
-
Hello guys any idea about the log? |
Beta Was this translation helpful? Give feedback.
-
ok, I don't know what screen this is. SELECT DISTINCT "lans".*
FROM "lans"
INNER JOIN "switches" ON "lans"."switch_id" = "switches"."id"
WHERE "switches"."type" IN ($1, $2, $3, $4, $5)
AND "switches"."ems_id" = $6
AND (
(
"lans"."switch" IS NULL
AND "lans"."uid_ems" = 'dvportgroup-104787'
) OR (
"lans"."switch" IS NULL
AND "lans"."uid_ems" = 'dvportgroup-104787'
)
)
ORDER BY "lans"."id" ASC
LIMIT 20 |
Beta Was this translation helpful? Give feedback.
-
@cronosy Do you have a full stack trace so we can see where this error is coming from? |
Beta Was this translation helpful? Give feedback.
-
@cronosy was this error from the refresh process? I've seen this happen when VMware has an invalid switch id on a network and we try to lookup the switch by ref and can't find it. |
Beta Was this translation helpful? Give feedback.
This is primarily why we only "support" a full admin user, it is so easy to misconfigure something and cause a problem.
I recommend that you try changing the credentials to a full administrator and see if the issue goes away. If you have to have a restricted user the only feasible way is if the user has full recursive read access to an entire datacenter. This is because DVSwitches/PortGroups are owned at the datacenter level.