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
Describe the bug
Not sure if this is a bug or user error, but it seems that zincati is not upgrading the system and getting a 502 error. The server hasn't been updated for 11 days now. Possbile that the server is indeed not available or I made a mistake in the zincati config. Not even sure if this is the right platform to post this anymore so I apologize in advance.
systemctl status zincati.service
● zincati.service - Zincati Update Agent
Loaded: loaded (/usr/lib/systemd/system/zincati.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-01-19 16:12:44 UTC; 1 week 4 days ago
Docs: https://github.com/coreos/zincati
Main PID: 835 (zincati)
Status: "periodically polling for updates (last checked Mon 2022-01-31 05:31:53 UTC)"
Tasks: 4 (limit: 4592)
Memory: 14.1M
CPU: 49.441s
CGroup: /system.slice/zincati.service
└─835 /usr/libexec/zincati agent -v
Jan 19 16:12:41 kimera zincati[835]: [INFO zincati::cli::agent] agent running on node 'e0bbf17e0b8b4dd1bce88c44696ef946', in update group 'default'
Jan 19 16:12:41 kimera zincati[835]: [INFO zincati::update_agent::actor] registering as the update driver for rpm-ostree
Jan 19 16:12:44 kimera zincati[835]: [INFO zincati::update_agent::actor] found 1 other finalized deployment
Jan 19 16:12:44 kimera zincati[835]: [INFO zincati::update_agent::actor] deployment 35.20211215.3.0 (30c82ee684674b9a552ffee709501f981f35f36408085f089686e43b09aeca1b) will be excluded from being a future update target
Jan 19 16:12:44 kimera zincati[835]: [INFO zincati::update_agent::actor] initialization complete, auto-updates logic enabled
Jan 19 16:12:44 kimera zincati[835]: [INFO zincati::strategy] update strategy: immediate
Jan 19 16:12:44 kimera systemd[1]: Started Zincati Update Agent.
Jan 19 16:12:44 kimera zincati[835]: [INFO zincati::update_agent::actor] reached steady state, periodically polling for updates
Jan 19 16:12:46 kimera zincati[835]: [INFO zincati::cincinnati] current release detected as not a dead-end
Jan 27 15:25:15 kimera zincati[835]: [ERROR zincati::cincinnati] failed to check Cincinnati for updates: server-side error, code 502: (unknown/generic server error)
As we speak, the latest FCOS stable version is 35.20220103.3.0, which your node is currently running.
Last Zincati check from the status is timestamped Mon 2022-01-31 05:44:38 UTC, which is a few minutes before this ticket timestamp.
Additionally, the node has a 35.20211215.3.0 rollback deployment, so it seems it successfully upgraded from the previous stable release. Last logged backend error is from 2022-01-27, which was 4 days ago.
This node auto-updates seem healthy to me from the logs you provided, but you can double-check your service metrics monitoring to make sure of that.
Hey @lucab, big thanks for your guidance on the matter. I guess I overreacted a bit then ^-^
Going to keep a close eye on this matter and report back if anything actually goes wrong. Sorry for wasting your time.
Describe the bug
Not sure if this is a bug or user error, but it seems that
zincati
is not upgrading the system and getting a 502 error. The server hasn't been updated for 11 days now. Possbile that the server is indeed not available or I made a mistake in thezincati
config. Not even sure if this is the right platform to post this anymore so I apologize in advance.Reproduction steps
Steps to reproduce the behavior:
ignition
file,zincati
Expected behavior
zincati
should pull the update, stage the new deployment and reboot the box immediately.Actual behavior
zincati
runs into a 502 error and unable to execute the update procedure.System details
Ignition config
Users and public keys are deleted, everything else is valid. Posting the
butane
config as well.Additional information
N/A
The text was updated successfully, but these errors were encountered: