Giter VIP home page Giter VIP logo

Comments (14)

dhellmann avatar dhellmann commented on August 27, 2024

Did the host actually boot the inspection agent? Are there messages on the console?

from metal3-docs.

hansbogert avatar hansbogert commented on August 27, 2024

Nope, just your usual PXE timeout screen

Traced it, I guess, to the ironic pod on the host:

sudo podman logs 01cd555fb4f9
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
Device "provisioning" does not exist.
Waiting for provisioning interface to be configured
AH00557: httpd: apr_sockaddr_info_get() failed for ironic-pod
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message
ln: failed to create symbolic link '/var/log/httpd/access_log': File exists
ln: failed to create symbolic link '/var/log/httpd/error_log': File exists
AH00557: httpd: apr_sockaddr_info_get() failed for ironic-pod
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message
ln: failed to create symbolic link '/var/log/httpd/access_log': File exists
ln: failed to create symbolic link '/var/log/httpd/error_log': File exists
AH00557: httpd: apr_sockaddr_info_get() failed for ironic-pod
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message
/bin/runhttpd: line 46:    28 Killed                  sleep infinity
ln: failed to create symbolic link '/var/log/httpd/access_log': File exists
ln: failed to create symbolic link '/var/log/httpd/error_log': File exists
AH00557: httpd: apr_sockaddr_info_get() failed for ironic-pod
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message
/bin/runhttpd: line 46:    28 Killed                  sleep infinity

from metal3-docs.

hansbogert avatar hansbogert commented on August 27, 2024

Which process/pod/container would actually hand out dhcp and/or the NBP in the try-it-out scenario?

from metal3-docs.

russellb avatar russellb commented on August 27, 2024

What commit from metal3-dev-env are you using?

We just merged metal3-io/metal3-dev-env#68 2 days ago that moved Ironic into the cluster, running as part of the baremetal operator pod instead of via podman on the host.

from metal3-docs.

hansbogert avatar hansbogert commented on August 27, 2024
git log  HEAD^..HEAD --oneline |more
1164092 Merge pull request #81 from Nordix/feature/increase-timeout-for-tests-kashif
2d6973e Increase timeout limit for tests

I can verify with wireshark that the master and worker VMs' PXE dhcp request is seen on the provisioning bridge on the host.

from metal3-docs.

dhellmann avatar dhellmann commented on August 27, 2024

I hit something like this. I think we associated it with https://bugzilla.redhat.com/show_bug.cgi?id=634736

I was able to fix it by using sysctl to set a few parameters described in that bug and in https://wiki.libvirt.org/page/Networking

net.bridge.bridge-nf-call-arptables = 0
net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0

It's not clear why this doesn't affect all systems.

from metal3-docs.

hansbogert avatar hansbogert commented on August 27, 2024

instant success with the above applied:

for easy copy & paste for others:

sudo sysctl -w net.bridge.bridge-nf-call-arptables=0
sudo sysctl -w net.bridge.bridge-nf-call-iptables=0
sudo sysctl -w net.bridge.bridge-nf-call-ip6tables=0

from metal3-docs.

dhellmann avatar dhellmann commented on August 27, 2024

I wonder if we should just have the scripts apply those changes? What do you think @russellb ?

from metal3-docs.

russellb avatar russellb commented on August 27, 2024

Sounds good to me. The arptables one probably isn’t needed, but otherwise I like the idea of just doing this automatically.

from metal3-docs.

dhellmann avatar dhellmann commented on August 27, 2024

Great, so how about it @hansbogert , are you up for creating a PR?

from metal3-docs.

hansbogert avatar hansbogert commented on August 27, 2024

Sure @dhellmann, should we put the sysctls in 02_configure_host.sh?

from metal3-docs.

russellb avatar russellb commented on August 27, 2024

from metal3-docs.

stbenjam avatar stbenjam commented on August 27, 2024

No activity since October, if this still needs addressing please open a PR or issue against metal3-dev-env.

/close

from metal3-docs.

metal3-io-bot avatar metal3-io-bot commented on August 27, 2024

@stbenjam: Closing this issue.

In response to this:

No activity since October, if this still needs addressing please open a PR or issue against metal3-dev-env.

/close

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.

from metal3-docs.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.