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

[General workload issue]: InvalidPolicyParameterUpdate #538

Open
1 task done
philwallerekco opened this issue Feb 19, 2025 · 8 comments
Open
1 task done

[General workload issue]: InvalidPolicyParameterUpdate #538

philwallerekco opened this issue Feb 19, 2025 · 8 comments
Assignees
@Brunoga-MS @tagolovina
Labels
Pattern: ALZ 🚁 Issues / PR's related to the ALZ Pattern

Comments

@philwallerekco
Copy link

Check for previous/existing GitHub issues

  • I have checked for previous/existing GitHub issues

Issue Type?

Question

Description

Hi

This is my scenario

I have already deployed to a client site months ago

The policies at the time were

$policies = @(
    "Alerting-Management",
    "Alerting-Connectivity",
    "Alerting-Identity",
    "Alerting-LandingZone",
    "Alerting-ServiceHealth"
)

I now want to add to that / update with the latest policies

$policies = @(
    "Alerting-ServiceHealth",
    "Alerting-HybridVM",
    "Alerting-VM",
    "Alerting-Connectivity",
    "Alerting-Identity",
    "Alerting-Management",
    "Alerting-KeyManagement",
    "Alerting-LoadBalancing",
    "Alerting-NetworkChanges",
    "Alerting-RecoveryServices",
    "Alerting-Storage",
    "Alerting-VM",
    "Alerting-Web"
)

My question is this

the notification assets are already in place so i dont want to re deploy them

I have updated the params file with my settings, but obvioulsy there are more settings in this params than there were in the previous one!

how do i do this ?

I have just tried a redeploy and i have the following ?> What does this even mean ?

Regards

Phil

PS , i guess i am just asking how do you update as more policies come out?

WARNING: The DeploymentDebug setting has been enabled. This can potentially log secrets like passwords used in resource property or listKeys operations when you retrieve the deployment operations through Get-AzResourceGroupDeploymentOperation
WARNING: 6:02:12 PM - The deployment 'ekco-amba-deployment' failed with error(s). Showing 3 out of 10 error(s).
Status Message: At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details. (Code: DeploymentFailed)

  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'networkInterfacesToInclude' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)
  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'disksToInclude' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)
  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'networkInterfacesToInclude' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)
  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'disksToInclude' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)
  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'disksToInclude' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)
  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'disksToInclude' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)
  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'disksToInclude' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)
  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'disksToInclude' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)

Status Message: At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details. (Code: DeploymentFailed)

  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'MonitorDisable' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)
  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'MonitorDisable' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)
  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'MonitorDisable' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)
  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'MonitorDisable' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)
  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'MonitorDisable' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)

Status Message: At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details. (Code: DeploymentFailed)

  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'MonitorDisable' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)
  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'MonitorDisable' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)
  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'MonitorDisable' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)
  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'MonitorDisable' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)
  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'MonitorDisable' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)
  • {
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "error": {
    "code": "InvalidPolicyParameterUpdate",
    "message": "The existing policy parameter(s) 'MonitorDisable' were not found in the policy being updated. The parameter names can not be changed."
    }
    } (Code:BadRequest)

