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

Notification Hub Namespace create failed with BadArgument Exception #38508

Open
Fred-sun opened this issue Nov 13, 2024 · 2 comments
Open

Notification Hub Namespace create failed with BadArgument Exception #38508

Fred-sun opened this issue Nov 13, 2024 · 2 comments
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Notification Hub question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@Fred-sun
Copy link

Fred-sun commented Nov 13, 2024 •
edited
Loading

  • Package Name: azure-mgmt-notificationhub
  • Package Version: azure-mgmt-notificationhubs==8.1.0b2
  • Operating System: Ubuntu 22.04
  • Python Version: python3

Describe the bug
A clear and concise description of what the bug is.
After upgrade azure-mgmt-notificationhub to v8.1.0b1, Create a namesapce failed. Error msg: BadArgument\nMessage: Value cannot be null. (Parameter 'value')\nTarget: value"

Created successfully in version v8.0.0b1!
To Reproduce
Steps to reproduce the behavior:

  1. Create a new notification hub.
  2. Create a new namespace in the notification hub. Can't create. Error msg: Message: Value cannot be null. (Parameter 'value')\nTarget: value"

Expected behavior
A clear and concise description of what you expected to happen.
The namespace created success!
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.
@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Notification Hub question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. labels Nov 13, 2024
@github-actions GitHub Actions
Copy link

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @tjsomasundaram.

@Fred-sun
Copy link
Author

Any feedback?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Notification Hub question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Fred-sun