Open lego290 opened 1 year ago
Thank you for opening this issue, we will look into it.
Hi @lego290 Find similar issue https://github.com/Azure/azure-cli/issues/16493. | ||
---|---|---|
Issue title | az sig image-version create fails | |
Create time | 2021-01-11 | |
Comment number | 9 |
Possible solution:
The error message "'NoneType' object is not subscriptable" is a common error message that can occur in different commands. In the past, this error message has been reported in the az sig image-version create
command. The issue was fixed in version 2.18.0 of the Azure CLI. However, if you cannot upgrade to the latest version, you can try downgrading to version 2.14.2-1~xenial.
Please confirm if this resolves your issue.
We are running version 2.52.0 of the cli, and are using the containerapp extension instead of the sig extension. So this doesn't seem related.
After some more investigation we have found that this issue happens for two of our container apps, both in the same environment. We also see that they are completely unresponsive to http requests, and are not logging any output to the console.
Just in case it is relevant, when accessing these apps in the management portal we recieve a timeout error on the pages overview, revisions, secrets, ingress, log stream and console, most of the other pages just show a blank screen, or are permanently stuck loading. The following error is logged to the browser console twice when we try to access these pages:
sandbox-66-2.reactblade.portal.azure.net/React/Index?reactView=true&l=en.en-us&trustedAuthority=https://portal.azure.com&contentHash=gVfAebUPAG9f&reactIndex=0&sessionId=cb88dcf2874a41809e3185cd3cfff1b8#postParams/:1 Uncaught (in promise) TypeError: Cannot convert undefined or null to object
at RpzdpBkAv9ow.js:3:1013
Promise.then (async)
(anonymous) @ oVfK0qpKi4aI.js:2
Hr @ 3KsPtNwXSeTh.js:62
unstable_runWithPriority @ 3KsPtNwXSeTh.js:52
St @ 3KsPtNwXSeTh.js:62
Wr @ 3KsPtNwXSeTh.js:62
Pr @ 3KsPtNwXSeTh.js:62
(anonymous) @ 3KsPtNwXSeTh.js:62
unstable_runWithPriority @ 3KsPtNwXSeTh.js:52
St @ 3KsPtNwXSeTh.js:62
Tt @ 3KsPtNwXSeTh.js:62
_t @ 3KsPtNwXSeTh.js:62
Nr @ 3KsPtNwXSeTh.js:62
yo @ 3KsPtNwXSeTh.js:62
e.render @ 3KsPtNwXSeTh.js:62
(anonymous) @ XzLyfUGUC043.js:12
(anonymous) @ XzLyfUGUC043.js:82
(anonymous) @ XzLyfUGUC043.js:82
(anonymous) @ 3KsPtNwXSeTh.js:16
(anonymous) @ 3KsPtNwXSeTh.js:16
a @ 3KsPtNwXSeTh.js:16
Promise.then (async)
u @ 3KsPtNwXSeTh.js:16
(anonymous) @ 3KsPtNwXSeTh.js:16
__awaiter @ 3KsPtNwXSeTh.js:16
e.renderNodeIntoRoot @ XzLyfUGUC043.js:82
(anonymous) @ XzLyfUGUC043.js:82
(anonymous) @ 3KsPtNwXSeTh.js:16
(anonymous) @ 3KsPtNwXSeTh.js:16
(anonymous) @ 3KsPtNwXSeTh.js:16
__awaiter @ 3KsPtNwXSeTh.js:16
e.renderComponentIntoRoot @ XzLyfUGUC043.js:82
u @ uRtaABX5DcBx.js:10
(anonymous) @ uRtaABX5DcBx.js:10
t @ 8U0-tHo9b49u.js:1
(anonymous) @ 8U0-tHo9b49u.js:1
he @ 8U0-tHo9b49u.js:1
a @ 8U0-tHo9b49u.js:1
Promise.then (async)
Ce @ 8U0-tHo9b49u.js:1
r @ 8U0-tHo9b49u.js:1
ii @ uRtaABX5DcBx.js:10
rt @ uRtaABX5DcBx.js:10
ut.then.e.<computed>.onmessage @ uRtaABX5DcBx.js:11
(anonymous) @ uRtaABX5DcBx.js:11
Promise.then (async)
e.<computed>.onmessage @ uRtaABX5DcBx.js:11
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @calvinsID.
Describe the bug
While trying to update one of our container apps we recieve an error.
The container app in question is located in swedencentral, and if going by the output of
az containerapp list
should be in the 'Failed' provisioning state.Related command
az containerapp update -g *** -n *** -i ***.azurecr.io/***
Errors
Issue script & Debug output
Expected behavior
We would expect this command to update the image the container app is using successfully
Environment Summary
azure-cli 2.52.0
core 2.52.0 telemetry 1.1.0
Extensions: containerapp 0.3.39 resource-graph 2.1.0
Dependencies: msal 1.24.0b1 azure-mgmt-resource 23.1.0b2
Python location '/opt/az/bin/python3' Extensions directory '/home/***/.azure/cliextensions'
Python (Linux) 3.10.10 (main, Aug 31 2023, 09:13:53) [GCC 11.4.0]
Additional context
The container app we are trying to update is the following: