[Sahara][SSL] Sahara uses public url to access swift binaries
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Released
|
High
|
Vitalii Gridnev | ||
9.x |
Fix Released
|
High
|
Vitalii Gridnev |
Bug Description
ENVIRONMENT: MOS 8.0 ISO 429
STEPS TO REPRODUCE:
1. Create environment with sahara
2. Deploy environment with sahara
3. Create cluster from TEMPLATE
4. Run any job with job binaries from swift
EXPECTED RESULT:
Job passed
ACTUAL RESULT:
Job has KILLED state
TEMPLATE:
clusters:
- plugin_name: vanilla
plugin_version: 2.7.1
image: ${vanilla_
node_
- name: worker-dn-nm
flavor: ${ci_flavor_id}
- datanode
- nodemanager
- name: worker-nm
flavor: ${ci_flavor_id}
- nodemanager
- name: worker-dn
flavor: ${ci_flavor_id}
- datanode
- name: master-rm-nn-hvs
flavor: ${ci_flavor_id}
- namenode
- resourcemanager
- hiveserver
- nodemanager
- name: master-oo-hs-sn
flavor: ${ci_flavor_id}
- oozie
- historyserver
- secondarynamenode
- nodemanager
cluster_
name: vanilla271
node_
worker-dn: 1
worker-nm: 1
cluster_
HDFS:
Sahara always uses keystone public auth url to access swift objects. So, there is no override this value causing the issues in cases when it's required to use internalUrl auth url. Links for reference:
[0] https:/
[1] https:/
Upstream-bug: https:/
Changed in mos: | |
status: | In Progress → Fix Committed |
Hmm, and why is using of publicURL an issue here? Isn't keystone available on publicURL?