Skip to content

Wrong address notation (#1) #50080

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

Merged
merged 1 commit into from
Sep 7, 2022

Conversation

ccardenosa
Copy link
Contributor

Missing network prefix

Error adding container to network "work-network": the 'address' field is expected to be in CIDR notation, got: '192.168.10.10'

Version(s):

  • PR applies to all versions after a specific version (e.g. 4.8): 4.8+

Issue:
POD creation fails due to this:

Warning FailedCreatePodSandBox 3s kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_multus-training-6f8cbbbf74-vn7v2_multus-training_b397a304-a920-4cd6-97c1-203f0ca2dc33_0(1a6516c279b60da692fb0dd3fc7206b49bf8904748f0fa3e68ab3530f01d7b71): error adding pod multus-training_multus-training-6f8cbbbf74-vn7v2 to CNI network "multus-cni-network": plugin type="multus" name="multus-cni-network" failed (add): [multus-training/multus-training-6f8cbbbf74-vn7v2/b397a304-a920-4cd6-97c1-203f0ca2dc33:work-network]: error adding container to network "work-network": the 'address' field is expected to be in CIDR notation, got: '192.168.10.10'

Link to docs preview:

https://docs.openshift.com/container-platform/4.6/networking/multiple_networks/configuring-additional-network.html#nw-multus-ipvlan-config-example_configuring-additional-network
https://docs.openshift.com/container-platform/4.7/networking/multiple_networks/configuring-additional-network.html#nw-multus-ipvlan-config-example_configuring-additional-network
https://docs.openshift.com/container-platform/4.8/networking/multiple_networks/configuring-additional-network.html#nw-multus-ipvlan-config-example_configuring-additional-network
https://docs.openshift.com/container-platform/4.9/networking/multiple_networks/configuring-additional-network.html#nw-multus-ipvlan-config-example_configuring-additional-network
https://docs.openshift.com/container-platform/4.10/networking/multiple_networks/configuring-additional-network.html#nw-multus-ipvlan-config-example_configuring-additional-network
https://docs.openshift.com/container-platform/4.11/networking/multiple_networks/configuring-additional-network.html#nw-multus-ipvlan-config-example_configuring-additional-network

*Missing network prefix*

Error adding container to network "work-network": the 'address' field is expected to be in CIDR notation, got: '192.168.10.10'
@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Sep 7, 2022
@mburke5678
Copy link
Contributor

Approvals in #50024

@mburke5678 mburke5678 merged commit dbc23bd into openshift:main Sep 7, 2022
@mburke5678
Copy link
Contributor

/cherrypick enterprise-4.8

@openshift-cherrypick-robot

@mburke5678: new pull request created: #50087

In response to this:

/cherrypick enterprise-4.8

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@mburke5678
Copy link
Contributor

/cherrypick enterprise-4.9

@mburke5678
Copy link
Contributor

/cherrypick enterprise-4.10

@mburke5678
Copy link
Contributor

/cherrypick enterprise-4.11

@mburke5678
Copy link
Contributor

/cherrypick enterprise-4.12

@openshift-cherrypick-robot

@mburke5678: new pull request created: #50092

In response to this:

/cherrypick enterprise-4.9

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-cherrypick-robot

@mburke5678: new pull request created: #50093

In response to this:

/cherrypick enterprise-4.10

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-cherrypick-robot

@mburke5678: new pull request created: #50094

In response to this:

/cherrypick enterprise-4.11

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-cherrypick-robot

@mburke5678: new pull request created: #50095

In response to this:

/cherrypick enterprise-4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@mburke5678
Copy link
Contributor

@ccardenosa Does this one need to be cherrypicked to 4.6 and 4.7? The address is 191.168.1.7 in 4.6.

@ccardenosa
Copy link
Contributor Author

@mburke5678 I think so. These are the current status for:

4.6

4.7

@mburke5678
Copy link
Contributor

/cherrypick enterprise-4.6

@mburke5678
Copy link
Contributor

/cherrypick enterprise-4.7

@openshift-cherrypick-robot

@mburke5678: new pull request created: #50120

In response to this:

/cherrypick enterprise-4.6

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-cherrypick-robot

@mburke5678: new pull request created: #50121

In response to this:

/cherrypick enterprise-4.7

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants