Re: Openshift Origin 3.9 rpms -> ansible playbooks
On Wed, Apr 11, 2018 at 9:53 AM, Charles Moulliard wrote: > Any ideas when rpms about origin 3.9 will be available under > http://mirror.centos.org/centos/7/paas/x86_64/ ? > The 3.9.0 are currently in testing. If there are no problems, we hope to have them released (where you are pointing) on Tuesday, April 17. If you want to use the testing packages they are here https://buildlogs.centos.org/centos/7/paas/x86_64/ > Can we use the origin docker images with the openshift-ansible playbook > instead of the RPMS to install the openshift_cluster ? If the answer to my > question is yes, what should I do then ? > > On Tue, Mar 20, 2018 at 6:52 AM, Clayton Coleman > wrote: >> >> We’re still waiting for a few more fixes to be delivered to 3.9 related to >> the subpath changes Kube. >> >> On Mar 19, 2018, at 4:15 AM, Charles Moulliard >> wrote: >> >> Do we know when Origin official rpms for OpenShift 3.9 will be released >> under "http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin39/"; ? >> Who manage such builds for RHEL, CentOS, Fedora ? >> >> On Fri, Mar 16, 2018 at 4:42 PM, Troy Dawson wrote: >>> >>> On Fri, Mar 16, 2018 at 8:32 AM, Charles Moulliard >>> wrote: >>> > Hi, >>> > >>> > Are the OpenShift Origin v3.9 rpms available from a repo ? >>> > How can we get them in order to install openshift cluster using ansible >>> > playbook ? >>> > >>> > Regards >>> > >>> > Charles >>> > >>> > ___ >>> > dev mailing list >>> > dev@lists.openshift.redhat.com >>> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >>> > >>> >>> https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin39/ >>> >>> I think it's >>> ansible-playbook -e openshift_repos_enable_testing=true >> >> >> ___ >> dev mailing list >> dev@lists.openshift.redhat.com >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Re: Openshift Origin 3.9 rpms -> ansible playbooks
Any ideas when rpms about origin 3.9 will be available under http://mirror.centos.org/centos/7/paas/x86_64/ ? Can we use the origin docker images with the openshift-ansible playbook instead of the RPMS to install the openshift_cluster ? If the answer to my question is yes, what should I do then ? On Tue, Mar 20, 2018 at 6:52 AM, Clayton Coleman wrote: > We’re still waiting for a few more fixes to be delivered to 3.9 related to > the subpath changes Kube. > > On Mar 19, 2018, at 4:15 AM, Charles Moulliard > wrote: > > Do we know when Origin official rpms for OpenShift 3.9 will be released > under "http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin39/"; > ? > Who manage such builds for RHEL, CentOS, Fedora ? > > On Fri, Mar 16, 2018 at 4:42 PM, Troy Dawson wrote: > >> On Fri, Mar 16, 2018 at 8:32 AM, Charles Moulliard >> wrote: >> > Hi, >> > >> > Are the OpenShift Origin v3.9 rpms available from a repo ? >> > How can we get them in order to install openshift cluster using ansible >> > playbook ? >> > >> > Regards >> > >> > Charles >> > >> > ___ >> > dev mailing list >> > dev@lists.openshift.redhat.com >> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >> > >> >> https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin39/ >> >> I think it's >> ansible-playbook -e openshift_repos_enable_testing=true >> > > ___ > dev mailing list > dev@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Re: Openshift Origin 3.9 rpms -> ansible playbooks
We’re still waiting for a few more fixes to be delivered to 3.9 related to the subpath changes Kube. On Mar 19, 2018, at 4:15 AM, Charles Moulliard wrote: Do we know when Origin official rpms for OpenShift 3.9 will be released under "http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin39/"; ? Who manage such builds for RHEL, CentOS, Fedora ? On Fri, Mar 16, 2018 at 4:42 PM, Troy Dawson wrote: > On Fri, Mar 16, 2018 at 8:32 AM, Charles Moulliard > wrote: > > Hi, > > > > Are the OpenShift Origin v3.9 rpms available from a repo ? > > How can we get them in order to install openshift cluster using ansible > > playbook ? > > > > Regards > > > > Charles > > > > ___ > > dev mailing list > > dev@lists.openshift.redhat.com > > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > > > https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin39/ > > I think it's > ansible-playbook -e openshift_repos_enable_testing=true > ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Re: Openshift Origin 3.9 rpms -> ansible playbooks
On Mon, Mar 19, 2018 at 1:15 AM, Charles Moulliard wrote: > Do we know when Origin official rpms for OpenShift 3.9 will be released > under "http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin39/"; ? > Who manage such builds for RHEL, CentOS, Fedora ? > RHEL has a dedicated team to release their packages, but that's not the repo you are pointing at. Both Fedora and CentOS's packages are built by a handful of volunteers who do it in their spare time. > On Fri, Mar 16, 2018 at 4:42 PM, Troy Dawson wrote: >> >> On Fri, Mar 16, 2018 at 8:32 AM, Charles Moulliard >> wrote: >> > Hi, >> > >> > Are the OpenShift Origin v3.9 rpms available from a repo ? >> > How can we get them in order to install openshift cluster using ansible >> > playbook ? >> > >> > Regards >> > >> > Charles >> > >> > ___ >> > dev mailing list >> > dev@lists.openshift.redhat.com >> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >> > >> >> https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin39/ >> >> I think it's >> ansible-playbook -e openshift_repos_enable_testing=true > > ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Re: Openshift Origin 3.9 rpms -> ansible playbooks
3.9 hasn't shipped yet, we're still cleaning up a last couple of items. I'm not sure off hand who releases the work for the other distros. On Mon, Mar 19, 2018 at 4:15 AM, Charles Moulliard wrote: > Do we know when Origin official rpms for OpenShift 3.9 will be released > under "http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin39/"; ? > Who manage such builds for RHEL, CentOS, Fedora ? > > On Fri, Mar 16, 2018 at 4:42 PM, Troy Dawson wrote: >> >> On Fri, Mar 16, 2018 at 8:32 AM, Charles Moulliard >> wrote: >> > Hi, >> > >> > Are the OpenShift Origin v3.9 rpms available from a repo ? >> > How can we get them in order to install openshift cluster using ansible >> > playbook ? >> > >> > Regards >> > >> > Charles >> > >> > ___ >> > dev mailing list >> > dev@lists.openshift.redhat.com >> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >> > >> >> https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin39/ >> >> I think it's >> ansible-playbook -e openshift_repos_enable_testing=true > > > > ___ > dev mailing list > dev@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > -- Michael Gugino Senior Software Engineer - OpenShift mgug...@redhat.com 540-846-0304 ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Re: Openshift Origin 3.9 rpms -> ansible playbooks
Do we know when Origin official rpms for OpenShift 3.9 will be released under "http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin39/"; ? Who manage such builds for RHEL, CentOS, Fedora ? On Fri, Mar 16, 2018 at 4:42 PM, Troy Dawson wrote: > On Fri, Mar 16, 2018 at 8:32 AM, Charles Moulliard > wrote: > > Hi, > > > > Are the OpenShift Origin v3.9 rpms available from a repo ? > > How can we get them in order to install openshift cluster using ansible > > playbook ? > > > > Regards > > > > Charles > > > > ___ > > dev mailing list > > dev@lists.openshift.redhat.com > > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > > > https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin39/ > > I think it's > ansible-playbook -e openshift_repos_enable_testing=true > ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Re: Openshift Origin 3.9 rpms -> ansible playbooks
Many thanks for your help Michael. Well appreciated On Sat, Mar 17, 2018 at 12:59 AM, Michael Gugino wrote: > For 3.7 and below, you need to do some manual preparation steps and > then the playbook you want to run is: > openshift-ansible/playbooks/byo/config.yml > > Prerequisites: https://docs.openshift.org/latest/install_config/install/ > prerequisites.html > > Host prep: https://docs.openshift.org/latest/install_config/install/ > host_preparation.html > > I think some of the items in those pages are already done on atomic > host (such as installing docker). > > On Fri, Mar 16, 2018 at 5:48 PM, Charles Moulliard > wrote: > > I see from your github repo that you use playbook committed under master > > branch > > as you use these commands to install ocp > > > > ansible-playbook -i inventory/hosts.localhost playbooks/prerequisites.yml > > ansible-playbook -i inventory/hosts.localhost > playbooks/deploy_cluster.yml > > > > Unfortunately that fails for me to install Openshift Origin v3.7 > > > > On Fri, Mar 16, 2018 at 10:17 PM, Michael Gugino > wrote: > >> > >> I use this basic inventory with fedora atomic: > >> https://github.com/michaelgugino/openshift-stuff/ > tree/master/fedora-atomic > >> > >> I usually deploy to AWS for testing and development. Wherever you > >> deploy, your instance's hostnames need to be resolvable. > >> > >> I don't have any recommendations for using any specific tags. I > >> usually use the head of a release branch; I very rarely use specific > >> tags or commits. > >> > >> I don't have any general recommendations for deploying any other than > >> released openshift code. If you're trying to deploy testing images / > >> rpms, > >> your setup is going to depend on what you're trying to accomplish. I > >> highly recommend deploying released code. That is the only way it's > >> going to > >> 'just work.' > >> > >> On Fri, Mar 16, 2018 at 4:41 PM, Charles Moulliard > > >> wrote: > >> > > >> > > >> > On Fri, Mar 16, 2018 at 8:57 PM, Michael Gugino > >> > wrote: > >> >> > >> >> I typically use the head of each release branch for > openshift-ansible. > >> >> Most of the time that's a good approach for anything that is already > >> >> released (such as 3.7). > >> > > >> > > >> >>> So using this tagged release is a good idea then : > >> >>> > >> >>> https://github.com/openshift/openshift-ansible/releases/ > tag/openshift-ansible-3.7.38-1 > >> >>> ? > >> > > >> >> Alternatively, you can install the > >> >> openshift-ansible origin rpm on a centos host. > >> > > >> > > >> >>> How can I do that ? > >> >> > >> >> > >> >> I don't recommend using openshift_repos_enable_testing, it's been > >> >> nothing but problems for me. I don't recommend using any testing > >> >> versions of any packages either. > >> > > >> > > >> >>> I agree as last run generayed such bad rpms installed > >> > > >> > Beginning of executing the playbook > >> > origin.x86_643.7.0-1.0.7ed6862 > >> > @centos-openshift-origin37 > >> > origin-clients.x86_643.7.0-1.0.7ed6862 > >> > @centos-openshift-origin37 > >> > origin-master.x86_64 3.7.0-1.0.7ed6862 > >> > @centos-openshift-origin37 > >> > > >> > Later ... > >> > > >> > origin.x86_643.7.1-1.el7.git.0.0a2d6a1 > >> > @centos-openshift-origin37-testing > >> > origin-clients.x86_643.7.1-1.el7.git.0.0a2d6a1 > >> > @centos-openshift-origin37-testing > >> > origin-master.x86_64 3.7.1-1.el7.git.0.0a2d6a1 > >> > @centos-openshift-origin37-testing > >> > origin-node.x86_64 3.7.1-1.el7.git.0.0a2d6a1 > >> > @centos-openshift-origin37-testing > >> > > >> > > >> >> > >> >> > >> >> For testing new origin code, I have had the best luck with Fedora > >> >> Atomic 27. > >> > > >> > > >> >>> Can you share what you did (info, doc, ...) ? > >> > > >> >> > >> >> However, I don't think 3.9 origin is in great shape at the > >> >> moment. > >> >> > >> >> On Fri, Mar 16, 2018 at 3:49 PM, Charles Moulliard > >> >> > >> >> wrote: > >> >> > Do you suggest to use a tagged version of the openshift ansible git > >> >> > repo > >> >> > combined > >> >> > with such parameters within the inventory ? > >> >> > > >> >> > E.g > >> >> > > >> >> > git clone -b > >> >> > > >> >> > > >> >> > https://github.com/openshift/openshift-ansible/releases/ > tag/openshift-ansible-3.7.38-1 > >> >> > > >> >> > inventory > >> >> > === > >> >> > openshift_repos_enable_testing = true > >> >> > containerized = false > >> >> > openshift_release = v3.7 > >> >> > openshift_pkg_version = "-3.7.0-1.0.7ed6862" # See -> > >> >> > https://buildlogs.centos.org/centos/7/paas/x86_64/ > openshift-origin37/ > >> >> > openshift_deployment_type = origin > >> >> > ... > >> >> > > >> >> > ansible-playbook -i inventory > >> >> > openshift-ansible/playbooks/byo/config.yml > >> >> > > >> >> > On Fri, Mar 16, 2018 at 8:44 PM, Michael Gugino < > mgug...@redhat.com> > >> >> > wrote: > >> >> >> > >> >> >> I wo
Re: Openshift Origin 3.9 rpms -> ansible playbooks
For 3.7 and below, you need to do some manual preparation steps and then the playbook you want to run is: openshift-ansible/playbooks/byo/config.yml Prerequisites: https://docs.openshift.org/latest/install_config/install/prerequisites.html Host prep: https://docs.openshift.org/latest/install_config/install/host_preparation.html I think some of the items in those pages are already done on atomic host (such as installing docker). On Fri, Mar 16, 2018 at 5:48 PM, Charles Moulliard wrote: > I see from your github repo that you use playbook committed under master > branch > as you use these commands to install ocp > > ansible-playbook -i inventory/hosts.localhost playbooks/prerequisites.yml > ansible-playbook -i inventory/hosts.localhost playbooks/deploy_cluster.yml > > Unfortunately that fails for me to install Openshift Origin v3.7 > > On Fri, Mar 16, 2018 at 10:17 PM, Michael Gugino wrote: >> >> I use this basic inventory with fedora atomic: >> https://github.com/michaelgugino/openshift-stuff/tree/master/fedora-atomic >> >> I usually deploy to AWS for testing and development. Wherever you >> deploy, your instance's hostnames need to be resolvable. >> >> I don't have any recommendations for using any specific tags. I >> usually use the head of a release branch; I very rarely use specific >> tags or commits. >> >> I don't have any general recommendations for deploying any other than >> released openshift code. If you're trying to deploy testing images / >> rpms, >> your setup is going to depend on what you're trying to accomplish. I >> highly recommend deploying released code. That is the only way it's >> going to >> 'just work.' >> >> On Fri, Mar 16, 2018 at 4:41 PM, Charles Moulliard >> wrote: >> > >> > >> > On Fri, Mar 16, 2018 at 8:57 PM, Michael Gugino >> > wrote: >> >> >> >> I typically use the head of each release branch for openshift-ansible. >> >> Most of the time that's a good approach for anything that is already >> >> released (such as 3.7). >> > >> > >> >>> So using this tagged release is a good idea then : >> >>> >> >>> https://github.com/openshift/openshift-ansible/releases/tag/openshift-ansible-3.7.38-1 >> >>> ? >> > >> >> Alternatively, you can install the >> >> openshift-ansible origin rpm on a centos host. >> > >> > >> >>> How can I do that ? >> >> >> >> >> >> I don't recommend using openshift_repos_enable_testing, it's been >> >> nothing but problems for me. I don't recommend using any testing >> >> versions of any packages either. >> > >> > >> >>> I agree as last run generayed such bad rpms installed >> > >> > Beginning of executing the playbook >> > origin.x86_643.7.0-1.0.7ed6862 >> > @centos-openshift-origin37 >> > origin-clients.x86_643.7.0-1.0.7ed6862 >> > @centos-openshift-origin37 >> > origin-master.x86_64 3.7.0-1.0.7ed6862 >> > @centos-openshift-origin37 >> > >> > Later ... >> > >> > origin.x86_643.7.1-1.el7.git.0.0a2d6a1 >> > @centos-openshift-origin37-testing >> > origin-clients.x86_643.7.1-1.el7.git.0.0a2d6a1 >> > @centos-openshift-origin37-testing >> > origin-master.x86_64 3.7.1-1.el7.git.0.0a2d6a1 >> > @centos-openshift-origin37-testing >> > origin-node.x86_64 3.7.1-1.el7.git.0.0a2d6a1 >> > @centos-openshift-origin37-testing >> > >> > >> >> >> >> >> >> For testing new origin code, I have had the best luck with Fedora >> >> Atomic 27. >> > >> > >> >>> Can you share what you did (info, doc, ...) ? >> > >> >> >> >> However, I don't think 3.9 origin is in great shape at the >> >> moment. >> >> >> >> On Fri, Mar 16, 2018 at 3:49 PM, Charles Moulliard >> >> >> >> wrote: >> >> > Do you suggest to use a tagged version of the openshift ansible git >> >> > repo >> >> > combined >> >> > with such parameters within the inventory ? >> >> > >> >> > E.g >> >> > >> >> > git clone -b >> >> > >> >> > >> >> > https://github.com/openshift/openshift-ansible/releases/tag/openshift-ansible-3.7.38-1 >> >> > >> >> > inventory >> >> > === >> >> > openshift_repos_enable_testing = true >> >> > containerized = false >> >> > openshift_release = v3.7 >> >> > openshift_pkg_version = "-3.7.0-1.0.7ed6862" # See -> >> >> > https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/ >> >> > openshift_deployment_type = origin >> >> > ... >> >> > >> >> > ansible-playbook -i inventory >> >> > openshift-ansible/playbooks/byo/config.yml >> >> > >> >> > On Fri, Mar 16, 2018 at 8:44 PM, Michael Gugino >> >> > wrote: >> >> >> >> >> >> I would start again with new hosts, probably the easiest way >> >> >> forward. >> >> >> I recommend using the released versions if you are not comfortable >> >> >> with troubleshooting openshift-ansible. >> >> >> >> >> >> On Fri, Mar 16, 2018 at 3:29 PM, Charles Moulliard >> >> >> >> >> >> wrote: >> >> >> > Yep. I did a mistake but I have cleaned my machine and did a new >> >> >> > deployment >> >> >> > but we a get weird error
Re: Openshift Origin 3.9 rpms -> ansible playbooks
I see from your github repo that you use playbook committed under master branch as you use these commands to install ocp ansible-playbook -i inventory/hosts.localhost playbooks/prerequisites.yml ansible-playbook -i inventory/hosts.localhost playbooks/deploy_cluster.yml Unfortunately that fails for me to install Openshift Origin v3.7 On Fri, Mar 16, 2018 at 10:17 PM, Michael Gugino wrote: > I use this basic inventory with fedora atomic: > https://github.com/michaelgugino/openshift-stuff/tree/master/fedora-atomic > > I usually deploy to AWS for testing and development. Wherever you > deploy, your instance's hostnames need to be resolvable. > > I don't have any recommendations for using any specific tags. I > usually use the head of a release branch; I very rarely use specific > tags or commits. > > I don't have any general recommendations for deploying any other than > released openshift code. If you're trying to deploy testing images / > rpms, > your setup is going to depend on what you're trying to accomplish. I > highly recommend deploying released code. That is the only way it's > going to > 'just work.' > > On Fri, Mar 16, 2018 at 4:41 PM, Charles Moulliard > wrote: > > > > > > On Fri, Mar 16, 2018 at 8:57 PM, Michael Gugino > wrote: > >> > >> I typically use the head of each release branch for openshift-ansible. > >> Most of the time that's a good approach for anything that is already > >> released (such as 3.7). > > > > > >>> So using this tagged release is a good idea then : > >>> https://github.com/openshift/openshift-ansible/releases/ > tag/openshift-ansible-3.7.38-1 > >>> ? > > > >> Alternatively, you can install the > >> openshift-ansible origin rpm on a centos host. > > > > > >>> How can I do that ? > >> > >> > >> I don't recommend using openshift_repos_enable_testing, it's been > >> nothing but problems for me. I don't recommend using any testing > >> versions of any packages either. > > > > > >>> I agree as last run generayed such bad rpms installed > > > > Beginning of executing the playbook > > origin.x86_643.7.0-1.0.7ed6862 > > @centos-openshift-origin37 > > origin-clients.x86_643.7.0-1.0.7ed6862 > > @centos-openshift-origin37 > > origin-master.x86_64 3.7.0-1.0.7ed6862 > > @centos-openshift-origin37 > > > > Later ... > > > > origin.x86_643.7.1-1.el7.git.0.0a2d6a1 > > @centos-openshift-origin37-testing > > origin-clients.x86_643.7.1-1.el7.git.0.0a2d6a1 > > @centos-openshift-origin37-testing > > origin-master.x86_64 3.7.1-1.el7.git.0.0a2d6a1 > > @centos-openshift-origin37-testing > > origin-node.x86_64 3.7.1-1.el7.git.0.0a2d6a1 > > @centos-openshift-origin37-testing > > > > > >> > >> > >> For testing new origin code, I have had the best luck with Fedora > >> Atomic 27. > > > > > >>> Can you share what you did (info, doc, ...) ? > > > >> > >> However, I don't think 3.9 origin is in great shape at the > >> moment. > >> > >> On Fri, Mar 16, 2018 at 3:49 PM, Charles Moulliard > > >> wrote: > >> > Do you suggest to use a tagged version of the openshift ansible git > repo > >> > combined > >> > with such parameters within the inventory ? > >> > > >> > E.g > >> > > >> > git clone -b > >> > > >> > https://github.com/openshift/openshift-ansible/releases/ > tag/openshift-ansible-3.7.38-1 > >> > > >> > inventory > >> > === > >> > openshift_repos_enable_testing = true > >> > containerized = false > >> > openshift_release = v3.7 > >> > openshift_pkg_version = "-3.7.0-1.0.7ed6862" # See -> > >> > https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/ > >> > openshift_deployment_type = origin > >> > ... > >> > > >> > ansible-playbook -i inventory openshift-ansible/playbooks/ > byo/config.yml > >> > > >> > On Fri, Mar 16, 2018 at 8:44 PM, Michael Gugino > >> > wrote: > >> >> > >> >> I would start again with new hosts, probably the easiest way forward. > >> >> I recommend using the released versions if you are not comfortable > >> >> with troubleshooting openshift-ansible. > >> >> > >> >> On Fri, Mar 16, 2018 at 3:29 PM, Charles Moulliard > >> >> > >> >> wrote: > >> >> > Yep. I did a mistake but I have cleaned my machine and did a new > >> >> > deployment > >> >> > but we a get weird error again > >> >> > > >> >> > INSTALLER STATUS > >> >> > > >> >> > > >> >> > > > > > >> >> > Initialization : Complete > >> >> > Health Check : Complete > >> >> > etcd Install : Complete > >> >> > Master Install : Complete > >> >> > Master Additional Install : Complete > >> >> > Node Install : In Progress > >> >> > This phase can be restarted by running: > >> >> > playbooks/byo/
Re: Openshift Origin 3.9 rpms -> ansible playbooks
I use this basic inventory with fedora atomic: https://github.com/michaelgugino/openshift-stuff/tree/master/fedora-atomic I usually deploy to AWS for testing and development. Wherever you deploy, your instance's hostnames need to be resolvable. I don't have any recommendations for using any specific tags. I usually use the head of a release branch; I very rarely use specific tags or commits. I don't have any general recommendations for deploying any other than released openshift code. If you're trying to deploy testing images / rpms, your setup is going to depend on what you're trying to accomplish. I highly recommend deploying released code. That is the only way it's going to 'just work.' On Fri, Mar 16, 2018 at 4:41 PM, Charles Moulliard wrote: > > > On Fri, Mar 16, 2018 at 8:57 PM, Michael Gugino wrote: >> >> I typically use the head of each release branch for openshift-ansible. >> Most of the time that's a good approach for anything that is already >> released (such as 3.7). > > >>> So using this tagged release is a good idea then : >>> https://github.com/openshift/openshift-ansible/releases/tag/openshift-ansible-3.7.38-1 >>> ? > >> Alternatively, you can install the >> openshift-ansible origin rpm on a centos host. > > >>> How can I do that ? >> >> >> I don't recommend using openshift_repos_enable_testing, it's been >> nothing but problems for me. I don't recommend using any testing >> versions of any packages either. > > >>> I agree as last run generayed such bad rpms installed > > Beginning of executing the playbook > origin.x86_643.7.0-1.0.7ed6862 > @centos-openshift-origin37 > origin-clients.x86_643.7.0-1.0.7ed6862 > @centos-openshift-origin37 > origin-master.x86_64 3.7.0-1.0.7ed6862 > @centos-openshift-origin37 > > Later ... > > origin.x86_643.7.1-1.el7.git.0.0a2d6a1 > @centos-openshift-origin37-testing > origin-clients.x86_643.7.1-1.el7.git.0.0a2d6a1 > @centos-openshift-origin37-testing > origin-master.x86_64 3.7.1-1.el7.git.0.0a2d6a1 > @centos-openshift-origin37-testing > origin-node.x86_64 3.7.1-1.el7.git.0.0a2d6a1 > @centos-openshift-origin37-testing > > >> >> >> For testing new origin code, I have had the best luck with Fedora >> Atomic 27. > > >>> Can you share what you did (info, doc, ...) ? > >> >> However, I don't think 3.9 origin is in great shape at the >> moment. >> >> On Fri, Mar 16, 2018 at 3:49 PM, Charles Moulliard >> wrote: >> > Do you suggest to use a tagged version of the openshift ansible git repo >> > combined >> > with such parameters within the inventory ? >> > >> > E.g >> > >> > git clone -b >> > >> > https://github.com/openshift/openshift-ansible/releases/tag/openshift-ansible-3.7.38-1 >> > >> > inventory >> > === >> > openshift_repos_enable_testing = true >> > containerized = false >> > openshift_release = v3.7 >> > openshift_pkg_version = "-3.7.0-1.0.7ed6862" # See -> >> > https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/ >> > openshift_deployment_type = origin >> > ... >> > >> > ansible-playbook -i inventory openshift-ansible/playbooks/byo/config.yml >> > >> > On Fri, Mar 16, 2018 at 8:44 PM, Michael Gugino >> > wrote: >> >> >> >> I would start again with new hosts, probably the easiest way forward. >> >> I recommend using the released versions if you are not comfortable >> >> with troubleshooting openshift-ansible. >> >> >> >> On Fri, Mar 16, 2018 at 3:29 PM, Charles Moulliard >> >> >> >> wrote: >> >> > Yep. I did a mistake but I have cleaned my machine and did a new >> >> > deployment >> >> > but we a get weird error again >> >> > >> >> > INSTALLER STATUS >> >> > >> >> > >> >> > >> >> > Initialization : Complete >> >> > Health Check : Complete >> >> > etcd Install : Complete >> >> > Master Install : Complete >> >> > Master Additional Install : Complete >> >> > Node Install : In Progress >> >> > This phase can be restarted by running: >> >> > playbooks/byo/openshift-node/config.yml >> >> > >> >> > >> >> > >> >> > Failure summary: >> >> > >> >> > >> >> > 1. Hosts:192.168.99.50 >> >> > Play: Configure nodes >> >> > Task: Install sdn-ovs package >> >> > Message: Error: Package: >> >> > origin-sdn-ovs-3.7.0-1.0.7ed6862.x86_64 >> >> > (centos-openshift-origin37) >> >> > Requires: origin-node = 3.7.0-1.0.7ed6862 >> >> > Installed: >> >> > origin-node-3.7.1-1.el7.git.0.0a2d6a1.x86_64 >> >> > (@centos-openshift-origin37-testing) >> >> > origin-node = 3.7.1-1.el7.git.0.0a2d6a1 >> >> > Availa
Re: Openshift Origin 3.9 rpms -> ansible playbooks
On Fri, Mar 16, 2018 at 8:57 PM, Michael Gugino wrote: > I typically use the head of each release branch for openshift-ansible. > Most of the time that's a good approach for anything that is already > released (such as 3.7). >> So using this tagged release is a good idea then : https://github.com/ openshift/openshift-ansible/releases/tag/openshift-ansible-3.7.38-1 ? Alternatively, you can install the > openshift-ansible origin rpm on a centos host. > >> How can I do that ? > > I don't recommend using openshift_repos_enable_testing, it's been > nothing but problems for me. I don't recommend using any testing > versions of any packages either. > >> I agree as last run generayed such bad rpms installed Beginning of executing the playbook origin.x86_643.7.0-1.0.7ed6862 @centos-openshift-origin37 origin-clients.x86_643.7.0-1.0.7ed6862 @centos-openshift-origin37 origin-master.x86_64 3.7.0-1.0.7ed6862 @centos-openshift-origin37 Later ... origin.x86_643.7.1-1.el7.git.0.0a2d6a1 @centos-openshift-origin37-testing origin-clients.x86_643.7.1-1.el7.git.0.0a2d6a1 @centos-openshift-origin37-testing origin-master.x86_64 3.7.1-1.el7.git.0.0a2d6a1 @centos-openshift-origin37-testing origin-node.x86_64 3.7.1-1.el7.git.0.0a2d6a1 @centos-openshift-origin37-testing > > For testing new origin code, I have had the best luck with Fedora > Atomic 27. >> Can you share what you did (info, doc, ...) ? > However, I don't think 3.9 origin is in great shape at the > moment. > > On Fri, Mar 16, 2018 at 3:49 PM, Charles Moulliard > wrote: > > Do you suggest to use a tagged version of the openshift ansible git repo > > combined > > with such parameters within the inventory ? > > > > E.g > > > > git clone -b > > https://github.com/openshift/openshift-ansible/releases/tag/ > openshift-ansible-3.7.38-1 > > > > inventory > > === > > openshift_repos_enable_testing = true > > containerized = false > > openshift_release = v3.7 > > openshift_pkg_version = "-3.7.0-1.0.7ed6862" # See -> > > https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/ > > openshift_deployment_type = origin > > ... > > > > ansible-playbook -i inventory openshift-ansible/playbooks/byo/config.yml > > > > On Fri, Mar 16, 2018 at 8:44 PM, Michael Gugino > wrote: > >> > >> I would start again with new hosts, probably the easiest way forward. > >> I recommend using the released versions if you are not comfortable > >> with troubleshooting openshift-ansible. > >> > >> On Fri, Mar 16, 2018 at 3:29 PM, Charles Moulliard > > >> wrote: > >> > Yep. I did a mistake but I have cleaned my machine and did a new > >> > deployment > >> > but we a get weird error again > >> > > >> > INSTALLER STATUS > >> > > >> > > > > > >> > Initialization : Complete > >> > Health Check : Complete > >> > etcd Install : Complete > >> > Master Install : Complete > >> > Master Additional Install : Complete > >> > Node Install : In Progress > >> > This phase can be restarted by running: > >> > playbooks/byo/openshift-node/config.yml > >> > > >> > > >> > > >> > Failure summary: > >> > > >> > > >> > 1. Hosts:192.168.99.50 > >> > Play: Configure nodes > >> > Task: Install sdn-ovs package > >> > Message: Error: Package: origin-sdn-ovs-3.7.0-1.0.7ed68 > 62.x86_64 > >> > (centos-openshift-origin37) > >> > Requires: origin-node = 3.7.0-1.0.7ed6862 > >> > Installed: > >> > origin-node-3.7.1-1.el7.git.0.0a2d6a1.x86_64 > >> > (@centos-openshift-origin37-testing) > >> > origin-node = 3.7.1-1.el7.git.0.0a2d6a1 > >> > Available: > >> > origin-node-v3.7.1-0.3.7.1.el7.git.0.b113c29.x86_64 > >> > (centos-openshift-origin37-testing) > >> > > >> > So it seems that the version calculated and downloaded from this repo > >> > https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/ > is > >> > not > >> > consistent > >> > > >> > Is there a way to download / install properly all the required origin > >> > rmps > >> > as ansible playbook fails ? > >> > > >> > > >> > On Fri, Mar 16, 2018 at 8:24 PM, Michael Gugino > >> > wrote: > >> >> > >> >> Charles, > >> >> > >> >> You cannot install 3.9 from the openshift-ansible 3.7 branch. If > >> >> you want to install 3.9, you need to use the openshift-ansible 3.9 > >> >> branch, which is not officially released yet. > >> >> > >> >> There is not a testing repo for each release of openshift; just the > >> >> latest unreleased version. If you enable testing repos on the 3.7 > >> >>
Re: Openshift Origin 3.9 rpms -> ansible playbooks
I typically use the head of each release branch for openshift-ansible. Most of the time that's a good approach for anything that is already released (such as 3.7). Alternatively, you can install the openshift-ansible origin rpm on a centos host. I don't recommend using openshift_repos_enable_testing, it's been nothing but problems for me. I don't recommend using any testing versions of any packages either. For testing new origin code, I have had the best luck with Fedora Atomic 27. However, I don't think 3.9 origin is in great shape at the moment. On Fri, Mar 16, 2018 at 3:49 PM, Charles Moulliard wrote: > Do you suggest to use a tagged version of the openshift ansible git repo > combined > with such parameters within the inventory ? > > E.g > > git clone -b > https://github.com/openshift/openshift-ansible/releases/tag/openshift-ansible-3.7.38-1 > > inventory > === > openshift_repos_enable_testing = true > containerized = false > openshift_release = v3.7 > openshift_pkg_version = "-3.7.0-1.0.7ed6862" # See -> > https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/ > openshift_deployment_type = origin > ... > > ansible-playbook -i inventory openshift-ansible/playbooks/byo/config.yml > > On Fri, Mar 16, 2018 at 8:44 PM, Michael Gugino wrote: >> >> I would start again with new hosts, probably the easiest way forward. >> I recommend using the released versions if you are not comfortable >> with troubleshooting openshift-ansible. >> >> On Fri, Mar 16, 2018 at 3:29 PM, Charles Moulliard >> wrote: >> > Yep. I did a mistake but I have cleaned my machine and did a new >> > deployment >> > but we a get weird error again >> > >> > INSTALLER STATUS >> > >> > >> > Initialization : Complete >> > Health Check : Complete >> > etcd Install : Complete >> > Master Install : Complete >> > Master Additional Install : Complete >> > Node Install : In Progress >> > This phase can be restarted by running: >> > playbooks/byo/openshift-node/config.yml >> > >> > >> > >> > Failure summary: >> > >> > >> > 1. Hosts:192.168.99.50 >> > Play: Configure nodes >> > Task: Install sdn-ovs package >> > Message: Error: Package: origin-sdn-ovs-3.7.0-1.0.7ed6862.x86_64 >> > (centos-openshift-origin37) >> > Requires: origin-node = 3.7.0-1.0.7ed6862 >> > Installed: >> > origin-node-3.7.1-1.el7.git.0.0a2d6a1.x86_64 >> > (@centos-openshift-origin37-testing) >> > origin-node = 3.7.1-1.el7.git.0.0a2d6a1 >> > Available: >> > origin-node-v3.7.1-0.3.7.1.el7.git.0.b113c29.x86_64 >> > (centos-openshift-origin37-testing) >> > >> > So it seems that the version calculated and downloaded from this repo >> > https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/ is >> > not >> > consistent >> > >> > Is there a way to download / install properly all the required origin >> > rmps >> > as ansible playbook fails ? >> > >> > >> > On Fri, Mar 16, 2018 at 8:24 PM, Michael Gugino >> > wrote: >> >> >> >> Charles, >> >> >> >> You cannot install 3.9 from the openshift-ansible 3.7 branch. If >> >> you want to install 3.9, you need to use the openshift-ansible 3.9 >> >> branch, which is not officially released yet. >> >> >> >> There is not a testing repo for each release of openshift; just the >> >> latest unreleased version. If you enable testing repos on the 3.7 >> >> branch, you'll end up getting 3.9 packages which is what's happening >> >> here. >> >> >> >> On Fri, Mar 16, 2018 at 11:32 AM, Charles Moulliard >> >> >> >> wrote: >> >> > Hi, >> >> > >> >> > Are the OpenShift Origin v3.9 rpms available from a repo ? >> >> > How can we get them in order to install openshift cluster using >> >> > ansible >> >> > playbook ? >> >> > >> >> > Regards >> >> > >> >> > Charles >> >> > >> >> > ___ >> >> > dev mailing list >> >> > dev@lists.openshift.redhat.com >> >> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >> >> > >> >> >> >> >> >> >> >> -- >> >> Michael Gugino >> >> Senior Software Engineer - OpenShift >> >> mgug...@redhat.com >> >> 540-846-0304 >> > >> > >> >> >> >> -- >> Michael Gugino >> Senior Software Engineer - OpenShift >> mgug...@redhat.com >> 540-846-0304 > > -- Michael Gugino Senior Software Engineer - OpenShift mgug...@redhat.com 540-846-0304 ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Re: Openshift Origin 3.9 rpms -> ansible playbooks
Do you suggest to use a tagged version of the openshift ansible git repo combined with such parameters within the inventory ? E.g git clone -b https://github.com/openshift/openshift-ansible/releases/tag/openshift-ansible-3.7.38-1 inventory === openshift_repos_enable_testing = true containerized = false openshift_release = v3.7 openshift_pkg_version = "-3.7.0-1.0.7ed6862" # See -> https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/ openshift_deployment_type = origin ... ansible-playbook -i inventory openshift-ansible/playbooks/byo/config.yml On Fri, Mar 16, 2018 at 8:44 PM, Michael Gugino wrote: > I would start again with new hosts, probably the easiest way forward. > I recommend using the released versions if you are not comfortable > with troubleshooting openshift-ansible. > > On Fri, Mar 16, 2018 at 3:29 PM, Charles Moulliard > wrote: > > Yep. I did a mistake but I have cleaned my machine and did a new > deployment > > but we a get weird error again > > > > INSTALLER STATUS > > > > > > > Initialization : Complete > > Health Check : Complete > > etcd Install : Complete > > Master Install : Complete > > Master Additional Install : Complete > > Node Install : In Progress > > This phase can be restarted by running: > > playbooks/byo/openshift-node/config.yml > > > > > > > > Failure summary: > > > > > > 1. Hosts:192.168.99.50 > > Play: Configure nodes > > Task: Install sdn-ovs package > > Message: Error: Package: origin-sdn-ovs-3.7.0-1.0.7ed6862.x86_64 > > (centos-openshift-origin37) > > Requires: origin-node = 3.7.0-1.0.7ed6862 > > Installed: > > origin-node-3.7.1-1.el7.git.0.0a2d6a1.x86_64 > > (@centos-openshift-origin37-testing) > > origin-node = 3.7.1-1.el7.git.0.0a2d6a1 > > Available: > > origin-node-v3.7.1-0.3.7.1.el7.git.0.b113c29.x86_64 > > (centos-openshift-origin37-testing) > > > > So it seems that the version calculated and downloaded from this repo > > https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/ > is not > > consistent > > > > Is there a way to download / install properly all the required origin > rmps > > as ansible playbook fails ? > > > > > > On Fri, Mar 16, 2018 at 8:24 PM, Michael Gugino > wrote: > >> > >> Charles, > >> > >> You cannot install 3.9 from the openshift-ansible 3.7 branch. If > >> you want to install 3.9, you need to use the openshift-ansible 3.9 > >> branch, which is not officially released yet. > >> > >> There is not a testing repo for each release of openshift; just the > >> latest unreleased version. If you enable testing repos on the 3.7 > >> branch, you'll end up getting 3.9 packages which is what's happening > >> here. > >> > >> On Fri, Mar 16, 2018 at 11:32 AM, Charles Moulliard < > cmoul...@redhat.com> > >> wrote: > >> > Hi, > >> > > >> > Are the OpenShift Origin v3.9 rpms available from a repo ? > >> > How can we get them in order to install openshift cluster using > ansible > >> > playbook ? > >> > > >> > Regards > >> > > >> > Charles > >> > > >> > ___ > >> > dev mailing list > >> > dev@lists.openshift.redhat.com > >> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > >> > > >> > >> > >> > >> -- > >> Michael Gugino > >> Senior Software Engineer - OpenShift > >> mgug...@redhat.com > >> 540-846-0304 > > > > > > > > -- > Michael Gugino > Senior Software Engineer - OpenShift > mgug...@redhat.com > 540-846-0304 > ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Re: Openshift Origin 3.9 rpms -> ansible playbooks
I would start again with new hosts, probably the easiest way forward. I recommend using the released versions if you are not comfortable with troubleshooting openshift-ansible. On Fri, Mar 16, 2018 at 3:29 PM, Charles Moulliard wrote: > Yep. I did a mistake but I have cleaned my machine and did a new deployment > but we a get weird error again > > INSTALLER STATUS > > Initialization : Complete > Health Check : Complete > etcd Install : Complete > Master Install : Complete > Master Additional Install : Complete > Node Install : In Progress > This phase can be restarted by running: > playbooks/byo/openshift-node/config.yml > > > > Failure summary: > > > 1. Hosts:192.168.99.50 > Play: Configure nodes > Task: Install sdn-ovs package > Message: Error: Package: origin-sdn-ovs-3.7.0-1.0.7ed6862.x86_64 > (centos-openshift-origin37) > Requires: origin-node = 3.7.0-1.0.7ed6862 > Installed: > origin-node-3.7.1-1.el7.git.0.0a2d6a1.x86_64 > (@centos-openshift-origin37-testing) > origin-node = 3.7.1-1.el7.git.0.0a2d6a1 > Available: > origin-node-v3.7.1-0.3.7.1.el7.git.0.b113c29.x86_64 > (centos-openshift-origin37-testing) > > So it seems that the version calculated and downloaded from this repo > https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/ is not > consistent > > Is there a way to download / install properly all the required origin rmps > as ansible playbook fails ? > > > On Fri, Mar 16, 2018 at 8:24 PM, Michael Gugino wrote: >> >> Charles, >> >> You cannot install 3.9 from the openshift-ansible 3.7 branch. If >> you want to install 3.9, you need to use the openshift-ansible 3.9 >> branch, which is not officially released yet. >> >> There is not a testing repo for each release of openshift; just the >> latest unreleased version. If you enable testing repos on the 3.7 >> branch, you'll end up getting 3.9 packages which is what's happening >> here. >> >> On Fri, Mar 16, 2018 at 11:32 AM, Charles Moulliard >> wrote: >> > Hi, >> > >> > Are the OpenShift Origin v3.9 rpms available from a repo ? >> > How can we get them in order to install openshift cluster using ansible >> > playbook ? >> > >> > Regards >> > >> > Charles >> > >> > ___ >> > dev mailing list >> > dev@lists.openshift.redhat.com >> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >> > >> >> >> >> -- >> Michael Gugino >> Senior Software Engineer - OpenShift >> mgug...@redhat.com >> 540-846-0304 > > -- Michael Gugino Senior Software Engineer - OpenShift mgug...@redhat.com 540-846-0304 ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Re: Openshift Origin 3.9 rpms -> ansible playbooks
Yep. I did a mistake but I have cleaned my machine and did a new deployment but we a get weird error again INSTALLER STATUS Initialization : Complete Health Check : Complete etcd Install : Complete Master Install : Complete Master Additional Install : Complete Node Install : In Progress This phase can be restarted by running: playbooks/byo/openshift-node/config.yml Failure summary: 1. Hosts:192.168.99.50 Play: Configure nodes Task: Install sdn-ovs package Message: Error: Package: origin-sdn-ovs-3.7.0-1.0.7ed6862.x86_64 (centos-openshift-origin37) Requires: origin-node = 3.7.0-1.0.7ed6862 Installed: origin-node-3.7.1-1.el7.git.0.0a2d6a1.x86_64 (@centos-openshift-origin37-testing) origin-node = 3.7.1-1.el7.git.0.0a2d6a1 Available: origin-node-v3.7.1-0.3.7.1.el7.git.0.b113c29.x86_64 (centos-openshift-origin37-testing) So it seems that the version calculated and downloaded from this repo https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/ is not consistent Is there a way to download / install properly all the required origin rmps as ansible playbook fails ? On Fri, Mar 16, 2018 at 8:24 PM, Michael Gugino wrote: > Charles, > > You cannot install 3.9 from the openshift-ansible 3.7 branch. If > you want to install 3.9, you need to use the openshift-ansible 3.9 > branch, which is not officially released yet. > > There is not a testing repo for each release of openshift; just the > latest unreleased version. If you enable testing repos on the 3.7 > branch, you'll end up getting 3.9 packages which is what's happening > here. > > On Fri, Mar 16, 2018 at 11:32 AM, Charles Moulliard > wrote: > > Hi, > > > > Are the OpenShift Origin v3.9 rpms available from a repo ? > > How can we get them in order to install openshift cluster using ansible > > playbook ? > > > > Regards > > > > Charles > > > > ___ > > dev mailing list > > dev@lists.openshift.redhat.com > > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > > > > > -- > Michael Gugino > Senior Software Engineer - OpenShift > mgug...@redhat.com > 540-846-0304 > ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Re: Openshift Origin 3.9 rpms -> ansible playbooks
Charles, You cannot install 3.9 from the openshift-ansible 3.7 branch. If you want to install 3.9, you need to use the openshift-ansible 3.9 branch, which is not officially released yet. There is not a testing repo for each release of openshift; just the latest unreleased version. If you enable testing repos on the 3.7 branch, you'll end up getting 3.9 packages which is what's happening here. On Fri, Mar 16, 2018 at 11:32 AM, Charles Moulliard wrote: > Hi, > > Are the OpenShift Origin v3.9 rpms available from a repo ? > How can we get them in order to install openshift cluster using ansible > playbook ? > > Regards > > Charles > > ___ > dev mailing list > dev@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > -- Michael Gugino Senior Software Engineer - OpenShift mgug...@redhat.com 540-846-0304 ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Re: Openshift Origin 3.9 rpms -> ansible playbooks
It's there, in both the origin39-testing area (which isn't getting
used), as well as the origin-testing area (which is getting used),
https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin39/origin-sdn-ovs-3.9.0-0.alpha.4.el7.git.23454.881f1dd.x86_64.rpm
https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin/origin-sdn-ovs-3.9.0-0.alpha.4.el7.git.23454.881f1dd.x86_64.rpm
I don't know why it isn't seeing it.
I'll let the openshift-ansible people take it from here. They should know why.
Troy
On Fri, Mar 16, 2018 at 9:12 AM, Charles Moulliard wrote:
> It seems that a rpm is missing for origin-sdn when we run openshift-ansible
> 3.7
>
> TASK [openshift_node : Install sdn-ovs package]
>
> FAILED - RETRYING: Install sdn-ovs package (2 retries left).
> FAILED - RETRYING: Install sdn-ovs package (1 retries left).
> fatal: [192.168.99.50]: FAILED! => {"attempts": 2, "changed": false, "msg":
> "Error: Package: origin-sdn-ovs-3.7.0-1.0.7ed6862.x86_64
> (centos-openshift-origin)\n Requires: origin-node =
> 3.7.0-1.0.7ed6862\n Installed:
> origin-node-3.9.0-0.alpha.4.el7.git.23454.881f1dd.x86_64
> (@centos-openshift-origin-testing)\n origin-node =
> 3.9.0-0.alpha.4.el7.git.23454.881f1dd\n Available:
> origin-node-v3.7.1-0.3.7.1.el7.git.0.b113c29.x86_64
> (centos-openshift-origin37-testing)\n origin-node =
> v3.7.1-0.3.7.1.el7.git.0.b113c29\n Available:
> origin-node-1.1.5-1.git.9912.4229825.el7.x86_64
> (centos-openshift-origin-testing)\n origin-node =
> 1.1.5-1.git.9912.4229825.el7\n Available:
> origin-node-1.1.6-1.git..9c5694f.el7.x86_64
> (centos-openshift-origin-testing)\n origin-node =
> 1.1.6-1.git..9c5694f.el7\n Available:
> origin-node-1.2.0-1.git.10183.7386b49.el7.x86_64
> (centos-openshift-origin-testing)\n origin-node =
> 1.2.0-1.git.10183.7386b49.el7\n Available:
> origin-node-1.2.0-2.el7.x86_64 (centos-openshift-origin-testing)\n
> origin-node = 1.2.0-2.el7\n Available:
> origin-node-1.2.0-3.el7.x86_64 (centos-openshift-origin-testing)\n
> origin-node = 1.2.0-3.el7\n Available:
> origin-node-1.2.0-4.el7.x86_64 (centos-openshift-origin-testing)\n
> origin-node = 1.2.0-4.el7\n Available:
> origin-node-1.2.1-1.el7.x86_64 (centos-openshift-origin-testing)\n
> origin-node = 1.2.1-1.el7\n Available:
> origin-node-1.3.0-2.el7.x86_64 (centos-openshift-origin-testing)\n
> origin-node = 1.3.0-2.el7\n Available:
> origin-node-1.3.0-3.el7.x86_64 (centos-openshift-origin-testing)\n
> origin-node = 1.3.0-3.el7\n Available:
> origin-node-1.3.0-4.el7.x86_64 (centos-openshift-origin-testing)\n
> origin-node = 1.3.0-4.el7\n Available:
> origin-node-1.3.1-1.el7.x86_64 (centos-openshift-origin-testing)\n
> origin-node = 1.3.1-1.el7\n Available:
> origin-node-1.3.3-1.el7.x86_64 (centos-openshift-origin-testing)\n
> origin-node = 1.3.3-1.el7\n Available:
> origin-node-1.4.0-2.el7.x86_64 (centos-openshift-origin-testing)\n
> origin-node = 1.4.0-2.el7\n Available:
> origin-node-1.4.1-1.el7.x86_64 (centos-openshift-origin-testing)\n
> origin-node = 1.4.1-1.el7\n Available:
> origin-node-1.5.0-0.4.el7.x86_64 (centos-openshift-origin-testing)\n
> origin-node = 1.5.0-0.4.el7\n Available:
> origin-node-1.5.0-0.7.rc1.x86_64 (centos-openshift-origin-testing)\n
> origin-node = 1.5.0-0.7.rc1\n Available:
> origin-node-1.5.0-1.el7.x86_64 (centos-openshift-origin-testing)\n
> origin-node = 1.5.0-1.el7\n Available:
> origin-node-1.5.1-1.el7.x86_64 (centos-openshift-origin-testing)\n
> origin-node = 1.5.1-1.el7\n Available:
> origin-node-3.6.0-1.0.c4dd4cf.x86_64 (centos-openshift-origin)\n
> origin-node = 3.6.0-1.0.c4dd4cf\n Available:
> origin-node-3.6.1-1.0.008f2d5.x86_64 (centos-openshift-origin)\n
> origin-node = 3.6.1-1.0.008f2d5\n Available:
> origin-node-3.7.0-0.alpha.1.859.5d7f1b8.x86_64
> (centos-openshift-origin-testing)\n origin-node =
> 3.7.0-0.alpha.1.859.5d7f1b8\n Available:
> origin-node-3.7.0-0.rc.0.0.e92d5c5.x86_64
> (centos-openshift-origin-testing)\n origin-node =
> 3.7.0-0.rc.0.0.e92d5c5\n Available:
> origin-node-3.7.0-1.0.7ed6862.x86_64 (centos-openshift-origin)\n
> origin-node = 3.7.0-1.0.7ed6862\n Available:
> origin-node-3.7.1-1.el7.git.0.0a2d6a1.x86_64
> (centos-openshift-origin37-testing)\n origin-node =
> 3.7.1-1.el7.git.0.0a2d6a1\n", "rc": 1, "results": ["Loaded plugins:
> fastestmirror\nLoading mirror speeds from cached hostfile\n * base:
> centos.mirror.fr.planethoster.net\n * extras:
> centos.mirror.fr.p
Re: Openshift Origin 3.9 rpms -> ansible playbooks
It seems that a rpm is missing for origin-sdn when we run openshift-ansible
3.7
TASK [openshift_node : Install sdn-ovs package]
FAILED - RETRYING: Install sdn-ovs package (2 retries left).
FAILED - RETRYING: Install sdn-ovs package (1 retries left).
fatal: [192.168.99.50]: FAILED! => {"attempts": 2, "changed": false, "msg":
"Error: Package: origin-sdn-ovs-3.7.0-1.0.7ed6862.x86_64
(centos-openshift-origin)\n Requires: origin-node =
3.7.0-1.0.7ed6862\n Installed:
origin-node-3.9.0-0.alpha.4.el7.git.23454.881f1dd.x86_64
(@centos-openshift-origin-testing)\n origin-node =
3.9.0-0.alpha.4.el7.git.23454.881f1dd\n Available:
origin-node-v3.7.1-0.3.7.1.el7.git.0.b113c29.x86_64
(centos-openshift-origin37-testing)\n origin-node =
v3.7.1-0.3.7.1.el7.git.0.b113c29\n Available:
origin-node-1.1.5-1.git.9912.4229825.el7.x86_64
(centos-openshift-origin-testing)\n origin-node =
1.1.5-1.git.9912.4229825.el7\n Available:
origin-node-1.1.6-1.git..9c5694f.el7.x86_64
(centos-openshift-origin-testing)\n origin-node =
1.1.6-1.git..9c5694f.el7\n Available:
origin-node-1.2.0-1.git.10183.7386b49.el7.x86_64
(centos-openshift-origin-testing)\n origin-node =
1.2.0-1.git.10183.7386b49.el7\n Available:
origin-node-1.2.0-2.el7.x86_64 (centos-openshift-origin-testing)\n
origin-node = 1.2.0-2.el7\n Available:
origin-node-1.2.0-3.el7.x86_64 (centos-openshift-origin-testing)\n
origin-node = 1.2.0-3.el7\n Available:
origin-node-1.2.0-4.el7.x86_64 (centos-openshift-origin-testing)\n
origin-node = 1.2.0-4.el7\n Available:
origin-node-1.2.1-1.el7.x86_64 (centos-openshift-origin-testing)\n
origin-node = 1.2.1-1.el7\n Available:
origin-node-1.3.0-2.el7.x86_64 (centos-openshift-origin-testing)\n
origin-node = 1.3.0-2.el7\n Available:
origin-node-1.3.0-3.el7.x86_64 (centos-openshift-origin-testing)\n
origin-node = 1.3.0-3.el7\n Available:
origin-node-1.3.0-4.el7.x86_64 (centos-openshift-origin-testing)\n
origin-node = 1.3.0-4.el7\n Available:
origin-node-1.3.1-1.el7.x86_64 (centos-openshift-origin-testing)\n
origin-node = 1.3.1-1.el7\n Available:
origin-node-1.3.3-1.el7.x86_64 (centos-openshift-origin-testing)\n
origin-node = 1.3.3-1.el7\n Available:
origin-node-1.4.0-2.el7.x86_64 (centos-openshift-origin-testing)\n
origin-node = 1.4.0-2.el7\n Available:
origin-node-1.4.1-1.el7.x86_64 (centos-openshift-origin-testing)\n
origin-node = 1.4.1-1.el7\n Available:
origin-node-1.5.0-0.4.el7.x86_64 (centos-openshift-origin-testing)\n
origin-node = 1.5.0-0.4.el7\n Available:
origin-node-1.5.0-0.7.rc1.x86_64 (centos-openshift-origin-testing)\n
origin-node = 1.5.0-0.7.rc1\n Available:
origin-node-1.5.0-1.el7.x86_64 (centos-openshift-origin-testing)\n
origin-node = 1.5.0-1.el7\n Available:
origin-node-1.5.1-1.el7.x86_64 (centos-openshift-origin-testing)\n
origin-node = 1.5.1-1.el7\n Available:
origin-node-3.6.0-1.0.c4dd4cf.x86_64 (centos-openshift-origin)\n
origin-node = 3.6.0-1.0.c4dd4cf\n Available:
origin-node-3.6.1-1.0.008f2d5.x86_64 (centos-openshift-origin)\n
origin-node = 3.6.1-1.0.008f2d5\n Available:
origin-node-3.7.0-0.alpha.1.859.5d7f1b8.x86_64
(centos-openshift-origin-testing)\n origin-node =
3.7.0-0.alpha.1.859.5d7f1b8\n Available:
origin-node-3.7.0-0.rc.0.0.e92d5c5.x86_64
(centos-openshift-origin-testing)\n origin-node =
3.7.0-0.rc.0.0.e92d5c5\n Available:
origin-node-3.7.0-1.0.7ed6862.x86_64 (centos-openshift-origin)\n
origin-node = 3.7.0-1.0.7ed6862\n Available:
origin-node-3.7.1-1.el7.git.0.0a2d6a1.x86_64
(centos-openshift-origin37-testing)\n origin-node =
3.7.1-1.el7.git.0.0a2d6a1\n", "rc": 1, "results": ["Loaded plugins:
fastestmirror\nLoading mirror speeds from cached hostfile\n * base:
centos.mirror.fr.planethoster.net\n * extras:
centos.mirror.fr.planethoster.net\n * updates:
rep-centos-fr.upress.io\nResolving
Dependencies\n--> Running transaction check\n---> Package
origin-sdn-ovs.x86_64 0:3.7.0-1.0.7ed6862 will be installed\n--> Processing
Dependency: origin-node = 3.7.0-1.0.7ed6862 for package:
origin-sdn-ovs-3.7.0-1.0.7ed6862.x86_64\n--> Processing Dependency:
openvswitch >= 2.6.1 for package:
origin-sdn-ovs-3.7.0-1.0.7ed6862.x86_64\n--> Processing Dependency:
bridge-utils for package: origin-sdn-ovs-3.7.0-1.0.7ed6862.x86_64\n-->
Processing Dependency: bind-utils for package:
origin-sdn-ovs-3.7.0-1.0.7ed6862.x86_64\n--> Running transaction
check\n---> Package bind-utils.x86_
Re: Openshift Origin 3.9 rpms -> ansible playbooks
Many thanks ! On Fri, Mar 16, 2018 at 4:42 PM, Troy Dawson wrote: > On Fri, Mar 16, 2018 at 8:32 AM, Charles Moulliard > wrote: > > Hi, > > > > Are the OpenShift Origin v3.9 rpms available from a repo ? > > How can we get them in order to install openshift cluster using ansible > > playbook ? > > > > Regards > > > > Charles > > > > ___ > > dev mailing list > > dev@lists.openshift.redhat.com > > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > > > https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin39/ > > I think it's > ansible-playbook -e openshift_repos_enable_testing=true > ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Re: Openshift Origin 3.9 rpms -> ansible playbooks
On Fri, Mar 16, 2018 at 8:32 AM, Charles Moulliard wrote: > Hi, > > Are the OpenShift Origin v3.9 rpms available from a repo ? > How can we get them in order to install openshift cluster using ansible > playbook ? > > Regards > > Charles > > ___ > dev mailing list > dev@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin39/ I think it's ansible-playbook -e openshift_repos_enable_testing=true ___ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
