-
Notifications
You must be signed in to change notification settings - Fork 25
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.
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
How to key Protocol when create subscription with rf_event_service.py #138
Comments
Right now the tool automatically puts in "Redfish" for you; it's not provided as an option. This is where the payload is built for the subscription request:
It starts with just the provided destination and fills in Protocol to always be Redfish, then optionally fills in other properties based on whatever else is provided by the user. If you add |
But at least from the error message on the console, it looks like either EventTypes isn't supported by the service or one of the values provided isn't supported. |
It's also possible you're hitting an old bug from a few years ago where the tool was always sending "EventTypes" as part of the payload. Given your sample script input, you're clearly not specifying EventTypes. Can you check your version of Tacklebox? The issue I'm thinking of was fixed in 1.2.9. |
Can you try with |
Are you sure you have the latest version of the tool? It looks like you're using an older version. With how you're invoking the tool, it will run from the installation and not from the source code you've checked out.
|
Hi,
As far as I know Destination and Protocol are necessary to create a subscription, but I don't know how to enter the value about Protocol when creating the subscription.
Not sure if the failure to send the command is related to missing necessary parameters.
Attached the request body about creating Subscription via Redfish:
{
"Context": "Event_Sub",
"Destination": "https://192.168.0.110:4443",
"Protocol": "Redfish",
"EventFormatType": "Event",
"ResourceTypes": [
"EventService",
"Systems",
"AccountService",
"TelemetryService",
"Chassis",
"Managers",
"TaskService"
],
"RegistryPrefixes": [
"EventLog",
"IPMI",
"HttpStatus",
"SyncAgent",
"Security",
"Base",
"Task"
]
}
Thanks,
Felix
The text was updated successfully, but these errors were encountered: