Automated Velero version update 1.17.2#5800
Conversation
replicated-ci-kurl
added
automated-pr
kurl::type::feature
replicated-ci-kurl
force-pushed
the
automation/update-velero
branch
2 times, most recently
from
f569954 to
3339f48
Compare
replicated-ci-kurl
force-pushed
the
automation/update-velero
branch
from
3339f48 to
c3d5fa5
Compare
replicated-ci-kurl
force-pushed
the
automation/update-velero
branch
from
c3d5fa5 to
f8a038a
Compare
replicated-ci-kurl
force-pushed
the
automation/update-velero
branch
2 times, most recently
from
75e98ee to
a71a6a9
Compare
replicated-ci-kurl
force-pushed
the
automation/update-velero
branch
from
a71a6a9 to
174e888
Compare
replicated-ci-kurl
changed the title
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5800-f3bd7e1-velero-1.17.1-k8s-docker-2025-11-12T01:39:41Z |
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5800-bc0875b-velero-1.17.1-k8s-docker-2025-11-12T06:09:52Z |
|
tesgrid is failed at test using the backup is failed to create due to Name: default-default-kopia
Namespace: velero
Labels: velero.io/repository-type=kopia
velero.io/storage-location=default
velero.io/volume-namespace=default
Annotations: <none>
API Version: velero.io/v1
Kind: BackupRepository
Metadata:
Creation Timestamp: 2025-11-14T02:43:06Z
Generation: 3
Resource Version: 3434
UID: f73e4126-241b-4a32-a8eb-59a773508253
Spec:
Backup Storage Location: default
Maintenance Frequency: 1h0m0s
Repository Type: kopia
Volume Namespace: default
Status:
Message: error to get repo options: error to get storage variables: invalid storage provider
Phase: NotReady
Events: <none> |
replicated-ci-kurl
force-pushed
the
automation/update-velero
branch
from
486c7d8 to
0fd3664
Compare
replicated-ci-kurl
force-pushed
the
automation/update-velero
branch
from
0fd3664 to
2021242
Compare
replicated-ci-kurl
force-pushed
the
automation/update-velero
branch
from
2021242 to
e6c1c95
Compare
replicated-ci-kurl
force-pushed
the
automation/update-velero
branch
2 times, most recently
from
8d25fad to
c23cdac
Compare
replicated-ci-kurl
force-pushed
the
automation/update-velero
branch
from
c23cdac to
4b6cf86
Compare
replicated-ci-kurl
force-pushed
the
automation/update-velero
branch
from
4b6cf86 to
9c68b3d
Compare
replicated-ci-kurl
changed the title
replicated-ci-kurl
force-pushed
the
automation/update-velero
branch
from
9c68b3d to
447c300
Compare
replicated-ci-kurl
force-pushed
the
automation/update-velero
branch
from
447c300 to
16b9c1b
Compare
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5800-91412ef-velero-1.17.2-k8s-docker-2026-04-28T07:31:04Z |
xavpaice
force-pushed
the
automation/update-velero
branch
from
b158f6d to
acb1fc9
Compare
|
Reviews (1): Last reviewed commit: "update for Velero with kopia" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5800-6ac327a-velero-1.17.2-k8s-docker-2026-06-30T08:07:08Z |
|
Reviews (2): Last reviewed commit: "fixup velero tests" | Re-trigger Greptile |
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5800-5377154-velero-1.17.2-k8s-docker-2026-06-30T21:24:07Z |
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5800-d388571-velero-1.17.2-k8s-docker-2026-07-02T22:00:35Z |
|
Reviews (3): Last reviewed commit: "rework velero tests" | Re-trigger Greptile |
|
TODO: we need some logic to prevent folks from upgrading from 1.16 if the LVP is in use (and therefore backups would be broken). |
|
Too many files changed for review. ( Bypass the limit by tagging |
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5800-af6bc38-velero-1.17.2-k8s-docker-2026-07-03T01:03:42Z |
Non-interactive environments such as cloud-init and piped shells may have a /dev/tty character device node without a controlling terminal. The previous prompts_can_prompt() only checked that the node existed, so it returned true in Testgrid VMs and then the read from /dev/tty failed with ENODEV, aborting the installer when a preflight warning (e.g. NTP) was shown. Now verify that /dev/tty can actually be opened for reading before deciding we can prompt. This restores the auto-accept behavior in non-interactive runs while still allowing prompts when /dev/tty is usable (e.g. interactive terminal with log redirection).
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-5800-a10fab6-velero-1.17.2-k8s-docker-2026-07-03T03:48:18Z |
4 participants
Automated changes by the cron-velero-update GitHub action
[sc-138665]