Dependency issues on upgrade to 8.3

[flam22]

On upgrading from 8.2 to 8.3, I see dependency issues with postfix and ssl-cert when attempting to start the zulip container.

Note: I am using podman-compose to run the containers but it did work previously using 8.2

[zulip]     | Notice: /Stage[main]/Zulip::App_frontend_base/File[/etc/nginx/zulip-include/s3-cache]/content: content changed '{md5}4c5e8545edbe940dfd82a6d2d98fbb0f' to '{md5}ff74cd0dd112933d9901fe72f4436891'
[zulip]     | Notice: /Stage[main]/Zulip::Nginx/Service[nginx]: Triggered 'refresh' from 1 event
[zulip]     | Notice: /Stage[main]/Zulip::Postfix_localmail/File[/etc/mailname]/ensure: defined content as '{md5}729a8ddede65e9a345b5fa0fc7c7adfd'
Error: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install postfix' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
Package postfix is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'postfix' has no installation candidate
Error: /Stage[main]/Zulip::Postfix_localmail/Package[postfix]/ensure: change from 'purged' to 'present' failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install postfix' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
Package postfix is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'postfix' has no installation candidate
[zulip]     | Notice: /Stage[main]/Zulip::Postfix_localmail/File[/etc/postfix/main.cf]: Dependency Package[postfix] has failures: true
Warning: /Stage[main]/Zulip::Postfix_localmail/File[/etc/postfix/main.cf]: Skipping because of failed dependencies
Warning: /Stage[main]/Zulip::Postfix_localmail/File[/etc/postfix/master.cf]: Skipping because of failed dependencies
Warning: /Stage[main]/Zulip::Postfix_localmail/File[/etc/postfix/virtual]: Skipping because of failed dependencies
Warning: /Stage[main]/Zulip::Postfix_localmail/File[/etc/postfix/transport]: Skipping because of failed dependencies
Warning: /Stage[main]/Zulip::Postfix_localmail/Exec[postmap /etc/postfix/transport]: Skipping because of failed dependencies
Warning: /Stage[main]/Zulip::Postfix_localmail/File[/etc/postfix/access]: Skipping because of failed dependencies
Error: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install ssl-cert' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
Package ssl-cert is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'ssl-cert' has no installation candidate
Error: /Stage[main]/Zulip::Snakeoil/Zulip::Safepackage[ssl-cert]/Package[ssl-cert]/ensure: change from 'purged' to 'present' failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install ssl-cert' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
Package ssl-cert is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'ssl-cert' has no installation candidate
[zulip]     | Notice: /Stage[main]/Zulip::Snakeoil/Exec[generate-default-snakeoil]: Dependency Package[ssl-cert] has failures: true
Warning: /Stage[main]/Zulip::Snakeoil/Exec[generate-default-snakeoil]: Skipping because of failed dependencies
Warning: /Stage[main]/Zulip::Postfix_localmail/Service[postfix]: Skipping because of failed dependencies
[zulip]     | Notice: Applied catalog in 0.44 seconds
exit code: 2

[timabbott]

I've not seen this failure mode before. I don't see how these packages would have no installation candidate unless the Dockerfile was modified to delete files that are included in our upstream image. Did you run some sort of image optimizer that might have deleted apt data files or something? In any case, I doubt we'll be able to reproduce this. Please report a new issue if you're able to reproduce a problem with the current container.