fix(ci): bump cwag images to focal and adapt package setup

[nstng]

Signed-off-by: Nils Semmelrock nils.semmelrock@tngtech.com

Summary

see #12898 - (partly in pairing with @jheidbrink)

Test Plan

• cwf/gateway$ vagrant up cwag
• cwf/gateway$ vagrant up cwag_test

Additional Information

• This change is backwards-breaking

[github-actions]

Thanks for opening a PR! 💯

A couple initial guidelines

• All commits must be signed off. This is enforced by DCO check.
• All PR titles must follow the semantic commits format. This is enforced by Semantic PR.

Howto

• Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
• Checks. All required CI checks must pass before merge.
• Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

• Contributing Conventions for norms around contributed code

If this is your first Magma PR, also consider reading

• Developer Onboarding for onboarding as a new Magma developer
• Development Workflow for guidance on your first pull request
• CI Checks for points of contact for failing or flaky CI checks
• GitHub-to-Slack mappings for Magma maintainers for guidance on how to contact maintainers on Slack

[github-actions]

Oops! Looks like you failed the Semantic PR check.

Howto

• Instructions on formatting your PR title
• For PRs with only one commit, the commit message must also be semantic. See Changing a commit message for a howto
• Guide to the different CI checks and resolution guidelines

♻️ Updated: ✅ The check is passing the Semantic PR after the last commit.

[nstng]

@tim FYI approach for fixing the CWF integ tests

[jheidbrink]

Did the cwf integ tests succeed with this change?

[nstng]

for now I just created the images - its on my list to try them locally (if feasible - if not, then CI might be the better choice here)

[jheidbrink]

just curious: how did you discover this dependency?

[nstng]

net-tools contains ifconfig - ifconfig is used in one of the ansible steps

[nstng]

I did run the tests locally and get
[vagrant@127.0.0.1:2201] out: DONE 4 runs, 44 tests, 11 skipped, 5 failures in 746.922s
I am wondering, if I take a look at green runs before the magmacore artifactory switch I see results like
[vagrant@127.0.0.1:2201] out: DONE 4 runs, 43 tests, 11 skipped, 3 failures in 1165.599s
e.g., https://github.com/magma/magma/runs/6494088763?check_suite_focus=true. What is the goal of these tests? Are the results evaluated somewhere else?

[uri200]

It looks like TestGyCreditExhaustionRedirect test seems to be flaky.

Once CWAG machine is built, test can be run again individyally using this command

 fab integ_test:provision_vm=False,rerun_fails=0,no_build=True,skip_unit_tests=True,test_result_xml=test.xml,test_re=TestGyCreditExhaustionRedirect