Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ExportID uint32 didn't match dbus type #1

Open
Zagrebelsky opened this issue Aug 19, 2019 · 1 comment · May be fixed by #5
Open

ExportID uint32 didn't match dbus type #1

Zagrebelsky opened this issue Aug 19, 2019 · 1 comment · May be fixed by #5

Comments

@Zagrebelsky
Copy link

Hi Gandi,

Please add fix from this branch:
https://github.com/croomes/ganesha_exporter/commit/779f3d91ecef72e1dd4bcb0705ac5f23c2012b1e
@diconico07
Copy link
Contributor

We actually use 32bits export_id at Gandi (16bits is definitely not enough) and the nfs-ganesha dbus api documentation present export_id as a 32 bits integer but the upstream code indeed says it is an uint16...
Does this issue make the exporter unusable ? If so, I think we should be able to find a way to hide this difference behind the --gandi flag

robertlestak pushed a commit to robertlestak/ganesha_exporter that referenced this issue Jul 27, 2024
bump go, remove vendor dir, address dbus.Store: length mismatch error. …
d830885 
…Fixes Gandi#1, Gandi#3, Gandi#4
@robertlestak robertlestak linked a pull request Jul 27, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

bump go, remove vendor dir, address dbus.Store: length mismatch error robertlestak/ganesha_exporter
2 participants
@diconico07 @Zagrebelsky