20 Commits

Author SHA1 Message Date
05c190bb9b Fix files
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
2026-04-24 15:12:04 +03:00
d2e747880c test
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
2026-04-24 02:27:24 +03:00
1b1b9a1dfd test
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
2026-04-24 02:21:26 +03:00
d7b580c9aa test
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
2026-04-24 02:16:59 +03:00
eddad9b770 test
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
2026-04-24 02:14:46 +03:00
f3c947c9c4 test
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
2026-04-24 01:53:48 +03:00
b16aa7cc7e test
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
2026-04-24 01:46:13 +03:00
dvirlabs
1cbe3d4de7 fix: Use checksum-based content comparison to avoid permission-based drift false positives
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
CRITICAL FIX:

Problem: drift-check.yml was using 'copy' module in check_mode, which compares:
  - File content ✓
  - Permissions (owner, group, mode) ✗
  - Ownership ✗

After deploy, files have root:root 0644 permissions. Even though content matches,
the copy module marked files as 'changed' because permissions were being compared.
This caused false OUT_OF_SYNC reports even when configuration was actually synced.

Solution: Use MD5 checksum-based comparison instead:
  - Compare only file CONTENT using stat checksums
  - Ignore permissions/ownership differences
  - This is what matters for config management

Also fixed URLs:
  - Changed back from port 80 to port 5000 (API only)
  - Updated service name to gitops-status-api

Now drift detection only triggers on actual config changes, not permission differences.
After successful deploy, should correctly report SYNCED status.
2026-04-23 13:21:20 +03:00
dvirlabs
06827001e6 Ajust the pipeline to the new api
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
2026-04-23 12:50:46 +03:00
dvirlabs
5285f4c241 debug: Add comprehensive debugging for drift detection and JSON POSTing
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
- Add debug output showing rsyslogd_check.diff structure
- Simplify file extraction logic for rsyslog.d directory changes
- Show full JSON payload before sending to API
- Add connectivity test to gitops-status-server before POST
- Show curl command and response codes for debugging
- Display warning if OUT_OF_SYNC but no files extracted

This helps diagnose why drift is detected but files aren't listed in the JSON.
2026-04-23 11:52:32 +03:00
dvirlabs
cdec5ce87c Debug api request
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
2026-04-23 11:40:17 +03:00
e8fed366b4 test
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
2026-04-23 00:35:03 +03:00
e500e21fab fix: resolve OUT_OF_SYNC and empty files array issues
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
Root causes:
1. Inconsistent Ansible callback (minimal) broke debug output parsing
2. DRIFTED_FILES extraction failed due to format changes
3. Files array stayed empty even when drift was detected

Fixes:
1. Use YAML callback for consistent, structured output
2. Improve DRIFTED_FILES parsing to handle YAML format
3. Remove conflicting ANSIBLE_CALLBACKS_ENABLED/minimal settings
4. Add GITOPS_STATUS_FIX.md with complete analysis

Result:
- Files array now populates correctly when drift exists
- Sync status accurately reflects actual server state
- Better debug logging for troubleshooting

See GITOPS_STATUS_FIX.md for full root cause analysis and testing guide.
2026-04-22 23:46:14 +03:00
654259c7cd test
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
2026-04-22 22:56:11 +03:00
8e54f82e12 Fix update-gitops-status
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
2026-04-22 22:46:18 +03:00
dvirlabs
fc8cb0c40e fix: Resolve 'too many open files' error in pipeline
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
- Remove -v verbose flag from ansible-playbook (was causing file descriptor exhaustion)
- Add recurse: false to find tasks (prevents recursive directory traversal)
- Set ulimit -n 4096 in Woodpecker container to increase FD limit
- Add ANSIBLE_* environment variables for container optimization:
  - ANSIBLE_HOST_KEY_CHECKING=False (skip SSH key verification)
  - ANSIBLE_CALLBACK_WHITELIST=minimal (reduce output verbosity)
  - ANSIBLE_FORCE_COLOR=False (no ANSI color codes)
  - ANSIBLE_RETRY_FILES_ENABLED=False (don't create retry files)

This resolves fsnotify watcher errors in container environments with low FD limits.
2026-04-22 21:54:00 +03:00
dvirlabs
f926b7eb0d Update drift-check to let the pipeline update also what files changed
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
2026-04-22 21:50:39 +03:00
dvirlabs
1bac032155 Fix: Enhanced error reporting and response verification in update-gitops-status.sh
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
- Capture and display full curl response body for debugging
- Add verification step to confirm JSON was stored on server
- Improve error messages with connectivity troubleshooting hints
2026-04-21 12:46:41 +03:00
dvirlabs
db28c9da82 Migrate from pushgateway to infinity
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
2026-04-21 12:41:09 +03:00
082ed0a0a4 Migrate to infinity datasource
Some checks failed
ci/woodpecker/cron/woodpecker Pipeline failed
ci/woodpecker/push/woodpecker Pipeline failed
2026-04-21 04:54:47 +03:00