Hey , 1.I'm having some issue while trying to run the integration tests for the network role , it happens when the checkpoint is created , I receive a dialog box which says System policy prevents the creation of a checkpoint or its rollback and so nm is unable to create a checkpoint .
2.When I'm running the example tests, the hosts are unreachable
3.I'm having a bit of trouble in setting up virtual interfaces to make some tests, what would be the best way to do it ? Any help would be greatly appreciated. Thanks, Harsh
Hi Harsh,
please provide more details about how you run the tests, what system are you using, what is the command line and what is the exact output that you are seeing.
Thank you Till
Am Mo., 16. März 2020 um 08:59 Uhr schrieb Harsh Jain harshjain075@gmail.com:
Hey , 1.I'm having some issue while trying to run the integration tests for the network role , it happens when the checkpoint is created , I receive a dialog box which says System policy prevents the creation of a checkpoint or its rollback and so nm is unable to create a checkpoint .
2.When I'm running the example tests, the hosts are unreachable
3.I'm having a bit of trouble in setting up virtual interfaces to make some tests, what would be the best way to do it ? Any help would be greatly appreciated. Thanks, Harsh _______________________________________________ systemroles mailing list -- systemroles@lists.fedorahosted.org To unsubscribe send an email to systemroles-leave@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/systemroles@lists.fedorahosted....
Hey Till,
When I try to run ansible-playbook tests_default.yml or any other test in the tests folder or anything that calls the system role , when it reaches
TASK [linux-system-roles.network : Configure networking connection profiles] a dialog box pops up asking for authentication saying System policy prevents the creation of a checkpoint or its rollback
this works like normal if I provide the password fast enough , otherwise a timeout occurs. Is there any way to overcom this so I won't have to provide the password again .I wasn't able to find anything relevant.
2.When I try to run the examples like ansible-playbook -i inventory bond-with-vlan.yml
I get this
fatal: [v-rhel7]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: Could not resolve hostname v-rhel7: Name or service not known", "unreachable": true} fatal: [v-rhel6]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: Could not resolve hostname v-rhel6: Name or service not known", "unreachable": true}
am I missing something really simple here ?
3. I want to know if multiple virtual interfaces would be required to make and run new tests and what would be the best way to make them .(ifconfig,nmcli or something else?)
I am running these on fedora 31. Appreciate any help Thanks, Harsh
On Mon, Mar 16, 2020 at 4:56 PM Till Maas till@redhat.com wrote:
Hi Harsh,
please provide more details about how you run the tests, what system are you using, what is the command line and what is the exact output that you are seeing.
Thank you Till
Am Mo., 16. März 2020 um 08:59 Uhr schrieb Harsh Jain < harshjain075@gmail.com>:
Hey , 1.I'm having some issue while trying to run the integration tests for
the network role , it happens when the checkpoint is created , I receive a dialog box which says System policy prevents the creation of a checkpoint or its rollback and so nm is unable to create a checkpoint .
2.When I'm running the example tests, the hosts are unreachable
3.I'm having a bit of trouble in setting up virtual interfaces to make
some tests, what would be the best way to do it ?
Any help would be greatly appreciated. Thanks, Harsh _______________________________________________ systemroles mailing list -- systemroles@lists.fedorahosted.org To unsubscribe send an email to systemroles-leave@lists.fedorahosted.org Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedorahosted.org/archives/list/systemroles@lists.fedorahosted....
-- Till Maas He/His/Him Associate Manager, Software Engineering NetworkManager, Nmstate, Ansible RHEL Networking System Role
Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas Savage
Well for the point no. 2 where you are getting an error related to ssh, you must be forgetting to use the keywords "ansible_user" and "ansible_password" in the inventory file of that system because ultimately in ansible we login into another system mentioned in inventory file for config. purposes via ssh from the controller node.
Also, there is an another option available as well to do this by generating a ssh key and copying it to the system in inventory file by ssh-keygen and ssh-copy-id cmds.
Hope you find this helpful!
For the point no.3 like you are saying the no. of virtual interf., I believe that it completely depends on the use case of what you are executing via a yaml file. Moreover to add in a new profile or a connection, I prefer using nmcli offering a variety of options, which you may check in the manual available offline.
Cheers!
Hey Naman, Thanks for the advice on nmcli, I had found it when I was looking around and it seems pretty nice to me as well . I am still not sure about how to handle the inventory on the examples since I do not have access to these machines.
I am also encountering an error while running tox , could you tell me if you are experiencing the same issue? Thanks, Harsh
On Thu, Mar 26, 2020 at 2:45 PM Naman Dhingra namandhingra100@gmail.com wrote:
For the point no.3 like you are saying the no. of virtual interf., I believe that it completely depends on the use case of what you are executing via a yaml file. Moreover to add in a new profile or a connection, I prefer using nmcli offering a variety of options, which you may check in the manual available offline.
Cheers! _______________________________________________ systemroles mailing list -- systemroles@lists.fedorahosted.org To unsubscribe send an email to systemroles-leave@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/systemroles@lists.fedorahosted....
Ok Harsh, nice that you were able to do that with nm.
For the inventory like you are mentioning about, there's no need to have the access to any such machine(maybe such machine doesn't even exist since it's a kind of an example given right there). So I suggest you to run it either in another guestOS/ VM or in order to test you may run it in localhost as well.
For the tox, I'll be able to give to tell only if you let me know the error that you're getting.
Look to hear from you!
Hi Harsh,
thank you for your patience.
Am Di., 17. März 2020 um 16:13 Uhr schrieb Harsh Jain harshjain075@gmail.com:
Hey Till,
When I try to run ansible-playbook tests_default.yml or any other test in the tests folder or anything that calls the system role , when it reaches
TASK [linux-system-roles.network : Configure networking connection profiles] a dialog box pops up asking for authentication saying System policy prevents the creation of a checkpoint or its rollback
this works like normal if I provide the password fast enough , otherwise a timeout occurs. Is there any way to overcom this so I won't have to provide the password again .I wasn't able to find anything relevant.
2.When I try to run the examples like ansible-playbook -i inventory bond-with-vlan.yml
I get this
fatal: [v-rhel7]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: Could not resolve hostname v-rhel7: Name or service not known", "unreachable": true} fatal: [v-rhel6]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: Could not resolve hostname v-rhel6: Name or service not known", "unreachable": true}
am I missing something really simple here ?
yes, you need to create/provide virtual machines that can be reached as v-rhel7 or v-rhel6.
I want to know if multiple virtual interfaces would be required to make and run new tests and what would be the best way to make them .(ifconfig,nmcli or something else?)
You should use virtual machines (or container images) that you use to run the tests against.
This is roughly what the test-harness does (linked from the wiki):
yum install standard-test-roles wget https://cloud.centos.org/centos/8/x86_64/images/CentOS-8-GenericCloud-8.1.19... TEST_SUBJECTS=CentOS-8-GenericCloud-8.1.1911-20200113.3.x86_64.qcow2 ansible-playbook -i /usr/share/ansible/inventory/standard-inventory-qcow2 tests/tests_ethernet.yml (etc)
Kind regards Till
I am running these on fedora 31. Appreciate any help Thanks, Harsh
On Mon, Mar 16, 2020 at 4:56 PM Till Maas till@redhat.com wrote:
Hi Harsh,
please provide more details about how you run the tests, what system are you using, what is the command line and what is the exact output that you are seeing.
Thank you Till
Am Mo., 16. März 2020 um 08:59 Uhr schrieb Harsh Jain harshjain075@gmail.com:
Hey , 1.I'm having some issue while trying to run the integration tests for the network role , it happens when the checkpoint is created , I receive a dialog box which says System policy prevents the creation of a checkpoint or its rollback and so nm is unable to create a checkpoint .
2.When I'm running the example tests, the hosts are unreachable
3.I'm having a bit of trouble in setting up virtual interfaces to make some tests, what would be the best way to do it ? Any help would be greatly appreciated. Thanks, Harsh _______________________________________________ systemroles mailing list -- systemroles@lists.fedorahosted.org To unsubscribe send an email to systemroles-leave@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/systemroles@lists.fedorahosted....
-- Till Maas He/His/Him Associate Manager, Software Engineering NetworkManager, Nmstate, Ansible RHEL Networking System Role
Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas Savage
systemroles@lists.fedorahosted.org
-
Harsh Jain -
Naman Dhingra -
Till Maas