Open chicagoandy opened 1 month ago
Hello, I've got the same issue !
Permissions are also set to Datastore.Audit, Sys.Audit, Sys.Modify, VM.Audit
Thank you for your help and great integration :)
same issue here.
Can confirm.
Same issue here, 'local' and 'local-lvm' storage is not accessible even though 'Datastore.Audit' permission is added.
Also confirmed. I'm trying to give Admin access to see if it works around it.
I solved it by adding the standard role 'PVEAuditor'. So it seems that Mapping.Audit, Pool.Audit or SDN.audit permissions are necessary.
Same here. Whatever permissions I give and even PVEAuditor the repair does not go away. Don't want to give admin as I just want to monitor.
Same here. Whatever permissions I give and even PVEAuditor the repair does not go away. Don't want to give admin as I just want to monitor.
same for me, my datastores are ZFS
I am getting 4 of these types of errors --- just for giggles (on this first PVE that I have added...I have 4 PVE total) - I changed the HomeAssistant from PVEAuditor to Admin - does not help.
Update - after setting to PVEAdmin (in Proxmox)
-- 4 of the errors disappeared after going back though [ CONFIG ] under the Integration (was able to 'uncheck' storage items and 'check' the new ones
... but now I have a new one.
2nd Update --- I used these steps: https://github.com/dougiteixeira/proxmoxve#proxmox-permissions
I created the 4 roles, and then added a 5th HomeAssistant.Admin
that I put all of the permissions from the other 4 in this one. I deleted the permissions setup, and added this one:
Restarted HA - and all errors are gone.
Now I get to play with what I can do with these things and make dashboards for PVE.
How long will the OLD Entities remain that were first created - is there a way to delete them? (or does this look about right for 1 (server with 2 vms)
@bearhntr you are a hero, this was the solution for me as well! Do not skip the step of removing the other permissions, that is crucial
Same error here, just to confirm
with
and the user
belongs to group
still, after reboot, results in ...
Ok, found it. If you "configure" the integration again, you have to deselect the old entries and select the newly appeared entries. Got it.
Checklist
Describe the issue you are experiencing
Getting errors on permissions for access filesystem.![image](https://github.com/user-attachments/assets/77d6adfd-a579-4423-9d2e-a61e9f755472)
Role with permission is created:![image](https://github.com/user-attachments/assets/8e41ecbc-6d51-4bd5-9feb-af0dcf945b5f)
User has role:![image](https://github.com/user-attachments/assets/e4b2e863-3804-435a-af7d-0f4b0ee62a89)
What am I missing...?
In which version of Home Assistant Core do you have the problem?
core-2024.6.4
What version of Proxmox VE Custom Integration has the issue?
3.4.4
What version of Proxmox VE do you have the problem?
7.4
Diagnostics information
home-assistant_proxmoxve_2024-07-13T20-23-42.690Z.log config_entry-proxmoxve-854f7a95cbf55c34318e7c21b95d76c0.json
Additional information
No response