[14:04] rick_h_: who do I ask charmworld questions to? [14:04] mbruzek: me or bac really I guess [14:04] mbruzek: we're both holding the gun to shoot it in the head [14:04] rick_h_: Understand [14:05] what's she done this time? :) [14:05] rick_h_: We pushed some code to a personal namespace last night (~kubernetes) and I don't see the revision bump in the charm store. I figure that is a charmworld ingestion problem? But educate me if I am wrong. [14:06] mbruzek: looking [14:06] mbruzek: what code? [14:07] I know they don't match bzr 1 for 1, but I would have expected to see a revision bump with Charles Butler's commit message there. https://jujucharms.com/u/kubernetes/kubernetes/trusty [14:07] Also https://jujucharms.com/u/kubernetes/kubernetes-master/trusty [14:07] mbruzek: yes, there's a bug in pulling the bzr rev info from charmworld. [14:07] mbruzek: checking the code vs the code in the charmstore [14:08] rick_h_: how are you doing that? Teach me to fish and I will leave you alone [14:08] mbruzek: so what I'm doing is going to the file list on the right side of the page [14:08] and clicking the "View Code" [14:08] ahh [14:08] mbruzek: and then looking at the last commit [14:09] mbruzek: and then based on the files changed, see if that file looks right in the actual file in the charmstore (from that list of files) [14:09] mbruzek: basically "ignoring what the page says is the last commit, is the content actually correct" [14:10] thats what i did :D [14:10] mbruzek: so looking at that, the change you made tothe test_install on the -master is there [14:10] mbruzek, i can verify the k8's master was not pushed yesterday as we thought, it landed in a personal branch of mine... i pushed the k8's master charm code about 30 minutes ago [14:10] rick_h_: that is fine by me but we are building bundles for the Cloud Weather Report (a high priority for our team right now). And our bundles have to have Specific revision numbers to pull the right code [14:11] but the k8's charm has revved to -7, as it should be. we're just pending k8's master to rev [14:11] mbruzek: lazypower the other thing I was doing is chceking the changes api to see if an update was pulled https://api.jujucharms.com/charmstore/v4/changes/published?limit=1000 [14:11] rick_h_: Those revision numbers in the charm store are the same as _before_ we pushed those changes, and we want the bundle to pull the right code [14:11] nice [14:11] k8s-master just revved to -9 as it should [14:12] mbruzek, the charms are where they need to be now. check the bundle vs whats available [14:12] the revnos match [14:12] mbruzek: lazypower huh? So the charmstore rev number did not increment? [14:12] nah they did increment [14:13] oh ok [14:13] rick_h_: kuberentes-master is still on 8, I see 9 in that api link that Rick just posted [14:13] Kubernetes went from 6 => 7 yesterday. [14:13] scared me as we've not chnaged anything in a bit and that would be scary. [14:13] Kubernetes-master will be moving from 8=>9 as soon as the store updates its display [14:13] but the deliverable should be shipping revno 9 already [14:13] mbruzek: it's 9 now https://jujucharms.com/u/kubernetes/kubernetes-master/ [14:13] s/deliverable/api/ [14:14] or rick_h_ can call schenanigans and prove us both wrong :D [14:14] juju deploy cs:~kubernetes/trusty/kubernetes-master-9 is the deploy command right now as I loaded the -master page [14:14] rick_h_: it seems to have *just* happened. [14:15] rick_h_: when I started this converstation it was 8, maybe since the boss looked at it charmworld started acting right [14:15] mbruzek: stale http cache? [14:15] mbruzek: I'm more tempted to think it's a caching issue tbh [14:16] we've got a http cache in there and wonder if it got 'stuck' until a few reloads updated things [14:16] rick_h_: possibly, I did refresh before I talked with you but I didn't force refresh [14:16] the charmworld/charmstore data and the api was good when hit it seemed (like that changes api call) [14:17] mbruzek: let me know if you hit that again. Maybe we've gone too agreesive. Since the data is essentially 'static' (the page for -8 will never change until it goes to -9) maybe we need ot fix the rules morefor pages without a revision number [14:18] rick_h_: everything looks correct now. [14:18] thanks!