panic resulted in: runtime error: invalid memory address or nil pointer dereference

Bug #1896749 reported by Guillermo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
High
Unassigned

Bug Description

After a change of the image of the charms with "juju config image=.." command, the units with the previous image were not deleted. I found the error in the logs below in juju debug-log:

https://pastebin.canonical.com/p/4S7c6MGBzs/

Juju status is the following:

ubuntu@client-osm:~$ juju status ng-ui
Model Controller Cloud/Region Version SLA Timestamp
osm manual-controller k8s-cloud/localhost 2.8.3 unsupported 10:56:57Z

App Version Status Scale Charm Store Rev OS Address Notes
ng-ui ngui:develop active 2 ng-ui jujucharms 7 kubernetes 10.152.183.97 exposed

Unit Workload Agent Address Ports Message
ng-ui/0 terminated failed 10.1.39.157 80/TCP unit stopped by the cloud
ng-ui/1 terminated failed 10.1.147.94 80/TCP unit stopped by the cloud
ng-ui/2 terminated failed 10.1.21.94 80/TCP unit stopped by the cloud
ng-ui/5* active idle 10.1.21.121 80/TCP ready
ng-ui/6 active idle 10.1.39.169 80/TCP ready

Tags: k8s
Revision history for this message
Guillermo (gcalvino) wrote :

Please, find the logs from the operator pod:

https://pastebin.canonical.com/p/bWvSdVyzK2/

Revision history for this message
Ian Booth (wallyworld) wrote :

Adding to 2.8.4 but will likely get bumped to 2.8.5

tags: added: k8s
Changed in juju:
milestone: none → 2.8.4
importance: Undecided → High
status: New → Triaged
Revision history for this message
Ian Booth (wallyworld) wrote :

Can you provide a link to teh charm? Often this sort of problem comes up when the charm has a bug causing it to send in new pod specs continually. A new pod spec results in a rolling update of the existing pods; the terminated pods are what juju shows as terminated units. These should get cleaned up but ir could be the nil pointer is stopping that from happening. The charm might be perfectly ok, but a link to it would help diagnose the issue. Regardless of any problem which may or may not exist with the charm, juju should not be having a nil pointer error.

Changed in juju:
milestone: 2.8.4 → 2.8.5
Changed in juju:
milestone: 2.8.5 → 2.8.6
Revision history for this message
Ian Booth (wallyworld) wrote :

This might be fixed in https://github.com/juju/juju/pull/12120
Will mark as Incomplete and can reopen if the problem comes back with the above PR landed.

Changed in juju:
status: Triaged → Incomplete
Changed in juju:
milestone: 2.8.6 → 2.8.7
Pen Gale (pengale)
Changed in juju:
milestone: 2.8.7 → none
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for juju because there has been no activity for 60 days.]

Changed in juju:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.