Bug 819984

Summary:	domain#update doesn't handle all gears (particularly scaled ones)
Product:	OKD	Reporter:	Dan McPherson <dmcphers>
Component:	Pod	Assignee:	Ram Ranganathan <ramr>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	2.x	CC:	bmeng, dmace, mfisher, mpatel, pruan, xtian
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-14 17:22:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dan McPherson 2012-05-08 19:29:27 UTC

Description of problem:

scale gears aren't updated when update namespace
we need to do a check in stage and prod for whether any existing apps are in this state.  May require a migration fix.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create a scaled app
2. Update namespace
3.
  
Actual results:
gears aren't changed on node or in dns


Expected results:
they should be


Additional info:

Comment 2 Dan McPherson 2012-05-09 14:28:39 UTC

Hi Xiaoli,

  I think it was just just the dns that was broken.  Not the env var but the actual DNS entry.  So if you would ping the old gear the dns entry was still there.  But pinging the gear in the new namespace would have not found anything in dns.

Comment 3 Krishna Raman 2012-05-09 15:03:51 UTC

*** Bug 819993 has been marked as a duplicate of this bug. ***

Comment 4 Peter Ruan 2012-05-11 03:39:04 UTC

verified with devevn-stg_189

Comment 5 Xiaoli Tian 2012-05-11 10:44:16 UTC

Checked again on devenv-stage_193, 

This bug may be partially fixed: 

The DNS itself is fixed, the old gear dns can not be accessed anymore and the new gear dns could be accessed.

But the entry in haproxy.cfg is still not updated, the new domain is doma001, but it's still using the old domain "doma00" :

" server gear-4fdd18229c-doma00 10.118.193.75:35536 check fall 2 rise 3 inter 2000 cookie 4fdd18229c-doma00 "

Should this be fixed as well?

Comment 6 Dan Mace 2012-05-11 13:18:50 UTC

@xiaoli,

We have a bz logged for the haproxy.cfg issue:

https://bugzilla.redhat.com/show_bug.cgi?id=811671

Comment 7 Xiaoli Tian 2012-05-11 13:43:12 UTC

Thanks, Dan Mace

I've updated summary of bug 811671, then let that bug to track it.