Activity log for bug #2074017

Date Who What changed Old value New value Message
2024-07-24 19:53:10 Ethan Myers bug added bug
2024-07-24 19:53:10 Ethan Myers attachment added debug.log https://bugs.launchpad.net/bugs/2074017/+attachment/5800020/+files/debug.log
2024-07-24 19:53:25 Ethan Myers bug added subscriber Canonical Field High
2024-07-24 19:53:48 Ethan Myers description Hi, I am unable to get Postgresql to initialize. The issue shows up as postgresql units never finishing the "agent initializing" step in juju. In the debug-log, I see a complaint about the charm not being found on disk. Sometimes, I also get a message about a Sha256 length 0 being not valid. This does not happen with older revisions of the charm, and the environment has wide-open network connectivity. Other charms initialize fine. I am using PostgreSQL charm as part of a Landscape deployment. The bundle is attached. I did not have this issue with a previous charm revision (345). Happy to provide any more details. Hi, I am unable to get Postgresql to initialize. The issue shows up as postgresql units never finishing the "agent initializing" step in juju. In the debug-log, I see a complaint about the charm not being found on disk. Sometimes, I also get a message about a Sha256 length 0 being not valid. This does not happen with older revisions of the charm, and the environment has wide-open network connectivity. Other charms initialize fine. I am using PostgreSQL charm as part of a Landscape deployment. The bundle is attached. I did not have this issue with a previous charm revision (345). Happy to provide any more details as needed
2024-07-24 19:54:18 Ethan Myers description Hi, I am unable to get Postgresql to initialize. The issue shows up as postgresql units never finishing the "agent initializing" step in juju. In the debug-log, I see a complaint about the charm not being found on disk. Sometimes, I also get a message about a Sha256 length 0 being not valid. This does not happen with older revisions of the charm, and the environment has wide-open network connectivity. Other charms initialize fine. I am using PostgreSQL charm as part of a Landscape deployment. The bundle is attached. I did not have this issue with a previous charm revision (345). Happy to provide any more details as needed Hello, I am unable to get Postgresql (rev 429) to initialize when deploying the charm with juju. The issue shows up as postgresql units never finishing the "agent initializing" step in juju. In the debug-log, I see a complaint about the charm not being found on disk. Sometimes, I also get a message about a Sha256 length 0 being not valid. This does not happen with older revisions of the charm, and the environment has wide-open network connectivity. Other charms initialize fine. I am using PostgreSQL charm as part of a Landscape deployment. The bundle is attached. I did not have this issue with a previous charm revision (345). Happy to provide any more details as needed
2024-07-24 19:54:38 Ethan Myers description Hello, I am unable to get Postgresql (rev 429) to initialize when deploying the charm with juju. The issue shows up as postgresql units never finishing the "agent initializing" step in juju. In the debug-log, I see a complaint about the charm not being found on disk. Sometimes, I also get a message about a Sha256 length 0 being not valid. This does not happen with older revisions of the charm, and the environment has wide-open network connectivity. Other charms initialize fine. I am using PostgreSQL charm as part of a Landscape deployment. The bundle is attached. I did not have this issue with a previous charm revision (345). Happy to provide any more details as needed Hello, I am unable to get Postgresql (rev 429) to initialize when deploying the charm with juju. The issue shows up as postgresql units never finishing the "agent initializing" step in juju. In the debug-log, I see a complaint about the charm not being found on disk. Sometimes, I also get a message about a Sha256 length 0 being not valid. Please see the attached debug.log for one example. This does not happen with older revisions of the charm, and the environment has wide-open network connectivity. Other charms initialize fine. I am using PostgreSQL charm as part of a Landscape deployment. The bundle is attached. I did not have this issue with a previous charm revision (345). Happy to provide any more details as needed
2024-07-24 19:57:01 Ethan Myers attachment added bundle2.yaml https://bugs.launchpad.net/postgresql-charm/+bug/2074017/+attachment/5800021/+files/bundle2.yaml
2024-07-24 20:00:18 Ethan Myers attachment added bundle2.yaml https://bugs.launchpad.net/postgresql-charm/+bug/2074017/+attachment/5800022/+files/bundle2.yaml
2024-07-24 20:54:55 Billy Olsen bug task added juju
2024-07-24 21:18:35 Ethan Myers attachment added bundle2.yaml https://bugs.launchpad.net/postgresql-charm/+bug/2074017/+attachment/5800052/+files/bundle2.yaml
2024-07-25 07:44:42 Peter Jose De Sousa bug added subscriber Canonical Field Critical
2024-07-25 08:52:10 Joseph Phillips juju: status New Incomplete
2024-07-25 09:42:52 Nobuto Murata bug watch added https://github.com/canonical/postgresql-operator/issues/548
2024-07-25 10:53:12 Alex Lutay bug watch added https://github.com/canonical/postgresql-operator/issues/354
2024-07-25 13:19:19 Jeff Hillman bug added subscriber Jeff Hillman
2024-07-25 15:13:55 Alex Lutay bug watch added https://github.com/canonical/maas-anvil/issues/9
2024-07-25 19:21:29 Ethan Myers summary Postgresql charm fails to initialize (rev 429)_ Postgresql charm fails to initialize (rev 429)
2024-07-25 19:53:32 Ethan Myers removed subscriber Canonical Field High
2024-07-25 23:58:04 Billy Olsen removed subscriber Canonical Field Critical
2024-07-25 23:58:39 Billy Olsen postgresql-charm: status New Invalid