[BUG] VAI Cache DB Files Not Present in Pods/Breaks Rancher UI #47601
Assignees
Labels
kind/bug
Issues that are defects reported by users or that we know have reached a real release
priority/0
team/frameworks
the team that is responsible for frameworks, projects, webhook, and other various areas
team/ui
Milestone
Comments
brudnak
added
kind/bug
|
This is a known bug - rancher/dashboard#12265 and was agreed not a release blocker. I tihnk @MbolotSuse was going to get a fix in for a later version Edit: Maybe two bugs same outcome. Though we agreed vai related issues aren't release-blockers |
We have removed the db |
|
Verified and agree with @richard-cox it's that same issue. Basically, listing resources contain the state field correctly, but data coming from the watch doesn't. That page is watching the deployments so on initial page load we get the correct state but they quickly become "unknown" when we receive the data from the watch. |
Merged
Validation TemplateRoot CauseWith rancher/steve#264 support for Transform functions was added to the SQL cache mode. This caused steve to add the metadata.state, metadata.relationships, and id fields before the object was added to the SQL cache. Because of this, the formatter (which previously added these values at a later layer before the request was returned to the user) was changed to no longer add these values when the sql cache was enabled, in order to not duplicate this addition. However, this change didn't fully work. While the list calls use the SQL cache to return information to the user, the other calls (create/update/delete/get/watch) did not use the cache, and instead returned objects to the user as they are seen by Kuberentes. Since the formatter was no longer adding the metadata.state when the SQL cache is on, this caused objects retrieved by this operation to be missing the metadata.state and metadata.relationships values. What was fixed, or what change have occurredThe formatter now will always add the metadata.state and metadata.relationships, like it did before rancher/steve#264. Areas or cases that should be tested
What areas could experience regressionsThe calculation of metadata.state and metadata.relationships for list calls. These values should be set on the list calls in the same way as before. They should also be usable for filtering/sorting (when the feature is enabled), like before. Lastly, they should be set to the same values as is visible on the objects when they are retrieved through other operations (note - there may be slight discrepancies here due to cache timing and object state change). Are the repro steps accurate/minimal?Yes, some are included here for convienence.
|
🧪 Test Environment... CLICK TO EXPAND! ⬅️
🧪 Test Cases
🚨 5 test cases... CLICK TO EXPAND! (For table links to work) ⬅️1 / Fresh Install
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rancher Server Setup
aws acmDescribe the bug
Enabling vai gives all deployments a UI status of
unknown. Unable to see the Rancher pods via the UI.To Reproduce
Result
Once Rancher restarts after making this change, all deploymets in the UI have a status of
unknown. And the Rancher pods aren't visible via the UI anymore.The
.dbfiles are not in the pods.Expected Result
For Rancher to work as usual once the vai feature is enabled.
Screenshots
Additional Context
Workaround
Disabling the vai cache does fix the UI
Bug Frequency
The text was updated successfully, but these errors were encountered: