There is no possibility to operate with old cluster after upgrade master to 7.0 and https only enabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
High
|
Fuel Python (Deprecated) | ||
6.1.x |
Won't Fix
|
High
|
MOS Maintenance | ||
7.0.x |
Won't Fix
|
High
|
Fuel Python (Deprecated) | ||
8.0.x |
Invalid
|
High
|
Fuel Python (Deprecated) |
Bug Description
Steps to reproduce:
1. Deploy master node with official Mirantis 6.1 release
2. Create simple cluster : 1 controller + 1 compute +1 cinder with Centos, run ostf
3. upgrade master node to 7.0
4. enable https only mode on master node
Open ssh to the master
Edit /etc/fuel/
Add the following to the end of the file:
"SSL":
"
Restart nginx container
5. Try to add the nodes to 6.1 running cluster (current nodes will mark as offline in nailgun)
6. ssh on one of the node and run command yum update (nailgun -agent with https support should come, but unexpectedly it is not )
7. Try to get nailgun agent that support https from master node repo (7.0) and install it
8. Edit nailgun -config change http to https and change the port)
Try to start agent
Current result:I, [2015-09-
I, [2015-09-
/usr/bin/
from /usr/bin/
from /usr/bin/
So the main problems that looks like critical:
1. There is no nailgun agent with https support in 6.1 update mirrors
2. There is no any mention about needed changes in config and how exactly to update package in official documentation
3. current nailgun agent from 7.0 repository nailgun-
failed to start with mentioned above error
{"build_id": "289", "build_number": "289", "release_versions": {"2015.1.0-7.0": {"VERSION": {"build_id": "289", "build_number": "289", "api": "1.0", "fuel-library_sha": "08ae959d38bbe5
tags: | added: area-python |
6.1 environments do not support https connections to the master node. And manual update of fuel-nailgun-agent on 6.1 environment to 7.0 version will not work. So workaround here is to not enforce SSL connections if you have environments that don't support it. We should add a release note about it. Changing priority to High.