Yes.. I uses Ubuntu 22 . but when executed manually source exists.
Failing when called through the playbook with the mentioned error.
@Todd Will it exists until the next play executes in the same playbook
?
I required the processed source variables for the next
play(only ) .
On Friday, March 10, 2023 at 9:27:26 PM UTC+5:30 Todd Lewis wrote:
> Even if it worked, its effects will go away as soon as the shell running
> it closes. It won't persist to another task.
>
> On Friday, March 10, 2023 at 10:45:06 AM UTC-5 Antony Stone wrote:
>
>> On Friday 10 March 2023 at 16:39:17, Veera wrote:
>>
>> > Its a problem with "pexpect" module requirement and it worked after
>> "pip3
>> > install pexpect".
>> > However , now "source ./myenv" is not working
>> >
>> > msg": "The command was not found or was not executable: source"
>> >
>> > Since source is a shell inbuilt command . Is there a way to overcome it
>> ?
>> > I tried multiple options ..
>>
>> "source" is a Bash built-in, but are you sure the remote machine is using
>> Bash
>> as its shell?
>>
>> If it's a modern Debian (ore derivative) machine and it's using /bin/sh,
>> that's Dash, not Bash, and Dash does not have the "source" command.
>>
>>
>> Antony.
>>
>> --
>> The Free Software Foundation Europe was formed on this day in 2001
>> https://fsfe.org
>>
>> Please reply to the list;
>> please *don't* CC me.
>>
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/970d8de7-0f4d-445b-99a0-02afce9fb66dn%40googlegroups.com.
