Public bug reported: Recently OpenStack introduced a mechanism to specify a constrained "working set" of packages that are "guaranteed" to produce a working OpenStack environment. This pinning of packages limits the more broadly- defined requirements.txt which is managed by global-requirements. Even though it pins package versions, it is called "upper-constraints".
We should include those constraints in our test runs. A mechanism exists to allow constraints to be overridden for specific patches by using Depends-On to a constraints update, allowing testing of new constraints. Given enough test coverage in the constraints updates (to be addressed in a separate patch to the gate jobs for that project) this would have allowed Horizon to detect that the recent heatclient update broke Horizon, but also would have allowed the Horizon gate to continue unaffected by the new heatclient update (because we would have been pinned to a previous, working version). ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1554791 Title: Horizon should use upper-constraints in testing Status in OpenStack Dashboard (Horizon): New Bug description: Recently OpenStack introduced a mechanism to specify a constrained "working set" of packages that are "guaranteed" to produce a working OpenStack environment. This pinning of packages limits the more broadly-defined requirements.txt which is managed by global- requirements. Even though it pins package versions, it is called "upper-constraints". We should include those constraints in our test runs. A mechanism exists to allow constraints to be overridden for specific patches by using Depends-On to a constraints update, allowing testing of new constraints. Given enough test coverage in the constraints updates (to be addressed in a separate patch to the gate jobs for that project) this would have allowed Horizon to detect that the recent heatclient update broke Horizon, but also would have allowed the Horizon gate to continue unaffected by the new heatclient update (because we would have been pinned to a previous, working version). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1554791/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp