Description of problem:


~]# hammer -u admin -p changeme repository create --name test2 --content-type 'ostree' --product=p1 --url=https://kojipkgs.fedoraproject.org/atomic/23/ --publish-via-http=no --checksum-type=sha1 --organization-id=1
Repository created

Here I created a ostree type repo with checksum-type=`sha1` and repo is created and info shows the checksum-type. But 

1) is it a valid use case ? can user set checksum type for ostree repos ?
If not then we should raise validation error

If yes, then same functionality should be exposed on UI

[root@qe-sat6-rhel7 ~]# hammer -u admin -p changeme repository info --name test2 --product=p1 --organization-id 1
ID:                 211
Name:               test2
Label:              test2
Organization:       Default Organization
Red Hat Repository: no
Content Type:       ostree
Checksum Type:      sha1
URL:                https://kojipkgs.fedoraproject.org/atomic/23/
Publish Via HTTP:   no
Published At:       https://qe-sat6-rhel7.satqe.lab.eng.rdu2.redhat.com/pulp/ostree/web/Default_Organization/Library/custom/p1/test2
Relative Path:      Default_Organization/Library/custom/p1/test2
Product:            
    ID:   516
    Name: p1
GPG Key:            

Sync:               
    Status: Not Synced
Created:            2016/08/25 10:43:13
Updated:            2016/08/25 10:43:15
Content Counts:     
    OSTree Branches: 0


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
Here I created a ostree type repo with checksum-type=`sha1` and repo is created and info shows the checksum-type. But 

1) is it a valid use case ? can user set checksum type for ostree repos ?
If not, then we should raise validation error

If yes, then same functionality should be exposed on UI

Additional info: