Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CASMTRIAGE-2793 Add Toggle for Exclusive IPv4 #21

Merged
merged 1 commit into from
Jan 7, 2022

Conversation

rustydb
Copy link
Contributor

@rustydb rustydb commented Jan 7, 2022

Summary and Scope

When testing CASMTRIAGE-2793 on MUG, IPv6 networking between the deployment server and client were not fully functional. During those tests, IPv6 was preventing the download of artifacts and the initial call-to-home by dracut. Using this feature MUG was able to deploy itself by forcing IPv4.

By default metal-dracut will use IPv4 unless it is told otherwise by the
new metal.ipv4 argument being set to 0.

Issue Type
  • RFE Pull Request

Example:

ncn-m002:~ # set -x
ncn-m002:~ # ping ${metal_ipv4:+-4} 10.1.1.2
+ ping 10.1.1.2
PING 10.1.1.2 (10.1.1.2) 56(84) bytes of data.
64 bytes from 10.1.1.2: icmp_seq=1 ttl=64 time=0.091 ms
64 bytes from 10.1.1.2: icmp_seq=2 ttl=64 time=0.077 ms
^C
--- 10.1.1.2 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1006ms
rtt min/avg/max/mdev = 0.077/0.084/0.091/0.007 ms
ncn-m002:~ # ^C
ncn-m002:~ # metal_ipv4=1
+ metal_ipv4=1
ncn-m002:~ # ping ${metal_ipv4:+-4} 10.1.1.2
+ ping -4 10.1.1.2
PING 10.1.1.2 (10.1.1.2) 56(84) bytes of data.
64 bytes from 10.1.1.2: icmp_seq=1 ttl=64 time=0.089 ms
64 bytes from 10.1.1.2: icmp_seq=2 ttl=64 time=0.061 ms
^C
--- 10.1.1.2 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1009ms
rtt min/avg/max/mdev = 0.061/0.075/0.089/0.014 ms
ncn-m002:~ # curl ${metal_ipv4:+-4} -O "http://pit/ncn-m002/kernel
> ^C
ncn-m002:~ # curl ${metal_ipv4:+-4} -O "http://pit/ncn-m002/kernel"
+ curl -4 -O http://pit/ncn-m002/kernel
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 8846k  100 8846k    0     0   479M      0 --:--:-- --:--:-- --:--:--  479M
ncn-m002:~ # unset metal_ipv4
+ unset metal_ipv4
ncn-m002:~ # curl ${metal_ipv4:+-4} -O "http://pit/ncn-m002/kernel"
+ curl -O http://pit/ncn-m002/kernel
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 8846k  100 8846k    0     0   454M      0 --:--:-- --:--:-- --:--:--  479M

Prerequisites

  • I have included documentation in my PR (or it is not required)
  • I tested this on internal system (x) (if yes, please include results or a description of the test)

MUG was able to download and fetch artifacts after incorporating this RPM.

Idempotency

Risks and Mitigations

What is less risky, or more risky now - or if your mod fails is there a new risk?

We're no no longer using whatever the environment provides by default, and forcing an older IP catalogue. This is retroactive, in the sense that we may want to remove this in the future.

By default metal-dracut will use IPv4 unless it is told otherwise by the
new metal.ipv4 argument being set to 0.
@rustydb rustydb merged commit 65fad89 into main Jan 7, 2022
@rustydb rustydb deleted the CASMTRIAGE-2793-ipv4-only branch January 7, 2022 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants