# snap changes
ID Status Spawn Ready Summary
1 Done today at 10:40 UTC today at 10:40 UTC Initialize system state
2 Done today at 10:41 UTC today at 10:41 UTC Change configuration of "core" snap
3 Done today at 10:42 UTC today at 10:42 UTC Change configuration of "core" snap
4 Error today at 10:42 UTC today at 10:44 UTC Install "core" snap
5 Done today at 10:42 UTC today at 10:42 UTC Initialize device
# snap tasks 4
Status Spawn Ready Summary
Done today at 10:42 UTC today at 10:44 UTC Ensure prerequisites for "core" are available
Undone today at 10:42 UTC today at 10:44 UTC Download snap "core" (7270) from channel "stable"
Error today at 10:42 UTC today at 10:44 UTC Fetch and check assertions for snap "core" (7270)
Hold today at 10:42 UTC today at 10:44 UTC Mount snap "core" (7270)
Hold today at 10:42 UTC today at 10:44 UTC Copy snap "core" data
Hold today at 10:42 UTC today at 10:44 UTC Setup snap "core" (7270) security profiles
Hold today at 10:42 UTC today at 10:44 UTC Make snap "core" (7270) available to the system
Hold today at 10:42 UTC today at 10:44 UTC Automatically connect eligible plugs and slots of snap "core"
Hold today at 10:42 UTC today at 10:44 UTC Set automatic aliases for snap "core"
Hold today at 10:42 UTC today at 10:44 UTC Setup snap "core" aliases
Hold today at 10:42 UTC today at 10:44 UTC Run install hook of "core" snap if present
Hold today at 10:42 UTC today at 10:44 UTC Start snap "core" (7270) services
Hold today at 10:42 UTC today at 10:44 UTC Run configure hook of "core" snap if present
......................................................................
Fetch and check assertions for snap "core" (7270)
2019-08-12T10:44:36Z ERROR cannot get nonce from store: store server returned status 503
The timestamps coincide with the charm log and gives a plausible reason for the failure.
However I must maintain that I do not think we can sustain this as a one-shot-to success type of transaction for the charm/layer and should add some resilience here.
Just to add some flavor to what's going on:
# snap changes
ID Status Spawn Ready Summary
1 Done today at 10:40 UTC today at 10:40 UTC Initialize system state
2 Done today at 10:41 UTC today at 10:41 UTC Change configuration of "core" snap
3 Done today at 10:42 UTC today at 10:42 UTC Change configuration of "core" snap
4 Error today at 10:42 UTC today at 10:44 UTC Install "core" snap
5 Done today at 10:42 UTC today at 10:42 UTC Initialize device
# snap tasks 4
Status Spawn Ready Summary
Done today at 10:42 UTC today at 10:44 UTC Ensure prerequisites for "core" are available
Undone today at 10:42 UTC today at 10:44 UTC Download snap "core" (7270) from channel "stable"
Error today at 10:42 UTC today at 10:44 UTC Fetch and check assertions for snap "core" (7270)
Hold today at 10:42 UTC today at 10:44 UTC Mount snap "core" (7270)
Hold today at 10:42 UTC today at 10:44 UTC Copy snap "core" data
Hold today at 10:42 UTC today at 10:44 UTC Setup snap "core" (7270) security profiles
Hold today at 10:42 UTC today at 10:44 UTC Make snap "core" (7270) available to the system
Hold today at 10:42 UTC today at 10:44 UTC Automatically connect eligible plugs and slots of snap "core"
Hold today at 10:42 UTC today at 10:44 UTC Set automatic aliases for snap "core"
Hold today at 10:42 UTC today at 10:44 UTC Setup snap "core" aliases
Hold today at 10:42 UTC today at 10:44 UTC Run install hook of "core" snap if present
Hold today at 10:42 UTC today at 10:44 UTC Start snap "core" (7270) services
Hold today at 10:42 UTC today at 10:44 UTC Run configure hook of "core" snap if present
....... ....... ....... ....... ....... ....... ....... ....... ....... .......
Fetch and check assertions for snap "core" (7270)
2019-08- 12T10:44: 36Z ERROR cannot get nonce from store: store server returned status 503
The timestamps coincide with the charm log and gives a plausible reason for the failure.
However I must maintain that I do not think we can sustain this as a one-shot-to success type of transaction for the charm/layer and should add some resilience here.