Luis Felipe Dominguez Vega
Luis Felipe Dominguez Vega
> you tried this? I've gotten it to include some ID in the logs, but it doesn't match the ID being used in the actual tr Hi I'm implementing with...
Works for span_id... but check how the trace_id is a lot of `000000...` (this happen with the other loop method) 
> In my case I have a remote `trace_id` which I feed into my spans with: > > ```rust > span.set_parent(opentelemetry::Context::new().with_remote_span_context( > opentelemetry::trace::SpanContext::new(...), > )); > ``` > > With...
> > Thanks, do you have any public code where i can review how do you use that??? > > No sorry that's extracted and adapted from a closed source...
`GET` over `/v3/{project_id}/volumes/{volume_id}` and get the `size` field of returned json (Gib)
I re-read the doc... sems that is CSI need to get total capacity from the node... in case of Cinder will be the total capacity to use... but if you...
Well i think that if I as the OpenStack manager put a 2T quota over 1T disk is a bad config from me, the CSI can't do magic jejej.... another...
But, check this essenario... you are a user of a Tenant of OpenStack, you dont have access to see the real physical resource of the cloud... then you deploy some...
happen to me, restarting solve the problem eventually... but this is strange... why is happening this?
Me too.. i cleaned the password on database and restarted the core, then the password is updated on database.. but always invalid credentials...