[ansible-project] Re: Wacky SSH timeout bug with Ansible

up. Thanks! On Monday, August 8, 2016 at 7:14:01 PM UTC-7, Brandon Heller wrote: > > tl;dr; Seeing an Ansible bug where commands take lots of time to start, > and then complete quickly; seems to affect Ubuntu VMs. > > Full description: I’m using Ansible to orchestrate code deploym

[ansible-project] Wacky SSH timeout bug with Ansible

tl;dr; Seeing an Ansible bug where commands take lots of time to start, and then complete quickly; seems to affect Ubuntu VMs. Full description: I’m using Ansible to orchestrate code deployments. These deployments frequently take _much_ longer than expected, because individual steps that sho

Re: [ansible-project] --start-at-task seems broken on 2.0.0-stable

--start-at-task seems to be fixed recently. Thanks, Ansible devs! This is a major improvement to my daily workflow :-) On Wednesday, December 2, 2015 at 4:10:17 PM UTC-8, Brian Coca wrote: > > Currently, this is the price we are paying for the dynamic 'task > includes', we are looking for ways

Re: [ansible-project] --start-at-task seems broken on 2.0.0-stable

Thanks Brian. Did you have a chance to talk to other devs? Is this a conversation I could join in? We've now switched internally to 2.0.0 but I'm finding a lot of debugging much slower, as I have to use a mix of tags and temporary commenting-out to get playbooks working. Thanks, -b On Tues

Re: [ansible-project] --start-at-task seems broken on 2.0.0-stable

On Nov 30, 2015 11:48 PM, "Brian Coca" wrote: > > My tests included a role and a bunch of debug tasks in 2 plays, all > worked, what did not have is a task include. > > This is probably due to the new 'dynamic' nature of tasks includes in > 2.0, the same reason those tasks don't appear in task lis

Re: [ansible-project] --start-at-task seems broken on 2.0.0-stable

ocal ~/src/fwd/ops/ansible/fwd-ubuntu fwd-ubuntu (testing/alex/docker) 14367 $ ansible-playbook -f 20 -i inventory/my_host.ini site-simple.yml --list-tasks playbook: site-simple.yml play #1 (docker_singlebox): TAGS: [] Test task direct TAGS: [] *Test task TAGS: []* On Mo

Re: [ansible-project] --start-at-task seems broken on 2.0.0-stable

Brian, can you point me to the tests you're running? As an update to the previous, I gave up on binary searching to find where the behavior changed; the issue is present at v2.0.0-0.1.alpha1~250 but before then I see a compilation issue where Ansible thinks quotes are missing. On Monday, Nove

Re: [ansible-project] --start-at-task seems broken on 2.0.0-stable

Thanks Brian. I roughly binary searched and the behavior seems to have broken between Ansible code versions v1.9.4-1 and v2.0.0-0.1.alpha1. Before, --list-tasks would show individual tasks and no 'meta' tasks. At 2.0, it just shows a shorter list of meta tasks, which breaks --start-at-task.

[ansible-project] --start-at-task seems broken on 2.0.0-stable

[prior post had a link in the title - if a mod can delete that post, would be great, thanks!] I'm having some issues with ansible 2.0.0-stable (b69942a), where --start-at-task can't find the task with that name. I think a clue may be in --list-tasks, which doesn't list task names for tasks d

[ansible-project] https://github.com/ansible/ansible/issues/11692

Hi, I'm having some issues with ansible 2.0.0-stable (b69942a), where --start-at-task can't find the task with that name. I think a clue may be in --list-tasks, which doesn't list task names for tasks defined as meta: [output from --list-tasks]: PLAY: #5 tasks: TASK: meta