Though we have a pre-deployment check [1] there still may be situations when errors are made in other parts of the description and that would only effect on the stage of installing of packages which is not under control of Nailgun code. The bug is best illustration here. Sure thing we must enhance the check: test that repository is viable too. But, in my opinion, it is not so simply to achieve as some design of such code and the way it is integrated in current logic of processing repository data must be done.
Though we have a pre-deployment check [1] there still may be situations when errors are made in other parts of the description and that would only effect on the stage of installing of packages which is not under control of Nailgun code. The bug is best illustration here. Sure thing we must enhance the check: test that repository is viable too. But, in my opinion, it is not so simply to achieve as some design of such code and the way it is integrated in current logic of processing repository data must be done.
[1] https:/ /github. com/openstack/ fuel-web/ blob/master/ nailgun/ nailgun/ task/task. py#l1445- l1449