KERBEROS_REALM is unset when creating a shell on HDFS pods
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- hadoop, kubernetes
- Domain
- devops, distributed-systems
Research direction
Inspect how the operator generates core-site.xml and the environment for HDFS pods, starting with the KERBEROS_REALM reference and the shell context for hdfs haadmin. Done when running hdfs haadmin -getAllServiceState from a pod uses the actual Kerberos realm and no longer reports an invalid principal.
Written by the indexing model from the issue text.
Description
Affected Stackable version
25.11
Affected Apache HDFS version
3.4.2
Current and expected behavior
When I shell into a pod to run an HDFS admin command and run hdfs haadmin -getAllServiceState to see the namenode HA status I receive an error message:
stackable@simple-hdfs-namenode-default-0 /stackable/hadoop-3.4.2-stackable25.11.0 $ hdfs haadmin -getAllServiceState
2026-03-10 14:28:00,336 WARN ipc.Client (Client.java:run(749)) - Exception encountered while connecting to the server simple-hdfs-namenode-default-0.simple-hdfs-namenode-default.default.svc.cluster.local/10.1.17.125:8020
javax.security.sasl.SaslException: Bad Kerberos server principal configuration [Caused by java.lang.IllegalArgumentException: Server has invalid Kerberos principal: nn/simple-hdfs.default.svc.cluster.local@KNAB.COM, expecting: nn/simple-hdfs.default.svc.cluster.local@${env.KERBEROS_REALM}]
core-site.xml contains references to the environment variable KERBEROS_REALM in place of the actual Kerberos realm name and this variable is not set in the shell.
Possible solution
Set the KERBEROS_REALM environment variable so that command line tools use the correct realm name.
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
None
- Dominant language
- Rust
- Stars
- 53
- Forks
- 9
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 10
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stackabletech/hdfs-operator
-
Topology Provider permissions briefly dropped during reconciliation when the reflector watch resets Opentype/bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
stackabletech/hdfs-operator#774 ·
-
type/bug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
stackabletech/hdfs-operator#773 ·
-
type/internal-debt
Difficulty 5/5 Over a week Newbie friendliness 15/100
stackabletech/hdfs-operator#769 ·
-
type/bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
stackabletech/hdfs-operator#712 ·
-
type/bug
Difficulty 3/5 1-2 days Newbie friendliness 42/100
stackabletech/hdfs-operator#686 ·
All issues in stackabletech/hdfs-operator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug team:backend track:services-maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cowprotocol/services#4950 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·