"error": {
"code": "InvalidPolicyParameterUpdate",
"message": "The existing policy parameter(s) 'MonitorDisable' were not found in the policy being updated. The parameter names can not be changed."
}
} (Code:BadRequest)
"error": {
"code": "InvalidPolicyParameterUpdate",
"message": "The existing policy parameter(s) 'MonitorDisable' were not found in the policy being updated. The parameter names can not be changed."
"error": {
"code": "InvalidPolicyParameterUpdate",
"error": {
"error": {
"error": {
"code": "InvalidPolicyParameterUpdate",
"message": "The existing policy parameter(s) 'MonitorDisable' were not found in the policy being updated. The parameter names can not be changed."
}
} (Code:BadRequest)

CorrelationId: 8ff9e7fd-24e2-4241-b7cd-ebf82bcb6fb7
WARNING: Could not Deploy AMBA resources
@philwallerekco philwallerekco added the AMBA Core Issues / PR's related AMBA Core label Feb 19, 2025
@philwallerekco
Copy link
Author

ok so since removing "Alerting-HybridVM" from policies i now have the following

WARNING: The DeploymentDebug setting has been enabled. This can potentially log secrets like passwords used in resource property or listKeys operations when you retrieve the deployment operations through Get-AzResourceGroupDeploymentOperation
WARNING: 7:58:11 PM - The deployment 'ekco-amba-deployment' failed with error(s). Showing 3 out of 42 error(s).
Status Message: The existing policy parameter(s) 'MonitorDisable' were not found in the policy being updated. The parameter names can not be changed. (Code:InvalidPolicyParameterUpdate)

Status Message: The existing policy parameter(s) 'MonitorDisable' were not found in the policy being updated. The parameter names can not be changed. (Code:InvalidPolicyParameterUpdate)

Status Message: The existing policy parameter(s) 'MonitorDisable' were not found in the policy being updated. The parameter names can not be changed. (Code:InvalidPolicyParameterUpdate)

@Brunoga-MS Brunoga-MS added Pattern: ALZ 🚁 Issues / PR's related to the ALZ Pattern and removed AMBA Core Issues / PR's related AMBA Core labels Feb 20, 2025
@Brunoga-MS Brunoga-MS assigned Brunoga-MS and tagolovina and unassigned judyer28 Feb 20, 2025
@Brunoga-MS
Copy link
Collaborator

Hello @philwallerekco ,
thanks for your feedback. I am under the impression that the last good deployment (from months ago) is not backward compatible anymore with the new code. We have introduced some necessary breaking changes which requires to remove the existing installation. You can refer to the specific release documentation at Update to new releases. More in details, each release subpage contains the necessary pre and post action to be done when updating from the previous release. In your case I would clean up the current installation and redeploy from scratch. You can use the param file you already aligned to redeploy using the same settings.

Thanks,
Bruno.

@philwallerekco
Copy link
Author

philwallerekco commented Feb 20, 2025 via email

@Brunoga-MS
Copy link
Collaborator

Using the public repo with your own copy of the param file is perfect. You only have to fork/clone the repo if you would like to make changes to the code. If this i not necessary, then there's no need to rely on your own copy. Using the public one will also relief you from keeping the repo in sync.

Thanks,
Bruno.

@philwallerekco
Copy link
Author

philwallerekco commented Feb 20, 2025 via email

@philwallerekco
Copy link
Author

philwallerekco commented Feb 20, 2025 via email

@Brunoga-MS
Copy link
Collaborator

it does :-). to confirm: Yes you need to:

  • Remove previous installation of AMBA-ALZ pattern (the one we are talking about) using the maintenance script and the procedure documented at Clean-up AMBA-ALZ Deployment
  • Align your local copy of param file (you already did this)
  • Deploy the new version using either the main branch or the latest release (2025-02-05). The main contains some additional little enhancement and bugfix compared to the latest release. These new additions will be included in the next release.

As far as the selection goes, it is perfectly fine to deploy everything since the policies includes a check for the resource type and resource existence. If no resource of a given type is found, the policy will not create any alert. Given that, you will end up having only the alerts for the resources the customer has.

HTH,
Bruno.

@philwallerekco
Copy link
Author

philwallerekco commented Feb 20, 2025 via email

@Brunoga-MS Brunoga-MS changed the title [General workload issue]: [General workload issue]: InvalidPolicyParameterUpdate Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Brunoga-MS Brunoga-MS

@tagolovina tagolovina

Labels
Pattern: ALZ 🚁 Issues / PR's related to the ALZ Pattern
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Brunoga-MS @tagolovina @judyer28 @philwallerekco