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.

Sign up for GitHub

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

Jump to bottom

openshift 3.6 #388

Open
bartpved opened this issue Sep 26, 2017 · 7 comments
Open

openshift 3.6 #388

bartpved opened this issue Sep 26, 2017 · 7 comments

Comments

@bartpved
Copy link

Hello,
Has anyone tried to use openshift 3.6 with this?
I see some issue openshift-ansible, docker.service is not started on nodes and master, and therefore docker status check tasks fail.

Looks like there is some issue with openshift-ansible tasks here:
https://github.com/openshift/openshift-ansible/blob/openshift-ansible-3.6.173.0.21-2/roles/docker/tasks/package_docker.yml

The task I think that should start docker service is ignored according to the ansible logs:
TASK [docker : Start the Docker service] ***************************************
task path: /usr/share/ansible/openshift-ansible/roles/docker/tasks/package_docker.yml:120
skipping: [ocp-36-infra-0.ocp-36.teco.dev.a.tecdomain.net] => {
"changed": false,
"skip_reason": "Conditional result was False",
"skipped": true
}

Like something would be messed up with param

openshift.docker.use_system_container

Failure log message:
------------snip----------------
CHECK [memory_availability : ocp-36-node-4aj8x72s.ocp-36.teco.dev.a.tecdomain.net] ***
fatal: [ocp-36-node-4aj8x72s.ocp-36.teco.dev.a.tecdomain.net]: FAILED! => {
"changed": true,
"checks": {
"disk_availability": {},
"docker_image_availability": {
"changed": true
},
"docker_storage": {
"changed": true,
"failed": true,
"msg": "Failed to query Docker API. Is docker running on this host?"
},
------------snip----------------
@bartpved
Copy link
Author

Manually starting the docker.service on each node/master/infra machine + manually running ansible seems to do the trick.

@ioggstream
Copy link
Contributor

When I tried, I got yum conflicts installing OSP10 and OCP3.6 packages.

iirc the conficting package was python-requests.

@bartpved
Copy link
Author

Tried with OSP8

@ioggstream
Copy link
Contributor

Were you able to move on ?

@bartpved
Copy link
Author

yeah, works well.

@t-v
Copy link

t-v commented Feb 23, 2018 •
edited
Loading

I am having a similar issue. I try to install openshift 3.6 on an openstack 10 environment and get these issues.

openstack stack creation:

openstack stack create -t openshift-on-openstack/openshift.yaml -e openshift_parameters.yaml openshift-test --wait
2018-02-14 15:56:11Z [openshift-test]: CREATE_IN_PROGRESS  Stack CREATE started
2018-02-14 15:56:13Z [openshift-test.cluster_network]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:13Z [openshift-test.fixed_network]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:13Z [openshift-test.registry_volume]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:13Z [openshift-test.node_security_group]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:13Z [openshift-test.master_security_group]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:13Z [openshift-test.infra_security_group]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:13Z [openshift-test.infra_server_group]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:13Z [openshift-test.bastion_security_group]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:13Z [openshift-test.master_server_group]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:13Z [openshift-test.ansible_keys]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:13Z [openshift-test.external_router]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:13Z [openshift-test.infra_server_group]: CREATE_COMPLETE  state changed
2018-02-14 15:56:13Z [openshift-test.master_server_group]: CREATE_COMPLETE  state changed
2018-02-14 15:56:13Z [openshift-test.ansible_keys]: CREATE_COMPLETE  state changed
2018-02-14 15:56:13Z [openshift-test.fixed_network]: CREATE_COMPLETE  state changed
2018-02-14 15:56:13Z [openshift-test.cluster_network]: CREATE_COMPLETE  state changed
2018-02-14 15:56:13Z [openshift-test.bastion_security_group]: CREATE_COMPLETE  state changed
2018-02-14 15:56:13Z [openshift-test.node_security_group]: CREATE_COMPLETE  state changed
2018-02-14 15:56:14Z [openshift-test.cluster_subnet]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:14Z [openshift-test.infra_security_group]: CREATE_COMPLETE  state changed
2018-02-14 15:56:14Z [openshift-test.fixed_subnet]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:15Z [openshift-test.master_security_group]: CREATE_COMPLETE  state changed
2018-02-14 15:56:15Z [openshift-test.registry_volume]: CREATE_COMPLETE  state changed
2018-02-14 15:56:15Z [openshift-test.fixed_subnet]: CREATE_COMPLETE  state changed
2018-02-14 15:56:15Z [openshift-test.cluster_subnet]: CREATE_COMPLETE  state changed
2018-02-14 15:56:16Z [openshift-test.bastion_port]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:17Z [openshift-test.external_router]: CREATE_COMPLETE  state changed
2018-02-14 15:56:17Z [openshift-test.bastion_port]: CREATE_COMPLETE  state changed
2018-02-14 15:56:18Z [openshift-test.lb_floating_ip]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:18Z [openshift-test.external_router_interface]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:18Z [openshift-test.lb_floating_ip]: CREATE_COMPLETE  state changed
2018-02-14 15:56:20Z [openshift-test.external_router_interface]: CREATE_COMPLETE  state changed
2018-02-14 15:56:21Z [openshift-test.bastion_floating_ip]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:21Z [openshift-test.ipfailover]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:22Z [openshift-test.bastion_floating_ip]: CREATE_COMPLETE  state changed
2018-02-14 15:56:23Z [openshift-test.bastion_host]: CREATE_IN_PROGRESS  state changed
2018-02-14 15:56:26Z [openshift-test.ipfailover]: CREATE_COMPLETE  state changed
2018-02-14 16:01:23Z [openshift-test.bastion_host]: CREATE_FAILED  WaitConditionFailure: resources.bastion_host.resources.wait_condition: failed to run os-collect-config
2018-02-14 16:01:23Z [openshift-test]: CREATE_FAILED  Resource CREATE failed: WaitConditionFailure: resources.bastion_host.resources.wait_condition: failed to run os-collect-config

 Stack openshift-test CREATE_FAILED

log on the bastion:

Package python-urllib3-1.16-1.el7ost.noarch is obsoleted by python2-urllib3-1.21.1-1.el7.noarch which is already installed
--> Finished Dependency Resolution
Error: Package: python-requests-2.11.1-1.el7ost.noarch (rhel-7-server-openstack-10-rpms)
Requires: python-urllib3 = 1.16
Installed: python2-urllib3-1.21.1-1.el7.noarch (@rhel-7-server-ose-3.6-rpms)
python-urllib3 = 1.21.1-1.el7
Available: python-urllib3-1.5-8.el7.noarch (rhel-7-server-rpms)
python-urllib3 = 1.5-8.el7
Available: python-urllib3-1.10.2-1.el7_1.noarch (rhel-7-server-rpms)
python-urllib3 = 1.10.2-1.el7_1
Available: python-urllib3-1.10.2-2.el7_1.noarch (rhel-7-server-rpms)
python-urllib3 = 1.10.2-2.el7_1
Available: python-urllib3-1.10.2-3.el7.noarch (rhel-7-server-rpms)
python-urllib3 = 1.10.2-3.el7
Available: python-urllib3-1.15.1-2.el7ost.noarch (rhel-7-server-openstack-10-rpms)
python-urllib3 = 1.15.1-2.el7ost
Available: python-urllib3-1.16-1.el7ost.noarch (rhel-7-server-openstack-10-rpms)
python-urllib3 = 1.16-1.el7ost
**********************************************************************
yum can be configured to try to resolve such errors by temporarily enabling
disabled repos and searching for missing dependencies.
To enable this functionality please set 'notify_only=0' in /etc/yum/pluginconf.d/search-disabled-repos.conf
**********************************************************************

Error: Package: python-requests-2.11.1-1.el7ost.noarch (rhel-7-server-openstack-10-rpms)
Requires: python-urllib3 = 1.16
Installed: python2-urllib3-1.21.1-1.el7.noarch (@rhel-7-server-ose-3.6-rpms)
python-urllib3 = 1.21.1-1.el7
Available: python-urllib3-1.5-8.el7.noarch (rhel-7-server-rpms)
python-urllib3 = 1.5-8.el7
Available: python-urllib3-1.10.2-1.el7_1.noarch (rhel-7-server-rpms)
python-urllib3 = 1.10.2-1.el7_1
Available: python-urllib3-1.10.2-2.el7_1.noarch (rhel-7-server-rpms)
python-urllib3 = 1.10.2-2.el7_1
Available: python-urllib3-1.10.2-3.el7.noarch (rhel-7-server-rpms)
python-urllib3 = 1.10.2-3.el7
Available: python-urllib3-1.15.1-2.el7ost.noarch (rhel-7-server-openstack-10-rpms)
python-urllib3 = 1.15.1-2.el7ost
Available: python-urllib3-1.16-1.el7ost.noarch (rhel-7-server-openstack-10-rpms)
python-urllib3 = 1.16-1.el7ost
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

@ioggstream
Copy link
Contributor

I had the same issue. You can solve it manually in some way, but I doubt it will be a supported solution (eg. new rpm releases may break too).

Try to check the latest OCP 3.6 on OSP 10 reference architecture and see if there's a solution there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ioggstream @t-v @bartpved