You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The charm added an overlay repository to offer a newer version of the software on top of what Ubuntu archive offers (ovn 20.03 in Ubuntu focal vs 22.03 in Cloud Archive repository).
However, the following warnings were recorded but the charm-helper code allowed the charm to move o n and install the software with an old version using the default Ubuntu archive.
2024-08-17 03:38:04 WARNING unit.ovn-chassis-dpdk/0.install logger.go:60 W: Failed to fetch http://ubuntu-cloud.archive.canonical.com/ubuntu/dists/focal-updates/ovn-22.03/InRelease 503 Service Unavailable [IP: 192.168.11.12 8000]
2024-08-17 03:38:04 WARNING unit.ovn-chassis-dpdk/0.install logger.go:60 W: Some index files failed to download. They have been ignored, or old ones used instead.
The expected behavior is the code should error out there and let the helper or charm retry the operation or simply wait an error resolution with an human intervention.
The text was updated successfully, but these errors were encountered:
nobuto-m
changed the title
apt_install W: Some index files failed to download. They have been ignored, or old ones used instead shouldn't be ignored
apt_update W: Some index files failed to download. They have been ignored, or old ones used instead shouldn't be ignored
Aug 19, 2024
nobuto-m
added a commit
to nobuto-m/charm-helpers
that referenced
this issue
Aug 19, 2024
APT doesn't error out even in the following case since it's a warning
instead of an error. And it allows charms to move on without having a
proper APT index and let them install unwanted versions of software for
example. The apt_update part should fail if it's marked as fatal in such
cases so that it can be retried or charm can raise it as an error to
users appropriately.
"--error-on=any" is supported for >= bionic.
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900Closes: juju#910
[w/o "--error-on=any"]
```
$ sudo apt-get update; echo $?
...
Err:2 http://security.ubuntu.com/ubuntu jammy-security InRelease
Could not connect to squid-deb-proxy.lxd:8000 (10.0.8.2).
- connect (113: No route to host)
Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Could not connect to squid-deb-proxy.lxd:8000 (10.0.8.2).
- connect (113: No route to host)
Err:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Unable to connect to squid-deb-proxy.lxd:8000:
Err:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Unable to connect to squid-deb-proxy.lxd:8000:
Reading package lists... Done
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease
Could not connect to squid-deb-proxy.lxd:8000 (10.0.8.2).
- connect (113: No route to host)
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease
Unable to connect to squid-deb-proxy.lxd:8000:
...
W: Some index files failed to download. They have been ignored, or old ones used instead.
```
-> 0
[w/ "--error-on=any"]
```
$ sudo apt-get --error-on=any update; echo $?
...
E: Some index files failed to download. They have been ignored, or old ones used instead.
```
-> 100
For example in https://bugs.launchpad.net/charm-ovn-chassis/+bug/2070332/comments/19
The charm added an overlay repository to offer a newer version of the software on top of what Ubuntu archive offers (ovn 20.03 in Ubuntu focal vs 22.03 in Cloud Archive repository).
However, the following warnings were recorded but the charm-helper code allowed the charm to move o n and install the software with an old version using the default Ubuntu archive.
The expected behavior is the code should error out there and let the helper or charm retry the operation or simply wait an error resolution with an human intervention.
The text was updated successfully, but these errors were encountered: