[rdo-dev] FYI.. tripleo jobs are cutting over to queens

[Wesley Hayutin]

FYI,
TripleO promotion jobs are cutting over to queens and master vs pike and
master.
Pike will move to the 24hr queue.

https://review.rdoproject.org/r/#/c/11775/
https://review.rdoproject.org/r/#/c/11920/
needs review  --> https://review.rdoproject.org/r/#/c/11910/
___
dev mailing list
dev@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/dev

To unsubscribe: dev-unsubscr...@lists.rdoproject.org

Re: [rdo-dev] [rdo-users] Quickstart and containers

[Boris Derzhavets]

Mentioned bellow my deployment (4 Node HA) via F27 WKS, which worked fine twice 
on 02/06  and 02/09  now fails with message in log :


2018-02-11 10:19:50 | 2018-02-11 10:19:27Z [overcloud]: CREATE_FAILED  Resource 
CREATE failed: Error: 
resources.AllNodesDeploySteps.resources.ControllerDeployment_Step1.resources[0]:
 Deployment to server failed: deploy_status_code: Deployment exited with 
non-zero status code: 2
2018-02-11 10:19:50 |
2018-02-11 10:19:50 |  Stack overcloud CREATE_FAILED
2018-02-11 10:19:50 |
2018-02-11 10:19:50 | 
overcloud.AllNodesDeploySteps.ControllerDeployment_Step1.0:
2018-02-11 10:19:50 |   resource_type: OS::Heat::StructuredDeployment
2018-02-11 10:19:50 |   physical_resource_id: 
a9db44c8-39f7-4bc6-80b8-534b2c402b48
2018-02-11 10:19:50 |   status: CREATE_FAILED
2018-02-11 10:19:50 |   status_reason: |
2018-02-11 10:19:50 | Error: resources[0]: Deployment to server failed: 
deploy_status_code : Deployment exited with non-zero status code: 2
2018-02-11 10:19:50 |   deploy_stdout: |
2018-02-11 10:19:50 | ...
2018-02-11 10:19:50 | "2018-02-11 10:19:11,526 INFO: 22569 -- 
Removing container: docker-puppet-heat_api_cfn",
2018-02-11 10:19:50 | "2018-02-11 10:19:11,558 INFO: 22569 -- 
Finished processing puppet configs for heat_api_cfn",
2018-02-11 10:19:50 | "2018-02-11 10:19:11,559 ERROR: 22567 -- 
ERROR configuring swift_ringbuilder"
2018-02-11 10:19:50 | ]
2018-02-11 10:19:50 | }
2018-02-11 10:19:50 |   to retry, use: --limit 
@/var/lib/heat-config/heat-config-ansible/a25a263b-579b-4954-bf09-25bda1c4f1c3_playbook.retry
2018-02-11 10:19:50 |
2018-02-11 10:19:50 | PLAY RECAP 
*
2018-02-11 10:19:50 | localhost  : ok=6changed=2
unreachable=0failed=1
2018-02-11 10:19:50 |
2018-02-11 10:19:50 | (truncated, view all with --long)
2018-02-11 10:19:50 |   deploy_stderr: |
2018-02-11 10:19:50 |
2018-02-11 10:19:51 | + status_code=1
2018-02-11 10:19:51 | + openstack stack list
2018-02-11 10:19:51 | + grep -q overcloud
2018-02-11 10:20:20 | + openstack stack list
2018-02-11 10:20:20 | + grep -Eq '(CREATE|UPDATE)_COMPLETE'


Thanks

Boris



From: users  on behalf of Boris 

Sent: Friday, February 9, 2018 9:03 PM
To: James LaBarre
Cc: us...@lists.rdoproject.org
Subject: Re: [rdo-users] Quickstart and containers




Пятница, 9 февраля 2018, 19:17 +03:00 от James LaBarre :

If I am trying to familiarize myself with the newer containerized
overcloud (Queens & upwards), is there a way to build a TripleO
Quickstart on a single node?
   Due to I cannot any longer respond from  hotmail.com ( backup address is 
used )

   1. https://www.anstack.com/blog/2018/01/05/tripleo-quickstart-cheatsheet.html
   2. this one was done via F27 connection to VIRTHOST
  http://lxer.com/module/newswire/view/252059/index.html

  I believe it might work in the way suggested by Carlos Camacho (1)

  Boris.

As I say, it's mainly to get some
experience in the newer configurations, after which I could probably
grab some more baremetal and do proper setups.

I do find myself wondering, though, with the way Quickstart worked with
images, if it's been doing containers all along...


___
users mailing list
us...@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/users

To unsubscribe: 
users-unsubscr...@lists.rdoproject.org


С уважением,
Boris Derzhavets
dba...@list.ru
___
dev mailing list
dev@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/dev

To unsubscribe: dev-unsubscr...@lists.rdoproject.org

Re: [rdo-dev] Long queue in RDO SF

[Haïkel Guémar]

On 02/11/2018 05:57 PM, David Manchado Cuesta wrote:

FWIW no alerts during the weekend and I have been able to spawn 10+
instances without issue.

Cheers
David Manchado
Senior Software Engineer - SysOps Team
Red Hat
dmanc...@redhat.com



Thanks David!
Just wanted to check :)

Regards,
H.



On 11 February 2018 at 16:39, Paul Belanger  wrote:

On Sun, Feb 11, 2018 at 12:44:52PM +0100, Haïkel Guémar wrote:

On 02/11/2018 12:17 AM, Sagi Shnaidman wrote:

Hi,

I see openstack-check has 53 hours queue when 1 job only is queued:
https://review.rdoproject.org/zuul/

Seems like problem with nodepool?

Thanks

--
Best regards
Sagi Shnaidman


___
dev mailing list
dev@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/dev

To unsubscribe: dev-unsubscr...@lists.rdoproject.org



Ok, it looks bad enough that a simple nodepool list fails with that error:
os_client_config.exceptions.OpenStackConfigException: Cloud rdo-cloud was
not found.

Despite RDO Cloud looks up, there might be an outage or incident hence
copying David Manchado.

Regards,
H.


Okay, I have to run, but this looks like a configuration issue. It is hard to
tell without debug logs for nodepool or zuul, but please double check your node
is setup properly.

I have to run now.



___
dev mailing list
dev@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/dev

To unsubscribe: dev-unsubscr...@lists.rdoproject.org

Re: [rdo-dev] Long queue in RDO SF

[Javier Pena]

Hi,

I see no issues in nodepool. Looking at the current Zuul queue, we have a 
single job stuck for ~90 hours, queued on 
"gate-tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset035-queens".

When that happens, it's usually a configuration issue, and this is the case 
here: we have no definition for the queens gate job for featureset035 in 
https://github.com/rdo-infra/review.rdoproject.org-config/blob/master/jobs/tripleo-upstream.yml#L979-L990.

An easy way to troubleshoot this is:

- If we find one or more jobs queued, first check at 
https://review.rdoproject.org/jenkins/ and see if there are nodes available to 
jenkins.

- If there are, just check the list of jobs available to Jenkins. If it's not 
there, we need to double-check the jjb configuration and find what is missing.

My only doubt is why this does not show up as "NOT_REGISTERED" in Zuul as it 
did before.

I have proposed https://review.rdoproject.org/r/12038 as a fix for this.

Regards,
Javier

- Original Message -
> FWIW no alerts during the weekend and I have been able to spawn 10+
> instances without issue.
> 
> Cheers
> David Manchado
> Senior Software Engineer - SysOps Team
> Red Hat
> dmanc...@redhat.com
> 
> 
> On 11 February 2018 at 16:39, Paul Belanger  wrote:
> > On Sun, Feb 11, 2018 at 12:44:52PM +0100, Haïkel Guémar wrote:
> >> On 02/11/2018 12:17 AM, Sagi Shnaidman wrote:
> >> > Hi,
> >> >
> >> > I see openstack-check has 53 hours queue when 1 job only is queued:
> >> > https://review.rdoproject.org/zuul/
> >> >
> >> > Seems like problem with nodepool?
> >> >
> >> > Thanks
> >> >
> >> > --
> >> > Best regards
> >> > Sagi Shnaidman
> >> >
> >> >
> >> > ___
> >> > dev mailing list
> >> > dev@lists.rdoproject.org
> >> > http://lists.rdoproject.org/mailman/listinfo/dev
> >> >
> >> > To unsubscribe: dev-unsubscr...@lists.rdoproject.org
> >> >
> >>
> >> Ok, it looks bad enough that a simple nodepool list fails with that error:
> >> os_client_config.exceptions.OpenStackConfigException: Cloud rdo-cloud was
> >> not found.
> >>
> >> Despite RDO Cloud looks up, there might be an outage or incident hence
> >> copying David Manchado.
> >>
> >> Regards,
> >> H.
> >>
> > Okay, I have to run, but this looks like a configuration issue. It is hard
> > to
> > tell without debug logs for nodepool or zuul, but please double check your
> > node
> > is setup properly.
> >
> > I have to run now.
> >
> 
___
dev mailing list
dev@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/dev

To unsubscribe: dev-unsubscr...@lists.rdoproject.org