Bug - setup-requirements.sh #4
Labels
No labels
bug
duplicate
enhancement
good first issue
help wanted
invalid
question
todo
todo 🗒️
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: stationgroup/ansible-experiments#4
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Ubuntu BugsMIGHT HAVE FIXED THIS
ubuntu1 fails at this step every time untilapt update
is run.setup-requirements
should runapt update
first on Ubuntu systems (maybepkg update
on FreeBSD too?).Once you get past the first bug by running
apt update
, ansible will say it failed again durring the python pip step.This "failure" stops the Ansible script from progressing. But when you run
./setup-requirements
again, it obviously succeeded.FreeBSD Bugs
I think the ansible playbook fails when
pkg upgrade --dry-run
comes back with updates, rather than move along. A--dry-run
isn't actually doing anything so I don't think it should fail.x-post: https://github.com/stationgroup/ansible-experiments/pull/3
https://github.com/stationgroup/ansible-experiments/issues/4
https://github.com/stationgroup/ansible-experiments/issues/1
https://github.com/stationgroup/ansible-experiments/pull/5
Will test and work on this again Monday.
I think the FreeBSD
os_upgrade.yml
bugs are fixed. https://github.com/stationgroup/ansible-experiments/issues/7