#solum

Ed Cranford proposed a change to stackforge/solum: Reverse diff check in check_uptodate https://review.openstack.org/118489

A change was merged to stackforge/python-solumclient: Plan create/show will display artifact public ssh keys if present https://review.openstack.org/109468

A change was merged to stackforge/solum: Moving git_url into git_info dictionary https://review.openstack.org/116710

A change was merged to stackforge/solum-specs: Custom language packs https://review.openstack.org/103689

so many little fixes all getting zuul'd at once

A change was merged to stackforge/solum: Configurable base location of worker scripts https://review.openstack.org/118390

whoo

James Li proposed a change to stackforge/solum: Run unit tests against a particular git branch https://review.openstack.org/117885

Paul Czarkowski proposed a change to stackforge/solum: WIP: use coreos+docker for VM based deployments https://review.openstack.org/102646

so that problem about q-dhcp failing is because it wants dnsmasq at 2.63 or better, but Precise only has 2.59

datsun180b: thanks for that insight on the q-dhcp concern.

i guess like james said earlier we can try rolling back qneutrontum

A change was merged to stackforge/solum: Add use of guestagent install shell script in infra dibs https://review.openstack.org/111012

moving forward to trusty will let us confront the old rabbit issue although we have a workaround for that.

Paul Czarkowski proposed a change to stackforge/solum: WIP: use coreos+docker for VM based deployments https://review.openstack.org/102646

fatal: unable to access 'https://github.com/stackforge/solum.git/': Could not resolve host: github.com

that's from slugtester. that seems like a problem!

running at RAX?

$ host github.com

github.com has address 192.30.252.129

yeah that works from the vm

i'm trying to figure out why slugtester can't cut it

ok

trying git:// i got an even stranger message: fatal: unable to connect to git@github.com:

git@github.com: Servname not supported for ai_socktype

and in none of those cases are those messages being dropped into the stage logs like they're supposed to, look i need to fix that too

A change was merged to stackforge/solum: Anticipate Plan delete DBReferenceError https://review.openstack.org/112412

batting a thousand

James Li proposed a change to stackforge/solum: Run unit tests against a particular git branch https://review.openstack.org/117885

Jeremy Stanley proposed a change to stackforge/solum-dashboard: Work toward Python 3.4 support and testing https://review.openstack.org/118845