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

fix: Hacking on ironic component #10

Conversation

nicholaskuechler
Copy link
Contributor

My changes to get it to progress the deployment. The ironic-api starts, but ironic-conductor fails to start:

  kubectl exec -it ironic-conductor-0 /bin/bash
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
Defaulted container "ironic-conductor" out of: ironic-conductor, ironic-conductor-pxe, ironic-conductor-http, init (init), ironic-conductor-pxe-init (init), ironic-conductor-init (init), ironic-conductor-http-init (init)
root@xs0002:/# ironic-conductor --config-file /etc/ironic/ironic.conf --config-file /tmp/pod-shared/conductor-local-ip.conf
2024-02-26 17:07:15.873 18 DEBUG ironic.common.service [-] Guru meditation reporting is disabled because oslo.reports is not installed prepare_service /var/lib/openstack/lib/python3.10/site-packages/ironic/common/service.py:64
2024-02-26 17:07:16.704 18 DEBUG ironic.conductor.base_manager [None req-650cbb5a-d53e-4182-95b7-b5aff562f6a1 - - - - - -] Initializing database client for xs0002.b0013.ord.ohthree.com. prepare_host /var/lib/openstack/lib/python3.10/site-packages/ironic/conductor/base_manager.py:82
2024-02-26 17:07:16.704 18 DEBUG ironic.conductor.base_manager [None req-650cbb5a-d53e-4182-95b7-b5aff562f6a1 - - - - - -] Removing stale locks from the database matching this conductor's hostname: xs0002.b0013.ord.ohthree.com prepare_host /var/lib/openstack/lib/python3.10/site-packages/ironic/conductor/base_manager.py:84
root@xs0002:/# echo $?
1

@nicholaskuechler nicholaskuechler changed the title Hacking on ironic component fix: Hacking on ironic component Feb 26, 2024
@cardoe cardoe force-pushed the ironic branch 7 times, most recently from 9ebdf98 to 3cf8831 Compare February 27, 2024 06:40
Comment on lines +3 to +8
So unfortunately OpenStack Helm doesn't publish helm charts that can be consumed like
regular helm charts. You must instead clone two of their git repos side by side and
build the dependencies manually. They additionally don't split out secrets but instead
template them into giant config files or even executable scripts that then get stored
as secrets, a clear violation of <https://12factor.net>. As a result we cannot store
a declarative config of Keystone and allow users to supply their own secrets.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it just because they don't publish them in a repo? If so, could we just host it ourselves internally?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's certainly an option. I'm happy to get some ideas around it.

table: "*"
username: ironic
grantOption: true
host: "%"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we restrict this to pod networking subnet?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah that would make sense. No idea how to look that up.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kubectl get nodes -o jsonpath='{.items[*].spec.podCIDR}'

would be one way, but it's also subject to change so maybe just 10.x.x.x would make sense

@cardoe
Copy link
Contributor

cardoe commented Feb 27, 2024

Closing this out in favor of #11 which integrates all of these changes.

@cardoe cardoe closed this Feb 27, 2024
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.

3 participants