Open miceiken opened 1 month ago
Hi @miceiken Find similar issue https://github.com/Azure/azure-cli/issues/22235. | ||
---|---|---|
Issue title | Storage commands failling on Fedora 35 when Python 3.6 is not present | |
Create time | 2022-04-29 | |
Comment number | 7 |
Possible solution:
It seems that the error message you are seeing is related to a missing package libpython3.6m.so.1.0()(64bit)
which is not included in the RPM's requirement since 2.35.0. One workaround is to specify python36
in the RPM's requirement. Another workaround is to install Azure CLI using pip instead of RPM.
However, since Python 3.6 is now deprecated, the better solution is to build RPMs with the latest Fedora. You can use dnf
command to query the package contents.
Please confirm if this resolves your issue.
Thank you for opening this issue, we will look into it.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @calvinsID.
Hi @miceiken Find similar issue #22235.
Issue title Storage commands failling on Fedora 35 when Python 3.6 is not present Create time 2022-04-29 Comment number 7 Possible solution: It seems that the error message you are seeing is related to a missing package
libpython3.6m.so.1.0()(64bit)
which is not included in the RPM's requirement since 2.35.0. One workaround is to specifypython36
in the RPM's requirement. Another workaround is to install Azure CLI using pip instead of RPM.However, since Python 3.6 is now deprecated, the better solution is to build RPMs with the latest Fedora. You can use
dnf
command to query the package contents.Please confirm if this resolves your issue.
This does not seem related.
Hi @miceiken Thanks for reporting this issue, I will take a look.
May I ask what this the result when you execute this command:
az containerapp env show -n {env-name} -g {rg} --query "properties.workloadProfiles"
Thanks
Hi @miceiken I have checked this error. This is due to your managed environment is not an environment that enable workload profiles. We don't support adding workload profiles for an environment that doesn't enable workload profiles. The existing environment which not enable workload profiles also not support change to enable.
You can create a new environment enable workload-profiles with following command:
az containerapp env create -g {} -n {} --location {} --logs-destination none --enable-workload-profiles
I will create a PR to give a more friendly message for this issue.
Thanks
Describe the bug
Adding a workload profile to existing Container Apps Environment fails
Related command
Errors
Issue script & Debug output
😉
Expected behavior
A workload profile is created and added to the Container Apps Environment.
Environment Summary
Additional context
No response